Test, debug, and validate MCP servers — health checks, OAuth conformance, tool-surface diffing, and structured triage from the terminal or CI
- capability exposure inferred + 22
- inherited (deps) attested + 1
- trust mitigators mixed − 8
attested inferred mixed
The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.
graded 10m ago · see ecosystem CVEs →
- A · 0 → B · 15
No known CVEs for this server.
inherited (deps) · grade factor +1
No tool-safety findings — heuristic detectors run on the compute-risk cadence; a finding appears when a tool trips a rule.
analyzed v3.15.2 · analyzer v28 · 2d ago
danger signals1
- suspicious endpoint us.i.posthog.com (telemetry)
expected for this server's purpose
package/dist/index.js :7784
var POSTHOG_HOST = "https://us.i.posthog.com";
[](https://mcpobservatory.com/servers/npm:@mcpjam/cli/security) Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of mcpjam-founders.