aap-mcp-server
Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
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
ansible
Source: github_code
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 →
Install from
M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
When Vitest UI server is listening, arbitrary file can be read and executed
js-yaml: YAML merge-key chains can force quadratic CPU consumption
JS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026-59870 fix not backported
JS-YAML: Quadratic-complexity DoS in merge key handling via repeated aliases
js-yaml has prototype pollution in merge (<<)
ANALYTICS_KEYBASE_URLLower priority than environment variableCONTAINER_VERSIONDEFAULT_PAGE_SIZEINSTALLER_IDINTERNAL_EMAIL_DOMAINSMCP_PORTServer portMCP_SERVER_URLOAUTH2_DISCOVERY_TIMEOUTOAUTH2_ENABLEDTELEMETRY_HMAC_KEYTool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
4/4 tools missing one or more hints — discover (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); call_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); discover (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +1 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.
Tool test coverage
2/4 tools referenced in tests (50%)
Write tests that reference each tool by name so every tool has at least one test.
Secrets stay with their owner
5 secret/sensitive values flow into network calls (ANALYTICS_KEY → dynamic, ANALYTICS_KEY → dynamic)
Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.
Secrets not logged
7 secret values sent to console.log
Redact or omit secret values from log output.
Production dependencies are patched
0 critical, 2 high severity in production deps — js-yaml@4.1.0 (high), js-yaml@4.1.0 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
Dev dependencies
1 critical/high in dev-only deps (does not ship to users)
Upgrade dev dependencies when convenient.
Dependency freshness
2/8 production deps stale: openapi-types@2023-05-24 (3.2y), prom-client@2024-06-27 (2.1y)
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.
[](https://m8ven.ai/mcp/ansible-aap-mcp-server-16229a)?variant=verified from the URL.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