A remote MCP server that extracts Safety Data Sheet (SDS/MSDS) PDFs into normalized 16-section JSON records with confidence scores and warnings.
What you can do
Extract a single SDS PDF into a normalized 16-section record with a confidence score and warnings, from a public URL or base64 file content. Submit up to 10 SDS PDFs as one asynchronous bulk job and poll its status and per-file results. Check the account's prepaid credit balance, price per document and last 30 days of usage.
When to use it
Useful when an assistant needs to turn supplier safety data sheets into structured hazard, composition, first aid, transport and regulatory fields, either one document at a time or in small batches, for review or downstream processing.
Requirements
A remote streamable HTTP endpoint; no local runtime. Tool listing works without a key, but tool calls need a per-customer API key sent as an Authorization Bearer header, with prepaid credit on the account. PDFs are supplied as public https URLs or base64 content.
Before you install
Calls are billed per document from prepaid credit, reserved up front for bulk jobs; a 402 insufficient_credit error means credit must be added. The API key is a secret sent in the Authorization header. Results with warnings or a low confidence score should go to human review before compliance decisions, and submitted PDFs are sent to a third-party service.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.safetydatasheetapi%2Fsds-extraction/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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.
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.
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.
Parametersjob_idrequired
get_account
Get account balance and usage
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.
Takes no parameters.
Version history
1
v1.1.0LatestOct 25, 2026
Score
72%
72% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Publish an icon in the registry entry.
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.