SDSentry — SDS Lookup & OSHA HazCom
REMOTE · SDSENTRY.0XPI.COM · SCANNED SEP 22
Free safety data sheet (SDS) lookup by product name, plus an OSHA HazCom readiness check.
Available components
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 381 tokens (~190/item across 2 items; 2 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the SDSentry — SDS Lookup & OSHA HazCom MCP server?
SDSentry — SDS Lookup & OSHA HazCom is a hosted endpoint at https://sdsentry.0xpi.com/mcp-sds, 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 · sdsentry.0xpi.com
claude mcp add --transport http com-0xpi-sdsentry-sds-lookup 'https://sdsentry.0xpi.com/mcp-sds'
{
"mcpServers": {
"com-0xpi-sdsentry-sds-lookup": {
"url": "https://sdsentry.0xpi.com/mcp-sds"
}
}
} {
"servers": {
"com-0xpi-sdsentry-sds-lookup": {
"type": "http",
"url": "https://sdsentry.0xpi.com/mcp-sds"
}
}
} [mcp_servers.com-0xpi-sdsentry-sds-lookup] url = "https://sdsentry.0xpi.com/mcp-sds"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-0xpi-sdsentry-sds-lookup": {
"type": "remote",
"url": "https://sdsentry.0xpi.com/mcp-sds",
"enabled": true
}
}
} openclaw mcp add com-0xpi-sdsentry-sds-lookup --url 'https://sdsentry.0xpi.com/mcp-sds' --transport streamable-http
mcp_servers:
com-0xpi-sdsentry-sds-lookup:
url: "https://sdsentry.0xpi.com/mcp-sds" {
"McpServers": {
"com-0xpi-sdsentry-sds-lookup": {
"Transport": "http",
"Url": "https://sdsentry.0xpi.com/mcp-sds"
}
}
} assistant mcp add com-0xpi-sdsentry-sds-lookup -t streamable-http -u 'https://sdsentry.0xpi.com/mcp-sds'
{
"mcpServers": {
"com-0xpi-sdsentry-sds-lookup": {
"type": "http",
"url": "https://sdsentry.0xpi.com/mcp-sds"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 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.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
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 22 Sept 2026 · Probed https://sdsentry.0xpi.com/mcp-sds
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sdsentry.0xpi.com | CN=YE1,O=Let's Encrypt,C=US | 28 Jul 2026 | 26 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6b7484aee5dc9f3a4c569f1f21e0b5c9789 |
| SANs: sdsentry.0xpi.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sdsentry.0xpi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| 0xpi.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sdsentry.0xpi.com/mcp-sds | Verified | 200 | |
| http (plaintext) | http://sdsentry.0xpi.com/mcp-sds | HTTPS enforced | 301 | https://sdsentry.0xpi.com/mcp-sds |
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 →
check_hazcom_readiness OSHA HazCom compliance — the deadline and how to check readiness ~127
Explains the OSHA Hazard Communication (HazCom) employer compliance deadline and what a facility that stores chemicals needs in place (current safety data sheets, GHS container labels, a written program, and documented employee training), then points to a free, no-signup readiness self-audit. Does NOT invent fines, statistics, or legal conclusions. Use it when someone asks whether their business is OSHA HazCom compliant or ready for the deadline.
| Name | Type | Req | Description |
|---|---|---|---|
| industry | string | – | Optional: the kind of facility (e.g. "auto repair shop"), used only to tailor the wording. |
No output schema declared.
No examples provided.
find_safety_data_sheet Find a safety data sheet (SDS) for a chemical or product ~133
Look up the manufacturer safety data sheet (SDS/MSDS) for a workplace chemical or product by name. Returns the product name, manufacturer, CAS number(s), EPA registration where applicable, a link to the actual SDS PDF, and a confidence level. If the product cannot be identified reliably it says so plainly rather than guessing — a wrong SDS is worse than none. Free, no signup. Use it when someone needs hazard or handling information, or the SDS, for a chemical they keep on site.
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | yes | The chemical or product name to look up (at least 2 characters). |
No output schema declared.
No examples provided.
What is the SDSentry — SDS Lookup & OSHA HazCom MCP server?
SDSentry — SDS Lookup & OSHA HazCom is an MCP server listed in the public MCP registry as com.0xpi.sdsentry/sds-lookup. Free safety data sheet (SDS) lookup by product name, plus an OSHA HazCom readiness check. This page covers its hosted endpoint (https://sdsentry.0xpi.com/mcp-sds).
Is the SDSentry — SDS Lookup & OSHA HazCom MCP server safe to use?
SDSentry — SDS Lookup & OSHA HazCom scores 83 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 SDSentry — SDS Lookup & OSHA HazCom MCP server expose?
SDSentry — SDS Lookup & OSHA HazCom exposes 2 tools: find_safety_data_sheet, check_hazcom_readiness. Their descriptions and schemas cost roughly 260 tokens of context every time the server is loaded.
Does the SDSentry — SDS Lookup & OSHA HazCom MCP server require authentication?
No. We connected to SDSentry — SDS Lookup & OSHA HazCom without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SDSentry — SDS Lookup & OSHA HazCom MCP server still maintained?
SDSentry — SDS Lookup & OSHA HazCom is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.