mcp-registry/uk.co.towingcapacitychecker/site · registry v1.0.1 · server reports v1.0.0
claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clientsAs of 2026-11-22 18:42 UTC, the Co Towingcapacitychecker Site MCP server is up with a Glimind reliability score of 82/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 73 outages in 90 days, with a median recovery of 5 minutes.
Towing Capacity Checker: the site's own MCP server — checker, enquiry (enquiry = a human...
Point your MCP client at this streamable-http endpoint: https://towingcapacitychecker.co.uk/mcp
6 of 6 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 →
2 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%2Fuk.co.towingcapacitychecker%2Fsite/fixes
{
"name": "checker_answer",
"description": "Given a question id and the chosen option (its `choice` index), return the next question or the final verdict.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"question",
"choice"
],
"properties": {
"choice": {
"type": "integer",
"minimum": 0
},
"question": {
"type": "string",
"minLength": 1
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Answer a question, get the next step"
}{
"name": "checker_start",
"description": "The first question of the Towing capacity checker decision guide.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
},
"annotations": {
"readOnlyHint": true
},
"title": "Start: Towing capacity checker"
}{
"name": "checker_tree",
"description": "Every question, option and verdict of the Towing capacity checker guide, for reasoning end to end.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
},
"annotations": {
"readOnlyHint": true
},
"title": "The whole decision tree"
}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/uk.co.towingcapacitychecker/site"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/uk.co.towingcapacitychecker/site"}) over MCP.
submit_enquiry ~364 tokensenquiry_describe ~124 tokenschecker_answer ~110 tokensenquiry_fields ~94 tokenschecker_tree ~67 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.
Shows whether the server is live and its agent-readiness score; it updates within the hour.
[](https://glimind.com/server/mcp-registry%2Fuk.co.towingcapacitychecker%2Fsite?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fuk.co.towingcapacitychecker%2Fsite?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fuk.co.towingcapacitychecker%2Fsite.svg" alt="MCP server status"></a>
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:e4b1874ddced0eec…, first seen 2026-11-12, included at leaf 238050 of 384,897. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable other 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?ref=install-server
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp?ref=install-server"
}
}
}
A free Glimind key lets your agent check whether a server works right now before it calls it, and switch to a live one when it doesn't. No signup, no card.
As of 2026-11-22 18:42 UTC, the Co Towingcapacitychecker Site MCP server is up with a Glimind reliability score of 82/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 73 outages in 90 days, with a median recovery of 5 minutes.
Co Towingcapacitychecker Site MCP server advertises 6 tools, including checker_answer, checker_start, checker_tree, enquiry_describe, enquiry_fields.
Point your MCP client at this streamable-http endpoint: https://towingcapacitychecker.co.uk/mcp
Glimind scanned all 6 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.