Token risk x402
REMOTE · API.OGENALABS.COM
Pre-trade token safety checks for AI agents on Solana and Base. x402 USDC per call, no key.
Available components
Last scanned (3 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: the endpoint responded but didn't complete an MCP handshake over streamable-http. 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.
- 2 Nov 26 −60
- Endpoint reachability: reachable → not serving MCP ▼ security
- HTTPS: unverified → fail ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 9 Oct 26 +1
- Stability: 0.90 → pass security
- 5 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Sept 26 0
- Server version: 0.1.0 → 0.2.0 functional
- 9 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 8 Sept 26 0
First indexed and scored.
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 5 Nov 2026 · Probed https://api.ogenalabs.com/api/token-risk/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ogenalabs.com | CN=WE1,O=Google Trust Services,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d65dd225b84cf67c0e918ad314449bfe |
| SANs: ogenalabs.com, *.ogenalabs.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.ogenalabs.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ogenalabs.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.ogenalabs.com/api/token-risk/mcp | Not MCP | 200 | |
| http (plaintext) | http://api.ogenalabs.com/api/token-risk/mcp | Served over HTTP | 200 |
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_token_risk_deep Token risk deep report ~93
Full pre-trade risk report for one token: verdict, score, reasons, price, liquidity and HMAC attestation. Costs $0.04 USDC per call. First 3 calls per caller per day are free.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Token mint (Solana) or contract address (Base). |
| chain | string | yes | Chain to screen ('solana' or 'base'). |
| Name | Type | Req | Description |
|---|---|---|---|
| priceUsd | number|null | – | – |
| reasons | array | – | – |
| score | number | – | – |
| verdict | string | – | – |
No examples provided.
check_token_safety_ping Token safety ping ~82
Fast pre-trade safety boolean for one token. Returns safe true, false or null plus mint-authority and liquidity-lock flags. Costs $0.005 USDC per call.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Token mint (Solana) or contract address (Base). |
| chain | string | yes | Chain to screen ('solana' or 'base'). |
| Name | Type | Req | Description |
|---|---|---|---|
| lpLocked | boolean|null | – | – |
| mintAuthorityOff | boolean|null | – | – |
| pairs | number | – | – |
| safe | boolean|null | – | – |
No examples provided.
How do I install the Token risk x402 MCP server?
Token risk x402 is a hosted endpoint at https://api.ogenalabs.com/api/token-risk/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 · api.ogenalabs.com
claude mcp add --transport http com-ogenalabs-token-risk-x402 'https://api.ogenalabs.com/api/token-risk/mcp'
What is the Token risk x402 MCP server?
Token risk x402 is an MCP server listed in the public MCP registry as com.ogenalabs/token-risk-x402. Pre-trade token safety checks for AI agents on Solana and Base. x402 USDC per call, no key. This page covers its hosted endpoint (https://api.ogenalabs.com/api/token-risk/mcp).
Is the Token risk x402 MCP server safe to use?
Token risk x402 scores 18 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 Token risk x402 MCP server expose?
Token risk x402 exposes 2 tools: check_token_safety_ping, check_token_risk_deep. Their descriptions and schemas cost roughly 175 tokens of context every time the server is loaded.
Does the Token risk x402 MCP server require authentication?
No. We connected to Token risk x402 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Token risk x402 MCP server still maintained?
Token risk x402 is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.