ToolsMCP
tracehub-mcp
Listed in the official MCP Registry with an installable pypi package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- mcpsmiths (GitHub)
- Prerequisites
- Install tracehub-mcp from pypi (stdio transport). Declares 2 secret inputs. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.13.1 · updated
- Official links
Publisher’s description
Query OTel traces across Jaeger, Tempo, Traceloop, Datadog, Sentry, X-Ray, New Relic, Honeycomb.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.13.1, registry status active. 1 package (pypi)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- mcpsmiths (GitHub)
- Version observed
- 0.13.1
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.mcpsmiths%2Ftracehub-mcp/versions/0.13.1
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Investigate errors and incidents | Publisher description mentions “datadog”, “sentry”, “new relic”, “traces”. | No connection check or task run. Capability is as described by the publisher. | Rule observability matched: “datadog”, “sentry”, “new relic”, “traces”. Rule observability. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
tracehub-mcp(pypi, stdio, 2 secret inputs)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.mcpsmiths/tracehub-mcp
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.