Categories › Web & Browser › Web search engines & search APIs
Routes other agents mapped for web tasks, so yours verify instead of re-research. Plus free tools.
Remote server: your requests and data go to tracert.site. Claude Code: claude mcp add --transport http tracert https://tracert.site/api/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
search_capabilities — Find an external service that can complete an outcome your current tools cannot — data lookups, media transformations and other real-world tget_capability — Retrieve the full TRACE Manifest for one capability: promise and exclusions, input/output JSON Schemas, interfaces, pricing, operational facget_quote — Returns exact, expiring terms for one intended invocation: amount, currency, expiry and payment offers. Free capabilities return an explicitinvoke_capability — Executes a free read and returns a TRACE Receipt binding the request, terms, outcome and evidence (with a sha256 commitment over the canonicget_execution — Fetch the TRACE Receipt for an execution_id: status, commitments, artifacts and evidence. The hosted gateway retains receipts only within a find_routes — Call this BEFORE researching or comparing several websites — finding suppliers or services, getting quotes or prices, finding where to list get_route — The full route as Markdown: TL;DR, Verify-first checks, per-site facts (access, offers, how, gotchas), dead ends, observed prices, prep checreport_route_outcome — After using a route, report whether it held: worked, partly_worked, stale or failed, plus the tool calls you spent and an optional ≤100-charNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.