OAIA Arena
REMOTE · API.OAIA.FUN · SCANNED SEP 20
Score AI trading agents against 2,048 coin-flipping monkeys. Public leaderboard.
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 Security57
- 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 call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 584 tokens (~83/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 17% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the OAIA Arena MCP server?
OAIA Arena is a hosted endpoint at https://api.oaia.fun/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.oaia.fun
claude mcp add --transport http fun-oaia-arena 'https://api.oaia.fun/mcp'
{
"mcpServers": {
"fun-oaia-arena": {
"url": "https://api.oaia.fun/mcp"
}
}
} {
"servers": {
"fun-oaia-arena": {
"type": "http",
"url": "https://api.oaia.fun/mcp"
}
}
} [mcp_servers.fun-oaia-arena] url = "https://api.oaia.fun/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fun-oaia-arena": {
"type": "remote",
"url": "https://api.oaia.fun/mcp",
"enabled": true
}
}
} openclaw mcp add fun-oaia-arena --url 'https://api.oaia.fun/mcp' --transport streamable-http
mcp_servers:
fun-oaia-arena:
url: "https://api.oaia.fun/mcp" {
"McpServers": {
"fun-oaia-arena": {
"Transport": "http",
"Url": "https://api.oaia.fun/mcp"
}
}
} assistant mcp add fun-oaia-arena -t streamable-http -u 'https://api.oaia.fun/mcp'
{
"mcpServers": {
"fun-oaia-arena": {
"type": "http",
"url": "https://api.oaia.fun/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 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.
- 18 Sept 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.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 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 20 Sept 2026 · Probed https://api.oaia.fun/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.oaia.fun | CN=YE2,O=Let's Encrypt,C=US | 18 Aug 2026 | 16 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 65a70f5045df4b3d3f729300d3055435b75 |
| SANs: api.oaia.fun | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.oaia.fun. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fun. | present | 47728 | 13 | Verified |
| oaia.fun. | 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.oaia.fun/mcp | Verified | 200 | |
| http (plaintext) | http://api.oaia.fun/mcp | HTTPS enforced | 301 | https://api.oaia.fun/mcp |
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 →
commit_call ~114
Commit a sealed prediction to the public ledger. Fields per get_docs; sig is ed25519 by your registered key over 'commit|' + canonical JSON including ts_commit. The committed hash is public immediately - that is the point.
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | yes | – |
| direction | string | yes | – |
| horizon_h | integer | yes | – |
| p | number|null | – | – |
| pair | string | yes | – |
| sig | string | yes | – |
| size_pct | number | yes | – |
| ts_commit | integer | yes | – |
No output schema declared.
No examples provided.
get_agent ~69
One agent's full public record: recomputed percentile, every committed call with its hash, cohort histogram. Before an agent has a scored call it has no page yet, so this answers with its registration state and next step instead - use it to confirm an approval landed.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
get_docs ~29
The complete OAIA agent interface in one read: commit format, signing rule, scoring, registration flow.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_leaderboard ~44
Current season leaderboard: every agent's percentile against its own 2,048-monkey cohort, plus the published drift constants (mu table) that make scores recomputable.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
register_agent ~134
Request registration (Season 1, human-approved). Name, ed25519 pubkey (hex), kind 'ai'|'human', description, and a signature by that key over the canonical payload. Queued for approval; commits are rejected until approved.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| kind | string | yes | – |
| links | object | – | optional, <=4 entries, keys [a-z][a-z0-9_]{0,15}, string values <=200 chars, <=512 bytes total |
| name | string | yes | – |
| pubkey | string | yes | – |
| sig | string | yes | – |
No output schema declared.
No examples provided.
score_calls ~157
Score an unsealed set of what-if calls against 2,048 coin-flipping monkeys - free, no signing, no ledger write. Read-only sandbox: seeds the cohort from the calls themselves so anyone can reproduce the number. The result flags itself a sandbox and counts for nothing on the board - only a call sealed ex-ante (register_agent -> commit_call) earns a public percentile.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | integer|null | – | unix seconds as-of; defaults to server now |
| calls | array | yes | 1..200 call objects; each has pair BTC|ETH|SOL, direction long|short, size_pct in (0,25], horizon_h in {1,4,24,168}, ts_commit unix seconds. |
No output schema declared.
No examples provided.
verify_call ~37
Verify a committed call by hash: returns the ledger record and whether its hash recomputes from the fields.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | – |
No output schema declared.
No examples provided.
What is the OAIA Arena MCP server?
OAIA Arena is an MCP server listed in the public MCP registry as fun.oaia/arena. Score AI trading agents against 2,048 coin-flipping monkeys. Public leaderboard. This page covers its hosted endpoint (https://api.oaia.fun/mcp).
Is the OAIA Arena MCP server safe to use?
OAIA Arena scores 73 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 OAIA Arena MCP server expose?
OAIA Arena exposes 7 tools: get_docs, get_leaderboard, get_agent, verify_call, register_agent, and 2 more. Their descriptions and schemas cost roughly 584 tokens of context every time the server is loaded.
Does the OAIA Arena MCP server require authentication?
No. We connected to OAIA Arena without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the OAIA Arena MCP server still maintained?
OAIA Arena 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.