Back to Browse

Tracert MCP Server

Developer ToolsUse Caution4.8MCP RegistryRemote
Free

Server data from the Official MCP Registry

Routes other agents mapped for web tasks, so yours verify instead of re-research. Plus free tools.

About

Routes other agents mapped for web tasks, so yours verify instead of re-research. Plus free tools.

Remote endpoints: streamable-http: https://tracert.site/api/mcp

Security Report

4.8
Use Caution4.8High Risk

Tracert is a read-oriented capability registry and MCP gateway whose code shows no exfiltration, hardcoded secrets, or shell execution in the reviewed files. The main points of note are that the hosted gateway performs live outbound fetches for free reads, that the visible code leaves the ownership-verification SSRF defenses truncated and unverified, and that the route-reporting tool writes anonymous analytics events. Permissions broadly match a developer-tools registry and router, so the server scores in the good range with a few items to review. Supply chain analysis found 17 known vulnerabilities in dependencies (2 critical, 8 high severity).

9 files analyzed · 21 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

database

Applies to the server that hosts this plugin, not to your machine.

File System Read

Reads files on the server that hosts it, not on your machine.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "site-tracert-tracert": {
      "url": "https://tracert.site/api/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Tracert

The open route from agent intent to a provable outcome. TRACE = Transparent Registry for Agent Capabilities and Execution.

Tracert is an open capability network: AI agents discover, evaluate and invoke free or pay-per-use services through one interface — with transparent, portable evidence (TRACE Receipts) of what was promised, what was paid and what happened.

Why

As generation makes creation cheap, scarcity moves downstream — to being found, selected, trusted and executed at the moment an agent is completing a task. Tracert is the structured route across that gap. Suppliers publish machine-readable capabilities; buying agents discover them, take an exact quote, invoke, and keep evidence they can re-verify. Tracert exposes inspectable facts and records — it never issues a universal quality score. The requesting agent applies its own policy.

This repository

A monorepo of three independently-runnable parts. Everything the site serves is generated from the registry — there is no hand-maintained marketing for a capability.

DirectoryWhat it isRun it
registry/The control plane: TRACE Manifest & Receipt JSON Schemas, capability manifests, validator and machine-export generators.cd registry && npm ci && npm run build
router/The five-tool MCP server — search_capabilities, get_capability, get_quote, invoke_capability, get_execution — over the registry, emitting verifiable receipts.cd router && npm ci && npm test
site/tracert.site: human routes (about / publish / use), an agent entry point, capability pages, and machine endpoints — all generated from the registry.cd site && npm ci && npm run build

Additional docs: docs/capabilities/ — normative execution contracts per capability.

The loop

publish → discover → evaluate → quote → invoke → pay (if priced) → prove → repeat

A capability is one bounded promise with a clear contract (registry/schemas/manifest.schema.json). An execution ends in an explicit terminal state and a TRACE Receipt (registry/schemas/receipt.schema.json) whose sha256 commitments over canonical request and output — plus public artifacts like a merged pull request or a live page — anyone can verify independently.

Verify it yourself

# validate every manifest against the schemas
cd registry && npm ci && npm run build

# drive the MCP router end-to-end (simulated adapter, no external writes)
cd router && npm ci && npm test

The router's live adapter is off by default: invoking a capability that writes external state (like publishing a public listing) refuses unless explicitly enabled, because the write is outward-facing and permanent. See router/README.md.

Design principles

  • Evidence over verdicts — raw claims, timestamps, hashes and execution records; no platform-owned trust score.
  • No wallet for free value — free listings and executions never touch payment infrastructure.
  • Open control plane, replaceable data plane — portable, forkable registry and schemas; gateways can compete or be self-hosted.
  • Terminal states only — every execution reaches an explicit state with machine-actionable reasons.
  • Reuse, don't capture — composes with MCP, A2A, MPP, x402 and AP2; internal identifiers stay network- and processor-agnostic.

Contributing a capability

Copy registry/templates/example-provider/ to registry/providers/<your-id>/, fill it in, run npm run validate in registry/, and open a pull request. Free capabilities are first-class and need no wallet. Full guide: registry/CONTRIBUTING.md · also registry/README.md and tracert.site/publish.

The registry ships empty — a clean slate. The first capability is one pull request away.

Status

Early. Live today: the TRACE contracts, the public registry with its first active capability, and the five-tool router verified end-to-end. Next: a hosted MCP endpoint and pay-per-use capabilities behind a method-agnostic payment adapter (MPP + x402), plus demand benchmarks across agent environments.

License

MIT.

Reviews

No reviews yet

Be the first to review this server!