Remote MCP · Endpoint

SafetyDataSheetAPI MCP server

No. SafetyDataSheetAPI answered an MCP handshake 33 minutes ago.

UpLast checked 33 minutes ago

Server URL

https://safetydatasheetapi.com/mcp

The last check completed an MCP handshake.

Registry name
com.safetydatasheetapi/sds-extraction
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
150 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Extract safety data sheet (SDS/MSDS) PDFs into a fixed 16-section JSON record.
Listing
From the official MCP registry (active).
Recent checks of SafetyDataSheetAPI
CheckedResultHandshake
33 minutes agoHandshake completed150 ms
3 days agoHandshake completed220 ms
13 days agoHandshake completed184 ms
13 days agoHandshake completed179 ms
15 days agoHandshake completed256 ms
16 days agoHandshake completed209 ms
17 days agoHandshake completed225 ms
18 days agoHandshake completed183 ms
18 days agoHandshake completed198 ms
20 days agoHandshake completed405 ms
22 days agoHandshake completed416 ms
25 days agoHandshake completed144 ms

The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 12.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with SafetyDataSheetAPI and makes no claim about it beyond what these checks measured.