← Index

io.github.mcpsmiths/tracehub-mcp

io.github.mcpsmiths/tracehub-mcpv0.2.3AI & LLMs

Query OpenTelemetry traces from LLM apps across Jaeger, Tempo, Traceloop, Datadog, and Sentry.

The current version, v0.2.3, was published to the official MCP registry on 2026-09-13. It is distributed as tracehub-mcp on PyPI, filed under AI & LLMs by this index, and declares 10 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using io.github.mcpsmiths/tracehub-mcp in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Auditable install path →Watch it hold a drift →
Trust verdict · v1 advisory · method
NOT YET SCREENEDno verdict on file

Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-09-13).

Contracts can change after screening, with no version bump. The gate pins io.github.mcpsmiths/tracehub-mcp’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Environment variables
BACKEND_TYPE
required

Which observability backend to query.

BACKEND_URL
required

Backend API endpoint, e.g. http://localhost:16686 for Jaeger or https://api.datadoghq.com for Datadog.

BACKEND_API_KEY
secret

API key or auth token. Required for Traceloop, Datadog, and Sentry; not used by Jaeger or Tempo.

BACKEND_APP_KEY
secret

Datadog Application key, required in addition to BACKEND_API_KEY for the Datadog backend only.

BACKEND_SENTRY_ORG

Sentry organization slug, required for the Sentry backend only.

BACKEND_SENTRY_PROJECT

Sentry project slug, optional for the Sentry backend - narrows queries to one project.

BACKEND_ENVIRONMENTS

Comma-separated environments for the Traceloop backend only.

BACKEND_TIMEOUT

Request timeout in seconds.

LOG_LEVEL

Logging level.

MAX_TRACES_PER_QUERY

Maximum traces validated per query (1-1000).

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
10
installability
25
documentation
15
stability
5
Alternatives in AI & LLMs
Codex Delegate
io.github.andreilungeanu/codex-delegate-mcp

Bridge AI coding hosts to the OpenAI Codex CLI for delegated implementation.

BridgeNode MCP
io.github.bridgenode-ai/bridgenode-mcp

BridgeNode — x402 pay-per-request AI inference. OpenAI-compatible API + MCP, Solana USDC, gas-free.

Agentic Observability MCP
io.github.mdfifty50-boop/agentic-observability

Agent tracing, cost tracking, anomaly detection for LLM agents