Tracert

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as site.tracert/tracert and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 8 Nov 2026. Not supplied by the maker.

• search_capabilities

  Find an external service that can complete an outcome your current tools cannot — data lookups, media transformations and other real-world tasks, free or pay-per-use. Returns a small candidate set wit

• get_capability

  Retrieve the full TRACE Manifest for one capability: promise and exclusions, input/output JSON Schemas, interfaces, pricing, operational facts, data-handling declarations, evidence and provenance. Cal

• get_quote

  Returns exact, expiring terms for one intended invocation: amount, currency, expiry and payment offers. Free capabilities return an explicit zero quote — no wallet or payment handshake is ever require

• invoke_capability

  Executes a free read and returns a TRACE Receipt binding the request, terms, outcome and evidence (with a sha256 commitment over the canonical output you can independently reproduce). This hosted gate

• get_execution

  Fetch the TRACE Receipt for an execution_id: status, commitments, artifacts and evidence. The hosted gateway retains receipts only within a warm instance — the invoke response returns the full receipt

• find_routes

  Call this BEFORE researching or comparing several websites — finding suppliers or services, getting quotes or prices, finding where to list or launch something, or working out a site's sign-up/upload

• get_route

  The full route as Markdown: TL;DR, Verify-first checks, per-site facts (access, offers, how, gotchas), dead ends, observed prices, prep checklist and what needs a human. Every fact is dated and labell

• report_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-char note on what changed. Takes one call; it keeps routes fresh