scientific-data-mcp@0.15.0
VERIFIED· not startedPublisher claims: "Scientific entity data MCP: PubChem, ChEMBL, UniProt, RCSB PDB, PubMed, WHO, STRING, openFDA, ClinicalTrials.gov, plus key-gated Materials Project and BioGRID." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
BIOGRID_ACCESS_KEYMATERIALS_PROJECT_API_KEYNCBI_API_KEYOPENFDA_API_KEYConfiguration, not credentials: NCBI_EMAIL- Where it talks to
- no vendor host named in the codeAlso ebi.ac.uk, nih.gov, bindingdb.org, thebiogrid.org, cbioportal.org, clinicaltrials.gov, ensembl.org, cancer.gov, gtexportal.org, jax.org, kegg.jp, materialsproject.org, monarchinitiative.org, fda.gov, opentargets.org, rcsb.org, reactome.org, string-db.org, uniprot.org, githubusercontent.com, obolibrary.org, azureedge.net, who.int — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names ebi.ac.uk, nih.gov, bindingdb.org, thebiogrid.org, cbioportal.org, clinicaltrials.gov, ensembl.org, cancer.gov, gtexportal.org, jax.org, kegg.jp, materialsproject.org, monarchinitiative.org, fda.gov, opentargets.org, rcsb.org, reactome.org, string-db.org, uniprot.org, githubusercontent.com, obolibrary.org, azureedge.net, who.int as well as its own vendor. The guard injects BIOGRID_ACCESS_KEY, MATERIALS_PROJECT_API_KEY, NCBI_API_KEY, OPENFDA_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-20 and scored it 93/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
No findings across 7,387 lines in 81 files.
Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Not checked against OSV yet; the weekly check has not reached this version.