tracehub-mcp (mcpsmiths/tracehub-mcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 15 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

tracehub-mcp

MCP server for querying OpenTelemetry traces across multiple observability backends (Jaeger, Tempo, Traceloop, Datadog, and more) for LLM application debugging. Fork of traceloop/opentelemetry-mcp-server.

→ mcpsmiths/tracehub-mcp· listed on github_repo_search

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

mcpsmiths

Source: github_repo_search

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
15 tools verified — handlers match their declared behaviour
15 read-only tools verified — handlers contain no write/delete/exec
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 2 credentials: BACKEND_API_KEY, BACKEND_APP_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configBACKEND_TYPEBackend type: jaeger, tempo, traceloop, datadog, or sentry
configBACKEND_URLBackend API endpoint (required)
configBACKEND_ENVIRONMENTSComma-separated environments (Traceloop only)
configBACKEND_TIMEOUTRequest timeout in seconds
🔐 secretBACKEND_API_KEYAPI key/auth token (required for Traceloop, Datadog, and Sentry)
🔐 secretBACKEND_APP_KEYApplication key (Datadog only, in addition to BACKEND_API_KEY)
configBACKEND_SENTRY_ORGOrganization slug (required for Sentry)
configBACKEND_SENTRY_PROJECTProject slug (optional for Sentry, narrows queries to one project)
configBACKEND_TEMPO_INSTANCE_IDGrafana Cloud stack/instance ID (Tempo only, enables Basic Auth in addition to BACKEND_API_KEY)
configLOG_LEVELLogging level: DEBUG, INFO, WARNING, ERROR
configMAX_TRACES_PER_QUERYParsed and validated (1-1000) but not currently wired into any query — each tool's own limit parameter is the real per-call cap
// quality suggestions

All four hints declared on every tool

15/15 tools missing one or more hints — search_traces (missing: destructiveHint); get_trace (missing: destructiveHint); get_llm_usage (missing: destructiveHint), +12 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 1 concrete improvement we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/mcpsmiths/tracehub-mcp)](https://m8ven.ai/mcp/mcpsmiths/tracehub-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: e60cfa46c0c1c71487f7d1265332becbe81c0a7d
code hash: 8ab83f225ee08836adc432ce463cf4d14ed719cf5af75dfe1476c5bb23e73383
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client