TunnelMind Data API
v1.0.1Tracker / Sigil / Cross-lens — every TunnelMind Data API operation as one MCP surface.
Endpoint health
online- Last checked
- 11/20/2026, 5:17:05 AM
- Latency
- 56 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:ai.tunnelmind%2Fdata
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"ai.tunnelmind/data": {
"url": "https://mcp-data.tunnelmind.ai/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
25 shown · authentication unknown
agent_record
Spec 125. One agent public key's record across attested Fareseal sites: summed requests, a sample of paths, whether robots.txt was fetched, the signed snapshots each figure comes from (`sources[]`), and the newest 100 receipts naming the key, verbatim. Free, no auth. Facts, not verdicts: no score, no tier, no IP. Counts are a LOWER BOUND. The cache is not the record — `verify` says how to recompute every sum from `fareseal_export` and check each source's sig. Use this tool when: - You want what the commons has observed of a specific agent key. - You are auditing an agent's conduct and want to check it yourself. Returns: - `key`, `ua`, `requests`, `isolates`, `first_seen`, `last_seen`, `paths[]` (capped), `robots_txt_fetched`. - `sources[]`: `{site, isolate_id, seq, taken_at, sig}`. - `paid`, `receipts_total`, `receipts[]` (each `receipt` verbatim as signed), plus the honesty fields. - 404 for a key with nothing attested: the same record, empty, in `error.record`. Cost: - Free. Anonymous 10/min per IP, no daily cap. Latency: - Typical: <150ms.
Schema valid · SHA-256 d1be049c9759…
View input schema
{ "type": "object", "properties": { "key": { "type": "string", "pattern": "^[A-Za-z0-9_-]{43}$", "description": "Agent Ed25519 public key, 43-character base64url (no padding)." } }, "required": [ "key" ] }agent_registries_lookup
P75 registry aggregation: the cross-lens join applied to agent identity. Incumbent providers each consult only their own registry; this endpoint checks every registry TunnelMind can reach and labels each answer with an explicit state, so a gap can never be mistaken for a clean result: - `observed` — the subject IS in this registry (record attached) - `not_present` — checked, and it isn't (an observation, not a gap) - `not_applicable` — the registry doesn't key on this subject type - `degraded` — the check failed (timeout, upstream error) - `unavailable` — the registry is not publicly consultable (closed / platform-scoped); stated in-band because silence would read as clean Registries (v0): `crawler_ranges` (operator-published IP feeds — Googlebot, GPTBot, PerplexityBot…), `wba_directory` (RFC 9421 Signature-Agent JWKS at the subject domain), `mcp_registry` (registry.modelcontextprotocol.io), `tunnelmind_known_agents` (curated verifiable/claim-only set), plus honest `unavailable` rows for Visa TAP, Mastercard Agent Pay, and Cloudflare Verified Bots. Use this tool when: - You are deciding whether an agent, bot, or MCP server is registered anywhere that vouches for it — in one call instead of five. - You need the blind spots stated: which registries could NOT be consulted for this subject, and why. Inputs: subject — an IP (registry membership by published ranges), a domain (WBA directory + MCP registry), or an agent name/UA fragment (e.g. `gptbot`, `claudebot`). `?receipt=true` attaches a signed Receipt v1.0 committed to the transparency log. Latency: remote registry checks are KV-cached for 1h; a warm call is edge-fast, a cold one bounded by 5s per-registry timeouts.
Connections
streamable-http
https://mcp-data.tunnelmind.ai/mcp