mcp-registry/app.rowb.caz-cost/zones · v1.0.0
As of 2026-10-26 19:10 UTC, the Rowb Caz Cost Zones MCP server is up with a Glimind reliability score of 78/100 (grade B). Over the last 30 days it answered 99.1% of Glimind's liveness checks. It had 16 outages in 90 days, with a median recovery of 4 minutes.
UK Clean Air Zone daily charges by council, per vehicle class, and what a trip costs.
Point your MCP client at this streamable-http endpoint: https://caz-cost.rowb.app/mcp
3 of 3 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
1 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fapp.rowb.caz-cost%2Fzones/fixes
{
"name": "list_zones",
"description": "List every UK Clean Air Zone with the daily charge each council publishes, per vehicle class, plus the London Congestion Charge and ULEZ which are separate schemes.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "zone_charges",
"description": "Get one zone by id: its daily charge for each vehicle class, its notes, its penalty figures and the source URLs the numbers came from.",
"inputSchema": {
"type": "object",
"required": [
"zone"
],
"properties": {
"zone": {
"type": "string",
"description": "Zone id, e.g. birmingham, bristol, bradford, bath, portsmouth, sheffield, tyneside, london-cc, london-ulez"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/app.rowb.caz-cost/zones"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/app.rowb.caz-cost/zones"}) over MCP.
trip_cost ~166 tokenszone_charges ~117 tokenslist_zones ~78 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fapp.rowb.caz-cost%2Fzones?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fapp.rowb.caz-cost%2Fzones?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.rowb.caz-cost%2Fzones.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.rowb.caz-cost%2Fzones.svg :target: https://glimind.com/server/mcp-registry%2Fapp.rowb.caz-cost%2Fzones?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:69ee800d1cf1f0cc…, first seen 2026-10-17, included at leaf 10970 of 74,955. Version history · verify what your client received.
Compare: most reliable data servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 19:10 UTC, the Rowb Caz Cost Zones MCP server is up with a Glimind reliability score of 78/100 (grade B). Over the last 30 days it answered 99.1% of Glimind's liveness checks. It had 16 outages in 90 days, with a median recovery of 4 minutes.
Rowb Caz Cost Zones MCP server advertises 3 tools, including list_zones, trip_cost, zone_charges.
Point your MCP client at this streamable-http endpoint: https://caz-cost.rowb.app/mcp
Glimind scanned all 3 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.