Remote MCP · Endpoint
Boundr MCP server
No. Boundr answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.boundr.dev/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.danielinniss/boundr
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 559 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 100% from 17 checks
- Described by its publisher as
- UK administrative boundary data from OS Boundary Line: name search, point lookup, GeoJSON geometries
- Website
- https://boundr.dev/
- Repository
- https://github.com/danielinniss/boundr
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 559 ms |
| 2 days ago | Handshake completed | 560 ms |
| 4 days ago | Handshake completed | 533 ms |
| 5 days ago | Handshake completed | 533 ms |
| 7 days ago | Handshake completed | 559 ms |
| 8 days ago | Handshake completed | 472 ms |
| 9 days ago | Handshake completed | 536 ms |
| 12 days ago | Handshake completed | 536 ms |
| 13 days ago | Handshake completed | 544 ms |
| 15 days ago | Handshake completed | 613 ms |
| 16 days ago | Handshake completed | 561 ms |
| 18 days ago | Handshake completed | 523 ms |
| 19 days ago | Handshake completed | 535 ms |
| 20 days ago | Handshake completed | 527 ms |
| 20 days ago | Handshake completed | 533 ms |
| 21 days ago | Handshake completed | 534 ms |
| 22 days ago | Handshake completed | 804 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 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 Boundr and makes no claim about it beyond what these checks measured.