pubchem-mcp-server
Related Servers
Alternatives to pubchem-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to search and retrieve chemical compound information, structures, and physical properties from the PubChem database. It supports querying via compound names, SMILES notation, or CIDs to provide detailed molecular data for chemical analysis.5-
- AlicenseBqualityDmaintenanceEnables comprehensive access to PubChem's chemical database with over 110 million compounds. Supports chemical searches, structure analysis, bioactivity data, safety information, and molecular property calculations through 30 specialized tools.30MIT
- AlicenseNot gradedqualityBmaintenanceProvides access to the NIH PubChem chemistry compound database, enabling queries for compound synonyms and other data through natural language.29 npmMIT
- FlicenseBqualityDmaintenanceExtracts basic chemical information and drug data from the PubChem API. It enables users to retrieve molecular details such as SMILES, IUPAC names, molecular formulas, and synonyms for specific compounds.311-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to convert a chemical name, CAS number, SMILES, InChI, or InChIKey into a requested representation, and to perform a one-shot lookup returning SMILES, InChIKey, IUPAC name, molecular formula, molecular weight, and CAS number.7 npmMIT
- AlicenseBqualityDmaintenanceEnables AI agents to search the Chemspace API for synthesizable building blocks and screening compounds using exact matches, substructure searches, and similarity searches by SMILES strings.31MIT
TDQS
Scored across 10 tools
Each tool targets a distinct data facet of PubChem (search, details, image, 3D, xrefs, safety, bioactivity, interactions, assays, summary), so boundaries are largely clear. The only mild overlap is between pubchem_get_bioactivity and pubchem_get_compound_interactions (both surface target activity) and details vs. summary, but descriptions clarify the intended split.
All tools follow a consistent pubchem_<verb>_<noun> pattern (pubchem_search_*, pubchem_get_compound_*, pubchem_get_summary), with uniform snake_case and only get/search as verbs. The convention is predictable and readable throughout.
10 tools is well-scoped for a large multi-faceted database like PubChem, with each tool earning its place across the compound/bioassay/target domains. No redundancy or padding.
Covers a broad read-only surface: compound search (name/SMILES/formula/substructure/similarity), details, image, 3D, xrefs, safety, bioactivity, interactions, plus assay search and entity summaries. Minor gaps exist (e.g., no dedicated gene/protein/taxonomy detail endpoint beyond the generic summary), but core workflows are well supported.