# 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.

- Trust score: 35/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `api.ogenalabs.com`: 35/100 (this document), [markdown](https://verifymcp.io/servers/com-ogenalabs-token-risk-x402/api-token-risk-mcp.md), [page](https://verifymcp.io/servers/com-ogenalabs-token-risk-x402/api-token-risk-mcp)

## Channel facts

- Endpoint: `https://api.ogenalabs.com/api/token-risk/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 0/100
  - Instruction-quality not yet verified: the AI judgement didn't run.
  - Nothing to assess: this server exposes no tool/resource definitions to measure a footprint for.
  - Nothing to assess: this server has no tools to check for usage examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-ogenalabs-token-risk-x402 'https://api.ogenalabs.com/api/token-risk/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-ogenalabs-token-risk-x402": {
      "url": "https://api.ogenalabs.com/api/token-risk/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-ogenalabs-token-risk-x402": {
      "type": "http",
      "url": "https://api.ogenalabs.com/api/token-risk/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-ogenalabs-token-risk-x402]
url = "https://api.ogenalabs.com/api/token-risk/mcp"
```

### opencode

```json
{
  "$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

```bash
openclaw mcp add com-ogenalabs-token-risk-x402 --url 'https://api.ogenalabs.com/api/token-risk/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-ogenalabs-token-risk-x402:
    url: "https://api.ogenalabs.com/api/token-risk/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-ogenalabs-token-risk-x402": {
      "Transport": "http",
      "Url": "https://api.ogenalabs.com/api/token-risk/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-ogenalabs-token-risk-x402 -t streamable-http -u 'https://api.ogenalabs.com/api/token-risk/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 35, +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.

### 2026-09-18 (score 34, +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.

### 2026-09-16 (score 33, +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.

### 2026-09-13 (score 32, +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.

### 2026-09-11 (score 31, +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.

### 2026-09-10 (score 30, 0)

- [functional] Server version: 0.1.0 → 0.2.0

### 2026-09-09 (score 30, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-08 (score 29)

First indexed and scored.

## MCP tools (0)

No tool schema has been captured from this endpoint yet.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-ogenalabs-token-risk-x402/api-token-risk-mcp#diagnostics

## Score history

- 2026-09-20: 35
- 2026-09-19: 34
- 2026-09-18: 34
- 2026-09-17: 33
- 2026-09-16: 33
- 2026-09-15: 32
- 2026-09-14: 32
- 2026-09-13: 32
- 2026-09-12: 31
- 2026-09-11: 31
- 2026-09-10: 30
- 2026-09-09: 30
- 2026-09-08: 29

## Common questions

### 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.

## Links

- Remote endpoint: https://api.ogenalabs.com/api/token-risk/mcp
- Repository: https://github.com/OgenaLabs/token-risk-mcp
- Website: https://ogenalabs.com/products
- Changelog RSS feed: https://verifymcp.io/servers/com-ogenalabs-token-risk-x402/api-token-risk-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-ogenalabs-token-risk-x402/api-token-risk-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-ogenalabs-token-risk-x402/api-token-risk-mcp