Drive an MCP server over real stdio against a real backend, and prove every tool was exercised
- capability exposure inferred + 6
- trust mitigators mixed − 3
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.
grade last moved 6d ago · see ecosystem CVEs →
No known CVEs for this server.
No tool-safety findings — heuristic detectors run on the compute-risk cadence; a finding appears when a tool trips a rule.
analyzed commit 0b2cd15 · analyzer v33 · 1w ago
danger signals1
- suspicious endpoint 169.254.169.254 (cloud metadata) ni-c-mcp-integration-harness-0b2cd15/test/loopback.test.ts :33
'http://169.254.169.254/latest/meta-data/',
[](https://mcpobservatory.com/servers/github:ni-c/mcp-integration-harness/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 ni-c.