pubchem-mcp-server
MCP server for PubChem. Search compounds, properties, safety, bioactivity, xrefs, and summaries.
https://pubchem.caseyjhand.com/mcpCurrent observation
This endpoint answered at its latest recorded check.
What this server reports about itself
Self-reported at initialize. Not verified by Licium.
- Server name
- pubchem-mcp-server
- Version
- 0.6.0
- Capability keys
- logging, resources, tools, prompts
- Tool names
- pubchem_search_compounds, pubchem_get_compound_details, pubchem_get_compound_image, pubchem_get_compound_3d_structure, pubchem_get_compound_xrefs, pubchem_get_compound_safety, pubchem_get_bioactivity, pubchem_get_compound_interactions, pubchem_search_assays, pubchem_get_summary
Use the pubchem_* tools to query PubChem's chemical database. Compounds are addressed by CID, assays by AID. Most flows start at `pubchem_search_compounds` (name, SMILES, InChIKey, formula, substructure, superstructure, or 2D similarity → CIDs), then call per-CID tools for details, safety, image, cross-references, bioactivity, interactions (drug-drug/drug-food/target), or 3D structure. To find assays for a biological target, chain `pubchem_search_assays` (gene/protein → AIDs) into `pubchem_get_summary` (`entityType: assay`) per AID; to check whether a compound is active against a target, call `pubchem_get_bioactivity` with a `cid` plus `targetGeneId`/`targetAccession`. `pubchem_get_summary` covers assay/gene/protein/taxonomy entity lookups. Compound and assay records are also exposed as URI-addressable resources (e.g. `pubchem://compound/{cid}`, `pubchem://assay/{aid}`).
Reported Aug 17, 2026, 05:06 AM UTC.
Check history
Oldest to newest. Each row is one recorded check.
- respondsMCP initialize · 8s limit · HTTP 200 · 99ms
- respondsMCP initialize · 8s limit · HTTP 200 · 356ms
- respondsMCP initialize · 8s limit · HTTP 200 · 279ms
- respondsMCP initialize · 8s limit · HTTP 200 · 331ms