Token risk x402
REMOTE · API.OGENALABS.COM · SCANNED SEP 20
Pre-trade token safety checks for AI agents on Solana and Base. x402 USDC per call, no key.
Available components
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 tool list to see what that exposes. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability0
- Instruction-quality not yet verified: the AI judgement didn't run.Unverified
- Nothing to assess: this server exposes no tool/resource definitions to measure a footprint for. See how to fix → Fail
- Nothing to assess: this server has no tools to check for usage examples. See how to fix → Fail
Stability & Change Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Unverified: 2 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.
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'
{
"mcpServers": {
"com-ogenalabs-token-risk-x402": {
"url": "https://api.ogenalabs.com/api/token-risk/mcp"
}
}
} {
"servers": {
"com-ogenalabs-token-risk-x402": {
"type": "http",
"url": "https://api.ogenalabs.com/api/token-risk/mcp"
}
}
} [mcp_servers.com-ogenalabs-token-risk-x402] url = "https://api.ogenalabs.com/api/token-risk/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-ogenalabs-token-risk-x402": {
"type": "remote",
"url": "https://api.ogenalabs.com/api/token-risk/mcp",
"enabled": true
}
}
} openclaw mcp add com-ogenalabs-token-risk-x402 --url 'https://api.ogenalabs.com/api/token-risk/mcp' --transport streamable-http
mcp_servers:
com-ogenalabs-token-risk-x402:
url: "https://api.ogenalabs.com/api/token-risk/mcp" {
"McpServers": {
"com-ogenalabs-token-risk-x402": {
"Transport": "http",
"Url": "https://api.ogenalabs.com/api/token-risk/mcp"
}
}
} assistant mcp add com-ogenalabs-token-risk-x402 -t streamable-http -u 'https://api.ogenalabs.com/api/token-risk/mcp'
{
"mcpServers": {
"com-ogenalabs-token-risk-x402": {
"type": "http",
"url": "https://api.ogenalabs.com/api/token-risk/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 0
- Server version: 0.1.0 → 0.2.0 functional
- 9 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 8 Sept 26 29
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 20 Sept 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 | 25 Jul 2026 | 23 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 43ebb7b0058730411345bf06844c5676 |
| 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 | Verified | 200 | |
| http (plaintext) | http://api.ogenalabs.com/api/token-risk/mcp | Inconclusive | 404 |
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 →
No tool schema has been captured from this endpoint yet.
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 35 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.
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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.