Remote MCP · Endpoint

CAZ Cost MCP server

No. CAZ Cost answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://caz-cost.rowb.app/mcp

The last check completed an MCP handshake.

Registry name
app.rowb.caz-cost/zones
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
427 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
UK Clean Air Zone daily charges by council, per vehicle class, and what a trip costs.
Listing
From the official MCP registry (active).
Recent checks of CAZ Cost
CheckedResultHandshake
7 hours agoHandshake completed427 ms
4 days agoHandshake completed943 ms
14 days agoHandshake completed449 ms
15 days agoHandshake completed638 ms
15 days agoHandshake completed589 ms
17 days agoHandshake completed440 ms
18 days agoHandshake completed1.02 s
19 days agoHandshake completed446 ms
20 days agoHandshake completed451 ms
21 days agoHandshake completed460 ms
23 days agoHandshake completed1.51 s
26 days agoHandshake completed625 ms
28 days agoHandshake completed402 ms

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

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