server-aws-kb-retrieval
npm:@modelcontextprotocol/server-aws-kb-retrieval@0.6.2
No findings
The classifier found no rule violations on this server's advertised tool surface against the public capframe rules (R1–R7). A clean score means the surface looks tight to the rule engine — it does not mean the implementation is audited.
Go deeper
Nothing here needs fixing — this surface is clean against R1–R7. The limit is what the rules can see: a public scan reads the tool surface, not the implementation behind it. Everything below is optional.
curl -fsSL capframe.ai/install | sh capframe find ./your-mcp-config.json --out findings.json
Five-step quickstart if you want the whole Find → Bind → Guard loop. If you'd rather have someone read your real tool definitions rather than the advertised surface — including the ones this public scan can't reach — that's the Agent Security Audit.
How this was scored
Source registry — tool surface extracted from the package's README + manifest (R3/R5/R6/R7 fire; schema-dependent rules deferred). Findings are emitted by the public capframe.findings.v1 schema. Score = 100 − (10·Critical + 4·High + 2·Medium + 1·Low), clamped to [0, 100].
Disagree with a finding? Open an issue.