Scigantic
PYPI · SCIGANTIC-MCP · 2 COMPONENTS
Search public scientific datasets and read schema cards that describe their files, columns and rows
Available components
Last scanned (13 hours ago)
Scores higher than 67% of PyPI servers
Category Health and Science
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 35 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT-0).Pass
- Actively maintained (last published 11 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1448 tokens (~131/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 20 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 12 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 10 Nov 26 54
First indexed and scored.
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/scigantic-mcp@0.3.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 35 packages
| Packages resolved | 35 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_archive ~43
Get full metadata for one archive by id, including whether a schema card exists. Args: id: Archive id from search_archives.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_data_access ~117
Get how to load a dataset in YOUR OWN environment: storage location plus copy-paste code snippets (from the dataset's schema card, or generated as a fallback). Use this after finding a dataset when you want to run analysis where you are, rather than in a hosted notebook. Args: id: Archive id from search_archives. language: Optional filter for the snippet language (e.g. "datasets", "s3fs", "gcsfs").
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| language | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_schema_card ~80
Get the compact schema card for an archive: file format, columns, sample rows/headers, sidecar docs (READMEs/data dictionaries) and a copy-paste starter cell. This is the fastest way to understand a dataset's structure without downloading it. Args: id: Archive id from search_archives.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_archive_files ~63
List a sample of the files/objects in an archive's storage. Args: id: Archive id from search_archives. limit: Max entries (default 50, max 200).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_archives ~134
Search the Scigantic catalog of public scientific data archives by natural-language query. Returns ranked matches with id, title, category and a short summary across all domains. Follow up with get_schema_card to understand a match's structure. Args: query: Natural-language search, e.g. "single-cell RNA-seq of human cortex". category: Optional category filter, e.g. "Genomics & Bioinformatics" (comma-separate for several). limit: Max results (default 10, max 50).
| Name | Type | Req | Description |
|---|---|---|---|
| category | – | – | – |
| limit | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
surechembl_compound ~165
Look up a compound in SureChEMBL, EMBL-EBI's database of chemistry extracted from patents, by any identifier, and report its structure, properties, cross-references (ChEMBL, PubChem, DrugBank, ChEBI, PDB) and how many patents mention it. Args: identifier: A SureChEMBL id ("SCHEMBL1353" or "1353"), a ChEMBL id ("CHEMBL25"), a PubChem CID as "pubchem:2244", a DrugBank id as "drugbank:DB00945", a standard InChIKey, a SMILES, or a chemical name ("aspirin").
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
surechembl_patent ~136
A patent document from SureChEMBL: title, dates, applicants, inventors, assignees, family, priority claims, number of compounds named in the text, abstract, and (optionally) the claims and description text. Args: doc_id: Publication number with kind code, e.g. "US-10000000-B2", "WO2016144528A1", "EP-3268771-B1". include_text: Also return the claims and description (can be long). Default false.
| Name | Type | Req | Description |
|---|---|---|---|
| doc_id | string | yes | – |
| include_text | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
surechembl_patent_chemistry ~120
The compounds SureChEMBL's text-mining finds named in a patent's text: SCHEMBL id, name, SMILES, InChIKey, formula, weight. Structures that appear only in images or MOL attachments are not included. Args: doc_id: Publication number with kind code, e.g. "US-5399578-A". limit: Max compounds to list (default 50, max 500).
| Name | Type | Req | Description |
|---|---|---|---|
| doc_id | string | yes | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
surechembl_patents_for_compound ~136
List the patents in which a compound was found (SureChEMBL). Accepts the same identifier forms as surechembl_compound. Aspirin is in ~700,000 documents, so read the total and narrow with surechembl_search_patents when it is large. Args: identifier: SureChEMBL id, ChEMBL id, "pubchem:CID", InChIKey, SMILES, or name. limit: Max patents to list (default 20, max 200).
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
surechembl_search_patents ~173
Full-text patent search over SureChEMBL with Solr syntax. Plain terms search all text; field prefixes narrow: ttl (title), ab (abstract), clm (claims), desc, asg (assignee), inv (inventor), pdyear, cpc, ic (IPCR), fam (family id). Quote publication numbers: pn:"US-10000000-B2". Combine with AND/OR/NOT. Only US, EP, WO, JP and CN publications are searchable. Args: query: e.g. 'ttl:kinase AND asg:novartis AND pdyear:2024'. limit: Max patents to list (default 20, max 200).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
surechembl_structure_search ~135
Search SureChEMBL's 31 million patent compounds by chemical structure. Args: structure: A SMILES. mode: "similarity" (Tanimoto, default), "substructure" (needs at least 5 atoms; the server caps results at 10,000), "identical" (all features must match), or "connectivity" (same skeleton, any stereo/isotopes). limit: Max hits (default 20, max 500).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| mode | string | – | – |
| structure | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Scigantic MCP server?
Scigantic runs locally as a PyPI package, launched with uvx scigantic-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · scigantic-mcp
claude mcp add com-scigantic-mcp -- uvx scigantic-mcp
What is the Scigantic MCP server?
Scigantic is an MCP server listed in the public MCP registry as com.scigantic/mcp. Search public scientific datasets and read schema cards that describe their files, columns and rows. This page covers its PyPI package (scigantic-mcp).
Is the Scigantic MCP server safe to use?
Scigantic scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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.
What tools does the Scigantic MCP server expose?
Scigantic exposes 11 tools: search_archives, get_archive, get_schema_card, list_archive_files, get_data_access, and 6 more. Their descriptions and schemas cost roughly 1,302 tokens of context every time the server is loaded.
Is the Scigantic MCP server still maintained?
Scigantic is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Scigantic MCP server under?
Scigantic declares the MIT-0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Scigantic MCP server?
VerifyMCP ran 16 checks on Scigantic, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.