Phoenix Zero — Execution Oracle for L2s
io-github-kant19801201behax5-phoenix-mcp-server declares 2 capabilities across 2 tools, with 1 critical issue. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.
Issues
2 of 2 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.
2 of 2 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.
2 of 2 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.
2 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
check_safety_free | read |
declared |
preflight_network_health | read |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-26 | 6 | tools/list answered by the npm package phoenix-mcp-server@1.0.1 (published to npm as phoenix-mcp-server, listed in the official MCP registry as io.github.kant19801201behax5/phoenix-mcp-server 1.0.1), run in an isolated container with no network access and no credentials |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.