Byok Observability MCP Server
byok-observability-mcp
npm
v0.5.2
Published by alimuratkuslu — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server for Grafana, Prometheus, Kafka UI, and Datadog — bring your own credentials (BYOK)
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
medium Hardcoded egress to an external endpoint (dist/init-YEHVUSNS.js)MTC-SRC-003
In the server's implementation (`dist/init-YEHVUSNS.js:51`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: { const res = await fetch(`https://api.${cfg.site}/api/v1/validate`, { headers: { "DD-API-KEY": cfg.apiKey }
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/init-YEHVUSNS.js
Tools 23
Each tool and what it can reach — statically extracted from the published source.
grafana_get_alert_rulesno sensitive capabilitygrafana_get_dashboardno sensitive capabilitygrafana_healthno sensitive capabilitygrafana_list_alertsno sensitive capabilitygrafana_list_dashboardsno sensitive capabilitygrafana_list_datasourcesno sensitive capabilitygrafana_query_metricsno sensitive capabilitykafka_broker_healthno sensitive capabilitykafka_consumer_group_lagno sensitive capabilitykafka_describe_topicno sensitive capability
Show 13 more tools ↓
kafka_list_clustersno sensitive capabilitykafka_list_consumer_groupsno sensitive capabilitykafka_list_topicsno sensitive capabilityobs_health_checkno sensitive capabilityobs_investigate_incidentno sensitive capabilityopsgenie_ack_alertno sensitive capabilityopsgenie_list_alertsno sensitive capabilityopsgenie_who_is_on_callno sensitive capabilityprometheus_healthno sensitive capabilityprometheus_list_metricsno sensitive capabilityprometheus_metric_metadatano sensitive capabilityprometheus_queryno sensitive capabilityprometheus_query_rangeno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (23 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.5.2 latest |
A 96/100 | 1 | 1.13.0 | 2026-09-09 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan byok-observability-mcp --onlineMore in Developer Tools
Hotel booking MCP server — 300K+ properties, real confirmation numbers, loyalty programs. Builders monetize every booking via Stripe Connect. The first MCP server that completes real hotel reservations inside AI conversations.
Generates production-ready UI components from natural language, inspired by v0.
Manage AdGuard Home through AI assistants
Read-only Azure DevOps for MCP clients using only your existing browser session — no PAT, no Azure CLI. Browse work items, pull requests, comments, attachments and Artifacts feeds across every project, repo and feed you can access.
MCP server for Adobe Experience Manager Assets integration development
Servidor MCP para el tiempo oficial de España (API pública OpenData de AEMET). Predicción, observación y avisos como herramientas MCP tipadas.