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
- 526 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 100% from 18 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 | 526 ms |
| 1 day ago | Handshake completed | 697 ms |
| 2 days ago | Handshake completed | 227 ms |
| 3 days ago | Handshake completed | 601 ms |
| 4 days ago | Handshake completed | 547 ms |
| 5 days ago | Handshake completed | 681 ms |
| 6 days ago | Handshake completed | 556 ms |
| 9 days ago | Handshake completed | 676 ms |
| 11 days ago | Handshake completed | 529 ms |
| 14 days ago | Handshake completed | 583 ms |
| 16 days ago | Handshake completed | 688 ms |
| 18 days ago | Handshake completed | 538 ms |
| 20 days ago | Handshake completed | 559 ms |
| 22 days ago | Handshake completed | 560 ms |
| 24 days ago | Handshake completed | 533 ms |
| 26 days ago | Handshake completed | 533 ms |
| 27 days ago | Handshake completed | 559 ms |
| 28 days ago | Handshake completed | 472 ms |
The last 18 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 Boundr and makes no claim about it beyond what these checks measured.