About Tracert
Tracert’s public website generates human- and agent-facing routes, capability pages, and machine-readable exports from a registry. It also serves static resources including a registry snapshot and JSON Schemas.
Key features
- 01Generate routes for humans and agents
- 02Publish capability pages and machine exports
- 03Serve a registry JSON snapshot
- 04Provide Manifest and Receipt JSON Schemas
Use cases
- 01Browse registered agent capabilities
- 02Retrieve capability listings in machine-readable form
- 03Inspect TRACE Manifest and Receipt structures
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://tracert.site/api/mcpclaude mcp add --transport http site-tracert-tracert https://tracert.site/api/mcp{"mcpServers":{"site-tracert-tracert":{"type":"http","url":"https://tracert.site/api/mcp"}}}Open in Cursor{"servers":{"site-tracert-tracert":{"type":"http","url":"https://tracert.site/api/mcp"}}}Open in VS Code{"mcpServers":{"site-tracert-tracert":{"type":"http","url":"https://tracert.site/api/mcp"}}}{"mcpServers":{"site-tracert-tracert":{"serverUrl":"https://tracert.site/api/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEtracert.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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.