mcp-registry/com.tunnelpowered/knowledge-base · v1.1.0
As of 2026-10-22 23:03 UTC, the Tunnelpowered Knowledge Base MCP server is up with a Glimind reliability score of 74/100 (grade C). Over the last 30 days it answered 99.3% of Glimind's liveness checks. It had 43 outages in 90 days, with a median recovery of 6 minutes.
Search verified local businesses, check what their verification proves, and message them.
Claude Code
claude mcp add --transport http tunnelpowered-knowledge-base-mcp-server https://api.tunnelpowered.com/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"tunnelpowered-knowledge-base-mcp-server": {
"type": "http",
"url": "https://api.tunnelpowered.com/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
17 of 17 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 →
5 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 →
Handshake + tools/list takes ~1,968 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
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. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.tunnelpowered%2Fknowledge-base/fixes
{
"name": "cancel_order",
"description": "Cancel an order you placed with commit_order. Returns `settled`. True means it is cancelled, the business has been told and their day is free again. False comes with a `reason`: \"inside-cancel-window\" (later notice than they said they need), \"no-cancel-window-set\" (they never said), \"order-passed\", \"not-open\" (already cancelled or withdrawn) or \"not-the-issuing-agent\". Every reason but the last two puts the request in front of the business and returns an `escalation` to poll with check_escalatio",
"inputSchema": {
"type": "object",
"required": [
"ref"
],
"properties": {
"ref": {
"type": "string",
"description": "The `ref` returned by commit_order. It is the only handle on this order."
},
"note": {
"type": "string",
"description": "Optional. Why, in the buyer's own words. Recorded, shown to the business and carried into the question if a person has to decide. Never parsed, and it cannot change the answer."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}{
"name": "check_availability",
"description": "Find out when a business is actually free. Worked out per call against their opening hours, their notice period, their blackout dates and what is already booked — there is no stored list of free times to be out of date. Returns `known` true with `days`, each holding `slots` that carry a start, an end and `free`. `firstFree` is the earliest one across the range. Pass `time` to ask about one exact moment instead of browsing. `known` false means this business has not set up a calendar and `reason` ",
"inputSchema": {
"type": "object",
"required": [
"slug"
],
"properties": {
"days": {
"type": "number",
"description": "Optional. How many days to walk, 1 to 14. Defaults to 7."
},
"from": {
"type": "string",
"description": "Optional. First day to look at, yyyy-mm-dd in the business's own local calendar. Defaults to their today."
},
"kind": {
"enum": [
"entity",
"website"
],
"type": "string",
"description": "Optional. The `kind` field from the same search result. Defaults to \"entity\"."
},
"slug": {
"type": "string",
"description": "The `slug` field from a search_businesses result."
},
"time": {
"type": "string",
"description": "Optional. One exact start time as HH:MM, 24-hour, on the first day of the range. The answer comes back under `asked`, and \"not-a-slot-start\" means their day divides differently — the free starts are listed beside it."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "check_commitment",
"description": "Read a commitment you were given by commit_order, including whether the business has since withdrawn it. Returns `state`: \"issued\" means it stands, \"repudiated\" means the business said they cannot honour it, with their stated reason. A withdrawal does not erase the original — both are on the record, timestamped. Check this before acting on a commitment made some time ago. Authentication: none. This tool works with no credentials.",
"inputSchema": {
"type": "object",
"required": [
"ref"
],
"properties": {
"ref": {
"type": "string",
"description": "The `ref` returned by commit_order. It is the only way to read this commitment."
}
}
},
"annotations": {
"readOnlyHint": true
}
}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/com.tunnelpowered/knowledge-base"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.tunnelpowered/knowledge-base"}) over MCP.
commit_order ~708 tokensrequest_quote ~450 tokensask_business_freeform ~432 tokenssearch_businesses ~379 tokenscheck_availability ~378 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%2Fcom.tunnelpowered%2Fknowledge-base?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.tunnelpowered%2Fknowledge-base?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.tunnelpowered%2Fknowledge-base.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.tunnelpowered%2Fknowledge-base.svg :target: https://glimind.com/server/mcp-registry%2Fcom.tunnelpowered%2Fknowledge-base?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:7f8034b7f5f3b97e…, first seen 2026-10-17, included at leaf 16830 of 48,647. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable commerce servers · most reliable calendar servers · most reliable other servers · most reliable retrieval 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-22 23:03 UTC, the Tunnelpowered Knowledge Base MCP server is up with a Glimind reliability score of 74/100 (grade C). Over the last 30 days it answered 99.3% of Glimind's liveness checks. It had 43 outages in 90 days, with a median recovery of 6 minutes.
Tunnelpowered Knowledge Base MCP server advertises 17 tools, including ask_business, ask_business_freeform, cancel_order, check_availability, check_commitment.
Point your MCP client at this streamable-http endpoint: https://api.tunnelpowered.com/api/mcp
Glimind scanned all 17 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.