Securealy
com-securealy-mcp declares 9 capabilities across 9 tools, with 2 critical issues.
Issues
9 of 9 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
1 tool is classified as irreversible and declares no limit.
9 of 9 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
9 of 9 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
8 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
grade_url | read |
declared |
scan_repo | read |
declared |
check_rls | read |
declared |
check_stripe | read |
declared |
check_vercel_env | read |
declared |
get_check | read |
declared |
list_checks | read |
declared |
fetch_fix | read |
declared |
post_result | send |
inferred |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-14 | 26 | tools/list answered by the npm package securealy-mcp@0.1.4 (published to npm as securealy-mcp, listed in the official MCP registry as com.securealy/mcp 0.1.4), run in an isolated container with no network access and placeholder credentials |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.