Remote MCP · Endpoint
AstraNL Dutch counterparty check MCP server
No. AstraNL Dutch counterparty check answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://astranl.com/mcp/streamable?profile=counterparty
The last check completed an MCP handshake.
- Registry name
- com.astranl/counterparty-nl
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 274 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- Check a Dutch supplier before you pay: KvK register, name match, VIES VAT, EU sanctions. No key.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 274 ms |
| 1 day ago | Handshake completed | 381 ms |
| 3 days ago | Handshake completed | 272 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.
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 AstraNL Dutch counterparty check and makes no claim about it beyond what these checks measured.