PubChem Chemical Safety MCP Server
Related Servers
Alternatives to PubChem Chemical Safety 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
- FlicenseBqualityFmaintenanceExtracts 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-
- AlicenseAqualityAmaintenanceEnables AI agents and applications to search, retrieve, and analyze chemical compounds, substances, and bioassays from PubChem's vast chemical information database through comprehensive tools for chemical research and discovery.101339Apache 2.0
- AlicenseNot gradedqualityCmaintenanceProvides access to the NIH PubChem chemistry compound database, enabling queries for compound synonyms and other data through natural language.5MIT
- AlicenseNot gradedqualityDmaintenanceProvides chemical hazard data from ECHA, NIOSH, GHS, and ICSC, enabling lookups of SVHC status, occupational exposure limits, GHS classifications, and cross-references to cosmetic and food additive databases.MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_compound_info retrieves basic chemical properties, get_safety_info focuses on GHS hazard classifications, and get_toxicity_data provides experimental toxicity data. There is no overlap in functionality, and the descriptions clearly differentiate their domains (basic info vs. safety vs. toxicity).
All tools follow a consistent verb_noun pattern with 'get_' prefix and snake_case naming (get_compound_info, get_safety_info, get_toxicity_data). This predictable structure makes it easy for agents to understand and navigate the toolset without confusion.
With only 3 tools, the set feels thin for a chemical safety domain that might benefit from additional operations like searching compounds, batch queries, or regulatory data. While the tools cover core areas, the low count limits comprehensive coverage and could require agents to work around missing functionality.
The tools cover key aspects (basic info, safety, toxicity) but leave notable gaps. There is no search or lookup tool to find compounds by criteria, no batch operations for efficiency, and no update/delete capabilities (though less critical here). Agents may struggle to initiate workflows without a way to discover compounds beyond direct name input.