Tracelane MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 198 installs a week from npm. Last commit 9 Oct 2026.
Read-only, tenant-scoped access to Tracelane agent traces and guardrail verdicts
We read the source, 1 d ago · rules ccca72095570
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
const r = spawnSync(command, [...args], { cwd, stdio: "inherit" });
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const r = spawnSync(command, [...args], { cwd, stdio: "inherit" });
return __import__(module)
USER root # aws-lc-rs / ring (via rustls + jsonwebtoken's aws_lc_rs feature) compile C -> cmake.
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch Tracelane MCP and you get told the day something new turns up.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add tracelane-mcp -- npx -y @tracelanedev/mcp
{
"mcpServers": {
"tracelane-mcp": {
"args": [
"-y",
"@tracelanedev/mcp"
],
"command": "npx"
}
}
}
[mcp_servers.tracelane-mcp]
command = "npx"
args = ["-y", "@tracelanedev/mcp"]
{
"mcpServers": {
"tracelane-mcp": {
"args": [
"-y",
"@tracelanedev/mcp"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"tracelane-mcp": {
"args": [
"-y",
"@tracelanedev/mcp"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
TRACELANE_API_KEY (Tracelane API key (tlane_…). Resolved to a tenant once at startup via the gateway's /v1/auth/whoami; the server refuses to start if the key is rejected. Also the credential used to read trace data through the gateway when CLICKHOUSE_URL is unset.), TRACELANE_GATEWAY_URL (Base URL of the Tracelane gateway. Validates TRACELANE_API_KEY, and — when CLICKHOUSE_URL is unset — is where every trace read goes. Must be https://…tracelane.dev outside development.), CLICKHOUSE_URL (self-host only; when unset the server reads through the gateway. Set this to point the server at your own ClickHouse instead of Tracelane Cloud.), CLICKHOUSE_USER (ClickHouse username.), CLICKHOUSE_PASSWORD (ClickHouse password.), CLICKHOUSE_DB (ClickHouse database holding the spans table.), TRACELANE_MCP_TRANSPORT (Transport to serve. stdio (default) for desktop clients; http for the Streamable HTTP transport.).
The author declared them in the registry entry; get the values from the project itself.
Read-only MCP server for coding-agent traces, alerts, costs, usage, and budget health.
Read-only MCP access to Filter Solutions Ltd public filtration and oil monitoring content.
Read-only access to your fresh produce shipments: ETAs, tracking, free time, alerts and documents.
Read-only MCP server over a local log-analysis backend; a client that computes no verdicts.
Test the voice agents you run: scored transcripts, pass/fail verdicts, latency and WER metrics.
Read-only access to Tideways PHP performance monitoring: performance, issues, traces, history.
AI browser tests from your coding agent: a verdict, failing steps, report, video and trace.
MCP server for EPICS Channel Access: read, monitor and guarded writes of process variables.
Answers built from our own checks of this server.