Remote MCP · Endpoint

Wozapi MCP server

No. Wozapi answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://woz-api.nl/Api/Mcp

The last check completed an MCP handshake.

Registry name
nl.woz-api/wozapi
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
404 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
WOZ values (official Dutch property valuations) for Dutch addresses, one lookup or a whole list.
Listing
From the official MCP registry (active).
Recent checks of Wozapi
CheckedResultHandshake
6 hours agoHandshake completed404 ms
9 days agoHandshake completed409 ms
10 days agoHandshake completed455 ms
11 days agoHandshake completed389 ms
12 days agoHandshake completed432 ms
14 days agoHandshake completed443 ms
15 days agoHandshake completed497 ms
15 days agoHandshake completed424 ms
17 days agoHandshake completed556 ms
19 days agoHandshake completed465 ms
22 days agoHandshake completed378 ms
24 days agoHandshake completed503 ms
26 days agoHandshake completed450 ms
28 days agoHandshake completed401 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 26 responding of 26.

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 Wozapi and makes no claim about it beyond what these checks measured.