Tracert MCP server
Commit Nov 15, 2026Provides a registry of agent capabilities and machine-readable manifests to allow agents to verify existing routes instead of re-researching tasks.
Also known as tracert-network/tracert
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.2.0
- Last commit
- Nov 15, 2026
- License
- MIT
What is Tracert MCP?
Tracert provides a registry of agent capabilities and machine-readable manifests to allow agents to verify existing routes instead of re-researching tasks.
Summary generated from the project's README
About Tracert MCP server
Verifying existing agent capabilities and machine-readable routes without re-researching tasks is what Tracert enables for developers building autonomous systems. It provides a centralized registry of capabilities that agents can query to confirm what tools or services are available. By using machine-readable manifests, an AI client can check specific capabilities via dedicated endpoints instead of performing expensive or redundant searches.
Users interact with the system through various machine-facing routes, including an index.json snapshot of the entire registry and individual manifest.json files for specific capabilities. The system serves specialized files like llms.txt for language model summarization and provides JSON schemas for both TRACE Manifests and TRACE Receipts. This setup allows agents to verify status, pricing, and media types directly from the source. Because the site is a fully static Next.js application, it delivers these manifests with high reliability and speed.
Written from the project's README. Every use case is checked against a quote from it.
How to install Tracert MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Tracert MCP in Claude Code
$ claude mcp add --transport http tracert https://tracert.site/api/mcpInstall Tracert MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"tracert": {
"url": "https://tracert.site/api/mcp"
}
}
}Install Tracert MCP in VS Code
.vscode/mcp.json
{
"servers": {
"tracert": {
"type": "http",
"url": "https://tracert.site/api/mcp"
}
}
}Install Tracert MCP in VS Code CLI
$ code --add-mcp '{"name":"tracert","type":"http","url":"https://tracert.site/api/mcp"}'Install Tracert MCP in Codex
$ codex mcp add tracert --url https://tracert.site/api/mcpInstall Tracert MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.tracert] url = "https://tracert.site/api/mcp"
Install Tracert MCP in Gemini CLI
$ gemini mcp add -s user --transport http tracert https://tracert.site/api/mcpInstall Tracert MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"tracert": {
"url": "https://tracert.site/api/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachabletracert-network/tracert is public and reachablegithub.com/tracert-network/tracert ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-14github.com/tracert-network/tracert ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 147 msPass
README
View on GitHubtracert.site
The public face of Tracert — human routes, an agent entry point, capability pages and machine exports, all generated from the registry at build time. No hand-maintained marketing for a capability: every fact on a capability page comes from its TRACE Manifest.
Next.js (App Router), fully static. Zero UI dependencies; a small hand-rolled design system that adapts to light and dark.
Develop
npm ci
npm run dev # http://localhost:3000
npm run build # static export of every route
The site reads the registry from a sibling ../registry by default. Point elsewhere with TRACERT_REGISTRY_DIR. After changing manifests, rebuild — pages are baked at build time.
Routes
Human: / (routes fork for humans vs agents) · /about · /publish · /use · /capabilities · /capabilities/<id>
Machine:
| URL | Serves |
|---|---|
/llms.txt |
This site, summarized for language models |
/index.json |
The registry snapshot — every capability with status, pricing, media types, manifest URL |
/schemas/manifest/v0.1 |
TRACE Manifest JSON Schema (served at its own $id) |
/schemas/receipt/v0.1 |
TRACE Receipt JSON Schema (served at its own $id) |
/capabilities/<id>/manifest.json |
One capability's canonical manifest, with an X-Tracert-Manifest-Hash header |
Deploy (Vercel)
The app lives in this site/ subdirectory of the monorepo. In the Vercel project, set Root Directory = site; the framework preset is Next.js. The build reads ../registry, which the registry-directory resolver locates from either the site root or the repository root — no extra configuration required. See ../DEPLOY.md.
Tracert MCP questions
How do I add Tracert MCP to Claude Code?
Run claude mcp add --transport http tracert https://tracert.site/api/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Tracert MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How can language models consume the site information?
Language models can access a summarized version of the site via the /llms.txt endpoint.
Where can I find the full registry snapshot?
The complete registry snapshot, including capability status, pricing, and media types, is available at the /index.json endpoint.
How are the capability pages generated?
All capability pages are generated from the registry at build time using TRACE Manifests.