Remote MCP · Endpoint
Structured Data Check MCP server
No. Structured Data Check answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://structured-data-check.david-cyr.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.Dawaxwx/structured-data-check
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 790 ms
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 58.8% from 17 checks
- Described by its publisher as
- Structured data validator in one call: extracts JSON-LD, microdata and RDFa from a URL or raw HTM...
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 790 ms |
| 2 days ago | Handshake completed | 394 ms |
| 4 days ago | Handshake completed | 374 ms |
| 5 days ago | Handshake completed | 410 ms |
| 7 days ago | Handshake completed | 324 ms |
| 8 days ago | Handshake completed | 435 ms |
| 9 days ago | Failed - the server returned an HTTP error | — |
| 12 days ago | Failed - the server returned an HTTP error | — |
| 13 days ago | Failed - the server returned an HTTP error | — |
| 15 days ago | Handshake completed | 849 ms |
| 17 days ago | Failed - the server returned an HTTP error | — |
| 18 days ago | Failed - the server returned an HTTP error | — |
| 19 days ago | Failed - the server returned an HTTP error | — |
| 20 days ago | Handshake completed | 569 ms |
| 20 days ago | Handshake completed | 913 ms |
| 21 days ago | Handshake completed | 606 ms |
| 23 days ago | Failed - the server returned an HTTP error | — |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 10 responding of 17.
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 Structured Data Check and makes no claim about it beyond what these checks measured.