Data Collection

tunnelpowered.com

A server that provides business lookup, verification checks, and Q&A about merchant listings from a registry.

1 endpoint17 known toolsFirst detected August 28, 2026Last detected August 28, 2026

ENDPOINT 1

https://api.tunnelpowered.com/api/mcp

No auth detected

MCP server metadata

Name: tunnel-knowledge-base
Version: 1.1.0

Capabilities

tools

Server instructions

Knowledge base of businesses, merchants and websites — including merchants who have no website and are listed from their social presence — plus a way to message the people behind them. Reading is open: search_businesses, get_business and check_merchant_verification need no account, no key and no registration. Only writing to a business does. Normal sequence: search_businesses to get a `slug`, then get_business for the profile, then check_merchant_verification before relying on anything consequential. Every answer is wrapped. `tunnel_mcp` is the schema version, `retrieved_at` is when we answered, `freshness` is when the underlying data was actually observed, and `completeness` with `missing` tells you what is absent. An empty field means we do not hold that information — it does not mean the business lacks it. Say which one you mean if it affects your answer. Verification has two levels and they are not the same claim. Read `verification.level`. Do not infer verification from the existence of a record: most records are not verified at all, and an "automated" one proves only that the business controls its own domain, inbox or social accounts. Neither level says anything about quality. Errors carry a stable `code` and a `fix` naming the call to make instead. Branch on `code` rather than parsing the message. Please send a descriptive User-Agent. It raises no limit and is never checked — it only lets us tell agent traffic apart from noise when we report on who uses this. Plain-REST equivalent of everything above: https://api.tunnelpowered.com/api/kb/llms.txt

Known tools 17

search_businesses

Find businesses, merchants and websites in the tunnel knowledge base by name or topic.

Inferred read-only

get_business

Read the full profile of one business.

Inferred read-only

check_merchant_verification

Check live what a merchant has actually been verified to, and by whom.

Inferred read-only

ask_business

Ask one specific question about a listing and get an answer from the registry, with no human involved.

Inferred read-only

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.

Potential side effects

check_escalation

Read the answer to a question that had to go to a human.

Inferred read-only

check_commitment

Read a commitment you were given by commit_order, including whether the business has since withdrawn it.

Inferred read-only

get_rate_card

Read the prices a business has authorised us to quote on their behalf.

Inferred read-only

request_quote

Price a specific set of line items against a business's rate card.

Inferred read-only

check_availability

Find out when a business is actually free.

Inferred read-only

commit_order

Place a binding order with a business, inside limits they set in advance.

Inferred read-only

cancel_order

Cancel an order you placed with commit_order.

Inferred read-only

reschedule_order

Move an order you placed to a different date, or a booking to a different slot.

Inferred read-only

request_order_change

Raise anything else about an order that already exists: a change to what was ordered, a refund request, or a problem with what was delivered.

Potential side effects

contact_business

Open a conversation with the person behind a listing.

Inferred read-only

check_replies

Read a conversation you opened with contact_business, including anything the business has replied since.

Inferred read-only

send_followup

Add another message to a conversation already opened with contact_business.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.tunnel-knowledge-base]
url = "https://api.tunnelpowered.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "tunnel-knowledge-base": {
      "type": "http",
      "url": "https://api.tunnelpowered.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: tunnel-knowledge-base
Remote MCP URL: https://api.tunnelpowered.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "tunnel-knowledge-base": {
      "url": "https://api.tunnelpowered.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "tunnel-knowledge-base": {
      "type": "http",
      "url": "https://api.tunnelpowered.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "tunnel-knowledge-base",
  "transport": "streamable-http",
  "url": "https://api.tunnelpowered.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.