Retrieve GHS hazard classification data for a chemical via PubChem PUG-View
domain: pubchem.ncbi.nlm.nih.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify the PubChem Compound ID (CID) for your chemical via PUG-REST, e.g. `GET https://pubchem.ncbi.nlm.nih.gov/rest/pug/compound/name/{name}/cids/JSON`.
Request the GHS Classification section of that compound's record with PUG-View: `GET https://pubchem.ncbi.nlm.nih.gov/rest/pug_view/data/compound/{cid}/JSON/?response_type=display&heading=GHS+Classification`.
Parse the returned JSON for hazard classification, signal word, pictograms, hazard statements, and precautionary statements — this data is compiled from source-specific hazard/SDS datasets rather than computed directly by PubChem.
For a fuller safety summary (first aid, handling, exposure controls), request the compound's Laboratory Chemical Safety Summary (LCSS) section using the same PUG-View pattern with a different `heading` value.
Remember PUG-View differs from PUG-REST: PUG-REST returns PubChem-computed property values, while PUG-View returns annotations aggregated from other data sources (including GHS/LCSS).
Known gotchas
Not every PubChem compound has a GHS Classification section — it's only present when a GHS classification exists in an underlying source dataset for that record, so absence of the heading isn't necessarily an error.
You must resolve a chemical name/CAS/SMILES to a numeric CID first via PUG-REST (or PubChem search) — the PUG-View compound endpoint is keyed by CID, not by name.
PUG-REST and PUG-View are two distinct services under the same PubChem domain with different request/response conventions — mixing up their URL patterns is a common integration mistake.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?