PubChem PUG REST API MCP. Audit compounds and formulas by CID or name instantly.

Listen up. This server hooks your AI agent right into PubChem, which is basically the gold standard for molecular data—it’s run by the National Library of Medicine. It lets your agent audit chemical compounds, pull deep metadata, and query specific formulas or Compound Identifiers (CIDs) without you ever having to visit a clunky scientific website yourself.

You're getting direct access to authoritative chemistry info.

When you use this tool set, your agent doesn’t just search; it performs structured chemical audits. It handles the complex stuff so you don't have to babysit databases manually. This speeds up your workflow big time.

Here’s how your AI client uses the tools:

First, before running anything else, your agent checks the service health using check_api_status. That confirms whether the PubChem PUG REST service is actually online and ready to spit out data. You don't want a failed retrieval because the endpoint was down.

To pull specific details on an already known compound, you’ve got two main options. If you know the exact Compound Identifier (CID), you use get_compound_by_cid. This tool retrieves all the technical metadata, molecular formulas, and detailed specs for that chemical record. On the other hand, if you only have a common or IUPAC name—say, 'Aspirin'—you use get_compound_by_name.

That gives your agent comprehensive records and formulas based purely on the name you feed it.

If you don’t know which CID to start with, you search first. You run search_compound_cids by giving it a general keyword or phrase. This scans the whole database and finds multiple CIDs that match your search term.

Knowing these tools lets your agent handle everything from basic lookups to deep technical auditing. It gathers high-resolution properties and formulas you need when you’re verifying any chemical record. You can find detailed records, including IUPAC names and molecular formulas, using the known name of a compound via get_compound_by_name. For full scientific verification, all available details for a compound are pulled through get_compound_by_cid once that unique ID is provided.

If you just need to know which CIDs exist for a term—like 'glucose' or something else—you use search_compound_cids to get that list of matching identifiers.

This setup makes sure your agent never gets stuck waiting on another person to run the search, giving it immediate access to core molecular data. You just hook up your preferred AI client and point it at this server. It handles all the necessary calls—status checks, name lookups, CID lookups, and keyword searches—so you're always working with verified chemical information.