Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

SafetyDataSheetAPI

REMOTE · SAFETYDATASHEETAPI.COM

Extract safety data sheet (SDS/MSDS) PDFs into a fixed 16-section JSON record.

+4 this week 74 Trust /100

Last scanned (6 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 580 tokens (~145/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 83% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 25 Oct 26 69

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://safetydatasheetapi.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=safetydatasheetapi.com CN=WE1,O=Google Trust Services,C=US 18 Oct 2026 16 Jan 2027 ECDSA 256 ECDSA-SHA256 397438dca17e9b131311cbb06f8ad6b7
SANs: safetydatasheetapi.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of safetydatasheetapi.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
safetydatasheetapi.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://safetydatasheetapi.com/mcp Verified 200
http (plaintext) http://safetydatasheetapi.com/mcp HTTPS enforced 301 https://safetydatasheetapi.com/mcp
MCP tools · 4 exposed · ~453 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
extract_sds ~193

Extract one Safety Data Sheet PDF into a normalized 16-section record (product identification, hazards, composition, first aid, transport, regulatory, and more) plus a confidence_score and warnings. Provide the PDF as file_url (a public https URL) or file_base64. Billed per document from prepaid credit (failures are not billed). Requires an API key.

NameTypeReqDescription
file_base64string–Base64-encoded SDS PDF bytes (use for small files).
file_urlstring–Public https URL of the SDS PDF.
filenamestring–Optional file name, for example acetone-sds.pdf.
include_formatsarray–Also return the XML and/or CSV renderings. Omitted by default to keep results compact.
language_hintstring–Optional language hint such as en, de, fr.
schema_versionstring–Optional output schema version.

No output schema declared.

No examples provided.

get_account ~46

Get the prepaid credit balance, price per document, and the last 30 days of usage for the account that owns the API key. Read-only. Requires a per-customer API key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_bulk_job ~57

Get the status and per-file results of a bulk extraction job created by submit_bulk_extraction. Read-only and safe to repeat. Requires an API key.

NameTypeReqDescription
job_idstringyesThe job_id returned by submit_bulk_extraction.

No output schema declared.

No examples provided.

submit_bulk_extraction ~157

Submit up to 10 SDS PDFs (public https URLs) as one asynchronous job. Returns a job_id; poll get_bulk_job until status is completed or failed. Reuse the same idempotency_key when retrying so no duplicate job is created. Billed per document from prepaid credit, reserved up front and released for any file that fails. Requires an API key.

NameTypeReqDescription
callback_urlstring–Optional https URL that receives a signed webhook when the job finishes.
file_urlsarrayyesPublic https URLs of SDS PDFs.
idempotency_keystring–Caller-chosen unique key; a repeat returns the existing job.
language_hintstring––
schema_versionstring––

No output schema declared.

No examples provided.

Install

How do I install the SafetyDataSheetAPI MCP server?

SafetyDataSheetAPI is a hosted endpoint at https://safetydatasheetapi.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · safetydatasheetapi.com

# add to Claude Code
claude mcp add --transport http com-safetydatasheetapi-sds-extraction 'https://safetydatasheetapi.com/mcp'
Common questions

What is the SafetyDataSheetAPI MCP server?

SafetyDataSheetAPI is an MCP server listed in the public MCP registry as com.safetydatasheetapi/sds-extraction. Extract safety data sheet (SDS/MSDS) PDFs into a fixed 16-section JSON record. This page covers its hosted endpoint (https://safetydatasheetapi.com/mcp).

Is the SafetyDataSheetAPI MCP server safe to use?

SafetyDataSheetAPI scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the SafetyDataSheetAPI MCP server expose?

SafetyDataSheetAPI exposes 4 tools: extract_sds, submit_bulk_extraction, get_bulk_job, get_account. Their descriptions and schemas cost roughly 453 tokens of context every time the server is loaded.

Does the SafetyDataSheetAPI MCP server require authentication?

No. We connected to SafetyDataSheetAPI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the SafetyDataSheetAPI MCP server still maintained?

SafetyDataSheetAPI is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.