com.tunnelpowered/knowledge-base
v1.1.0Search verified local businesses, check what their verification proves, and message them.
Endpoint health
online- Last checked
- 11/20/2026, 8:18:00 AM
- Latency
- 378 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.tunnelpowered%2Fknowledge-base
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.tunnelpowered/knowledge-base": {
"url": "https://api.tunnelpowered.com/api/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
17 shown · authentication unknown
ask_business
Ask one specific question about a listing and get an answer from the registry, with no human involved. Try this before contact_business: it is instant, free, and does not put a message in someone's inbox. Returns either an answer or an escalation. When `resolved` is true, `answer` holds it and `basis` names the fields it was read from. When `escalate` is true we do not hold the fact — this is NOT a negative answer, and in particular an unlisted place is "we do not know", never "they do not deliver there". Only the business can declare its own list complete. Unsupported questions come back with `refused` true and a `supported` list rather than a guess: nothing here is ever inferred, approximated or improvised. Authentication: none. This tool works with no credentials.
Schema valid · SHA-256 78b4a7fce721…
View input schema
{ "type": "object", "properties": { "slug": { "type": "string", "description": "The `slug` field from a search_businesses result." }, "kind": { "type": "string", "enum": [ "entity", "website" ], "description": "The `kind` field from the same search result." }, "intent": { "type": "string", "enum": [ "is_open_now", "delivers_to", "lead_time" ], "description": "Which question to ask. \"is_open_now\" needs nothing else; \"delivers_to\" needs a `params` place; \"lead_time\" asks the shortest notice they accept an order on." }, "params": { "type": "object", "description": "Arguments for the question. For \"delivers_to\": { \"place\": \"Botanica\" }. Ignored by the others." } }, "required": [ "slug", "kind", "intent" ] }ask_business_freeform
Same answers as ask_business, but you send the person's own words instead of choosing an intent, and the reply comes back in the language they used. Supported languages: en, ro, ru, de; anything else is answered in English. Prefer ask_business when you already know which of the three questions you are asking — it is instant and costs nothing, whereas this one runs a model to read the question and is rate-limited accordingly. A model is used ONLY to decide which question was asked and in which language. It never sees the business's stored data and never writes the answer. Returns an `outcome` and a `reply` in the asker's language. Branch on `outcome`, not on the prose: "answered" carries `reply` and a structured `answer`; "needs_detail" means we need one more thing from the asker and `reply` requests it; "not_understood" means it was not one of our three questions, with `supported` listing them; "escalated" means a real question we do not hold the fact for — we forward that one to the business ourselves, and `escalation` carries the `ref` that reads their answer later with check_escalation. `handoff` still holds what was gathered, for contact_business. An escalation is never a negative answer. Authentication: none. This tool works with no credentials.
Connections
streamable-http
https://api.tunnelpowered.com/api/mcp