apix402
REMOTE · API402X.COM
Live onchain governance, vesting, oracle and Safe authority checks. Free samples over MCP.
Available components
Last scanned (38 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 19 Sep 2026.
Category Crypto and Web3
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 28 Sept 26 −16
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 26 Sept 26 −15
The score moved with no change recorded against any check. We would rather say so than guess.
- 25 Sept 26 −16
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −16
The score moved with no change recorded against any check. We would rather say so than guess.
- 20 Sept 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 13 Sept 26 0
- Stability: 0.97 → pass security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 28 Sept 2026 · Probed https://api402x.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api402x.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| api402x.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api402x.com/mcp | Unreachable | ||
| http (plaintext) | http://api402x.com/mcp | HTTPS enforced |
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 →
apix402_catalog ~62
List every apix402 check an agent can buy: route, price in USDC, what question it answers, and its free preview. Start here. Payment is x402 over plain HTTP -- no API key, no account, the wallet is the identity.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
dao_governance_discrepancies ~77
Live sample: DAO governance proposals closest to their deadline, with a count of disagreements between the off-chain Snapshot signal and a direct read of the onchain Governor contract. Fixed set of tracked DAOs, no arguments. The count is free; which DAO disagrees and how is the paid GET /dao-proposals.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
lending_depeg_sample ~73
Live sample: one fixed, real Aave V3 position -- whether it is exposed to the stETH depeg blind spot and how much of its collateral is wstETH. The depeg level at which it becomes liquidatable is the paid GET /lending-depeg-exposure, which takes any borrower.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
oracle_staleness_sample ~73
Live sample: for a fixed set of price feeds, whether each one would be rejected right now by a guard built on that feed's own measured cadence. Boolean verdicts only; ages, thresholds, the Chainlink-vs-Pyth spread and the revert selector are the paid GET /oracle-staleness.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
safe_authority_sample ~84
Live sample: who can actually move funds out of one fixed Gnosis Safe -- owners, threshold, and modules expanded recursively, because a Safe that reads as 1-of-1 can in fact be governed through a module by a separate 2-of-8. The paid GET /safe-signer-drift takes any Safe and adds what changed and in which block.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vesting_status_sample ~45
Live sample: the current state of one fixed vesting plan read straight from the contract. The paid GET /vesting-status takes any Hedgey plan or Sablier stream.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the apix402 MCP server?
apix402 is a hosted endpoint at https://api402x.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api402x.com
claude mcp add --transport http com-api402x-apix402 'https://api402x.com/mcp'
What is the apix402 MCP server?
apix402 is an MCP server listed in the public MCP registry as com.api402x/apix402. Live onchain governance, vesting, oracle and Safe authority checks. Free samples over MCP. This page covers its hosted endpoint (https://api402x.com/mcp).
Is the apix402 MCP server safe to use?
apix402 scores 0 out of 100 on VerifyMCP. 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 apix402 MCP server expose?
apix402 exposes 6 tools: apix402_catalog, dao_governance_discrepancies, oracle_staleness_sample, lending_depeg_sample, vesting_status_sample, safe_authority_sample. Their descriptions and schemas cost roughly 414 tokens of context every time the server is loaded.
Does the apix402 MCP server require authentication?
Its publisher declares no required credentials for apix402. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the apix402 MCP server still maintained?
apix402 has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 19 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.