Remote MCP · Endpoint
Public Data Catalog MCP server
No. Public Data Catalog answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://public-data-catalog-mcp.yusuke8h.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.yhay81/public-data-catalog
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 338 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Reviewed public-data search and execution with provenance and verifiable integrity receipts.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 338 ms |
| 1 day ago | Handshake completed | 395 ms |
| 2 days ago | Handshake completed | 190 ms |
| 3 days ago | Handshake completed | 660 ms |
| 4 days ago | Handshake completed | 170 ms |
| 5 days ago | Handshake completed | 279 ms |
| 6 days ago | Handshake completed | 354 ms |
| 8 days ago | Handshake completed | 241 ms |
| 11 days ago | Handshake completed | 192 ms |
| 13 days ago | Handshake completed | 435 ms |
| 15 days ago | Handshake completed | 452 ms |
| 18 days ago | Handshake completed | 235 ms |
| 20 days ago | Handshake completed | 359 ms |
| 22 days ago | Handshake completed | 250 ms |
| 24 days ago | Handshake completed | 380 ms |
| 26 days ago | Handshake completed | 201 ms |
| 27 days ago | Handshake completed | 206 ms |
| 28 days ago | Handshake completed | 230 ms |
| 29 days ago | Handshake completed | 326 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 Public Data Catalog and makes no claim about it beyond what these checks measured.