Remote MCP · Endpoint
io.bildata/bildata MCP server
No. io.bildata/bildata answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://bildata.io/mcp
The last check completed an MCP handshake.
- Registry name
- io.bildata/bildata
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 149 ms
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Danish vehicle registration tax (registreringsafgift) calculator and DMR registration statistics
- Website
- https://bildata.io/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 149 ms |
| 11 hours ago | Handshake completed | 218 ms |
| 1 day ago | Handshake completed | 165 ms |
| 2 days ago | Handshake completed | 188 ms |
| 4 days ago | Handshake completed | 183 ms |
| 4 days ago | Handshake completed | 175 ms |
| 5 days ago | Handshake completed | 143 ms |
| 6 days ago | Handshake completed | 168 ms |
| 8 days ago | Handshake completed | 168 ms |
| 11 days ago | Handshake completed | 174 ms |
| 13 days ago | Handshake completed | 314 ms |
| 16 days ago | Handshake completed | 213 ms |
| 18 days ago | Handshake completed | 333 ms |
| 20 days ago | Handshake completed | 335 ms |
| 22 days ago | Handshake completed | 192 ms |
| 24 days ago | Handshake completed | 314 ms |
| 26 days ago | Handshake completed | 145 ms |
| 27 days ago | Handshake completed | 134 ms |
| 29 days ago | Handshake completed | 149 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.
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 io.bildata/bildata and makes no claim about it beyond what these checks measured.