Phoenix Zero — Execution Oracle for L2s
NPM · PHOENIX-MCP-SERVER
Pre-transaction PASS/FAIL for an L2. Free verdict delayed ~60 s, no revert ratio; live via x402.
Available components
Last scanned (18 hours ago)
Scores higher than 58% of npm servers
Category Monitoring and Observability
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 322 tokens (~161/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 −1
- Stability: pass → 0.93 functional
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 0
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: pass → fail ▼ functional
- First check of Schema quality: unverified functional
- Stability: pass → 0.97 functional
- Package version: 1.0.1 → 1.3.1 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 22 Oct 26 +1
- Stability: 0.97 → pass security
- 21 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.80 → pass security
- 16 Oct 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/phoenix-mcp-server@1.3.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_safety_free ~105
FREE safety check for an L2 before sending a transaction (100 calls/IP/day). Returns `safe` true/false plus a `reason` code (`safe` is null only with `warming_up`) for the chosen chain. The verdict is delayed ~60 s; the live verdict is the paid x402 endpoint GET /api/v1/safe (from $0.01 USDC).
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | L2 chain to check. Defaults to base. |
No output schema declared.
No examples provided.
preflight_network_health ~217
Decide whether an L2 is suitable for sending a transaction: PASS or FAIL with a reason code for the chosen chain, from Phoenix Zero measurements (each chain polled every ~2 s against 2-3 independent RPC nodes, Casper 10; feed records signed BLAKE3+Ed25519, responses signed EIP-191). The free answer is delayed ~60 s and checks chain halt, sequencer stall and latency only: it does not include revert ratio, so it never returns DEGRADED. The live verdict with revert ratio (Base/Arbitrum) and p99 latency is paid via x402 from $0.01 USDC (the 402 offers USDC on Base, Polygon or Arbitrum).
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | L2 chain to check. Defaults to base. |
| metric | string | – | health_check = free delayed PASS/FAIL (no revert ratio). latency / revert_ratio = live values via paid x402 endpoints. revert_ratio: Base and Arbitrum only. |
No output schema declared.
No examples provided.
How do I install the Phoenix Zero — Execution Oracle for L2s MCP server?
Phoenix Zero — Execution Oracle for L2s runs locally as an npm package, launched with npx -y phoenix-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · phoenix-mcp-server
claude mcp add kant19801201behax5-phoenix-mcp-server -- npx -y phoenix-mcp-server
What is the Phoenix Zero — Execution Oracle for L2s MCP server?
Phoenix Zero — Execution Oracle for L2s is an MCP server listed in the public MCP registry as io.github.kant19801201behax5/phoenix-mcp-server. Pre-transaction PASS/FAIL for an L2. Free verdict delayed ~60 s, no revert ratio; live via x402. This page covers its npm package (phoenix-mcp-server).
Is the Phoenix Zero — Execution Oracle for L2s MCP server safe to use?
Phoenix Zero — Execution Oracle for L2s scores 78 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Phoenix Zero — Execution Oracle for L2s MCP server expose?
Phoenix Zero — Execution Oracle for L2s exposes 2 tools: check_safety_free, preflight_network_health. Their descriptions and schemas cost roughly 322 tokens of context every time the server is loaded.
Is the Phoenix Zero — Execution Oracle for L2s MCP server still maintained?
Phoenix Zero — Execution Oracle for L2s is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Phoenix Zero — Execution Oracle for L2s MCP server under?
Phoenix Zero — Execution Oracle for L2s declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.