c3fst Biomedical Search
PYPI · C3FST-MCP-SERVER
Biomedical search: FDA drugs, MeSH headings, ClinVar genomic variants with BM25 ranking.
Available components
Last scanned (12 hours ago)
Scores higher than 2% of PyPI servers
Category Health and Science
Degraded
One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- No malware found by supply-chain analysis.Pass
- Known CVEs could not be checked: we could not find this package in its registry.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: we could not find this package in its registry.Unverified
Provenance & Transparency0
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: the registry has no such package, so there's no artefact to verify. See how to fix → View diagnostics → Fail
- License check failed: the registry has no such package, so no license can be read. See how to fix → Fail
- Maintenance check failed: the registry has no such package, so there's no release history to read. See how to fix → Fail
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →
Checks we ran (5)
- Malware scan
- Source repository
- Provenance
- License
- Maintenance
Checks we could not complete (9)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Known CVEs in Supply Chain SecurityKnown CVEs could not be checked: we could not find this package in its registry.
- Install scripts in Supply Chain SecurityInstall-script risk not yet assessed.
- Dependency health in Supply Chain SecurityDependency health could not be checked: we could not find this package in its registry.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.
- Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 −6
- Malware scan: unverified → pass ▲ security
- 20 Nov 26 −7
- Malware scan: pass → unverified ▼ security
- 19 Nov 26 −7
The score moved with no change recorded against any check. We would rather say so than guess.
- 18 Nov 26 0
- Malware scan: unverified → pass ▲ security
- 17 Nov 26 0
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Provenance: Provenance check failed: the registry has no such package, so there's no artefact to verify. security
- The code this package runs automatically changed: its declared build backend security
- Dependency health: 0.99 → unverified ▼ functional
- License: pass → fail ▼ functional
- Maintenance: pass → fail ▼ functional
- Licence: MIT functional
- 11 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 9 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Sept 26 0
- Provenance: unverified → fail ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed pypi/c3fst-mcp-server@1.0.0
Provenance Package not found
The registry answered that no such package exists, so no provenance could be looked up.
| Result | Package not found |
|---|---|
| Ecosystem | pypi |
| Reason | Package details unavailable |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. Our sandbox could not run this package, so no tool list has been captured. That is a gap on our side, not a finding about the package.
How do I install the c3fst Biomedical Search MCP server?
c3fst Biomedical Search runs locally as a PyPI package, launched with uvx c3fst-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · c3fst-mcp-server
claude mcp add mjandrews1-c3fst-biomedical-search -- uvx c3fst-mcp-server
What is the c3fst Biomedical Search MCP server?
c3fst Biomedical Search is an MCP server listed in the public MCP registry as io.github.mjandrews1/c3fst-biomedical-search. Biomedical search: FDA drugs, MeSH headings, ClinVar genomic variants with BM25 ranking. This page covers its PyPI package (c3fst-mcp-server).
Is the c3fst Biomedical Search MCP server safe to use?
c3fst Biomedical Search scores 14 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Is the c3fst Biomedical Search MCP server still maintained?
c3fst Biomedical Search is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 16 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the c3fst Biomedical Search MCP server?
VerifyMCP ran 5 checks on c3fst Biomedical Search, covering Malware scan, Source repository, Provenance, License and 1 more. 9 items could not be completed, a gap on our side rather than a finding about c3fst Biomedical Search: Known CVEs, Install scripts, Dependency health, Security disclosure and 5 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.