io.github.tracelane/tracelane-mcp
io.github.tracelane/tracelane-mcp
Is the io.github.tracelane/tracelane-mcp MCP server down? No. It is up and needs network, probed 2026-10-30.
Read-only, tenant-scoped access to Tracelane agent traces and guardrail verdicts
needs network probed 2026-11-15 · unchanged since 2026-10-30
MCP error -32000: Connection closed
{"level":"warn","component":"mcp","msg":"whoami fetch failed","error":"fetch failed"}
{"level":"error","component":"mcp","ms- Run it
- npx -y @tracelanedev/mcp@0.4.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/tracelane/tracelane
- Website
- https://tracelane.dev/docs/mcp-server
- Registry
- active, updated 2026-10-09 · registry entry
- Changes
- 2 recorded, reachable in 0 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.totalaudiopromo/tap-mcp · alive
- io.github.tothienbao6a0/upnext · alive
- io.github.totte-dev/vibe-provision · needs env
- io.github.tponscr-debug/oracle-h · alive
- io.github.tracentdev/paystack-mcp · alive
- io.github.trackerfitness729-jpg/sitelauncher-mcp-server · timeout
- Konvizi io.github.trades-survey/konvizi · alive
- io.github.tradetabula/tabula-mcp · crashed on start
Servers that mention guardrail or verdicts.
- ai.geodesiclabs/governance-platform · alive
- Overwing ai.overwing/mcp · alive
- ai.responsibleailabs/rail-score · no DNS
- ai.sellermate/amazon-ads · needs auth
- ThinkNEO Control Plane ai.thinkneo/control-plane · no DNS
- app.leadsmarts/leadsmarts · needs auth
- app.zenable/zenable · needs auth
- A.U.G.U.R Synapse art.maddegen.agent/synapse · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-10-30 07:53 | needs network | ||||
| 2026-10-16 06:29 | timeout |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server tries to reach the network on start. The probe runs in a container with the network off, so a server that connects lazily, on the first tool call, is measured.