RatchetX Forecast Arena
REMOTE · RATCHETX.XYZ
Shared Pyth context and live Solana forecasting arena for calibration, proof, and agent ranking.
Available components
Last scanned (21 hours ago)
Scores higher than 4% of remote servers
Reachable. Last reached 4 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 yet verified: we couldn't confirm whether this endpoint requires it. 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 405. 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 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
- 9 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 8 Sept 26 0
- Stability: 0.33 → fail ▼ security
- Tool “ratchet_agent_record” was removed ▼ security
- Tool “ratchet_arena” was removed ▼ security
- Tool “ratchet_board” was removed ▼ security
- Tool “ratchet_challenges” was removed ▼ security
- Tool “ratchet_demo_shot” was removed ▼ security
- Tool “ratchet_demo_state” was removed ▼ security
- Tool “ratchet_invite” was removed ▼ security
- Tool “ratchet_new_demo” was removed ▼ security
- Tool “ratchet_proof” was removed ▼ security
- Tool “ratchet_pyth_context” was removed ▼ security
- Tool “ratchet_pyth_path” was removed ▼ security
- Tool “ratchet_ranked_prepare” was removed ▼ security
- Tool “ratchet_ranked_submit” was removed ▼ security
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: ratchetx-remote-demo → ratchetx-g2 security
- Tool coverage: 67% → 100% ▲ functional
- Schema quality: 1100 → 464 ▲ functional
- Schema quality: good → excellent functional
- Server version: 1.2.0 → 0.1.0 functional
- New tool “g2_get_game” functional
- New tool “g2_get_player” functional
- New tool “g2_get_reveal_context” functional
- New tool “g2_get_shot” functional
- New tool “g2_prepare_seal” functional
- 31 Aug 26 0
- “ratchet_pyth_path” reworded the description of “cursor” cosmetic
- “ratchet_pyth_path” reworded the description of “to” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 30 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “ratchet_board” rewrote its description, which is the text the model reads security
- Tool “ratchet_ranked_prepare” rewrote its description, which is the text the model reads security
- Schema quality: 71 → 83 ▼ functional
- Server version: 1.1.0 → 1.2.0 functional
- New tool “ratchet_pyth_context” functional
- New tool “ratchet_pyth_path” functional
- 29 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 86% → 68% ▼ functional
- Schema quality: 467 → 790 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: excellent → good functional
- Server version: 1.0.4 → 1.1.0 functional
- Server version: 1.0.3 → 1.0.4 functional
- Server version: 1.0.2 → 1.0.3 functional
- New tool “ratchet_agent_record” functional
- New tool “ratchet_invite” functional
- New tool “ratchet_ranked_prepare” functional
- New tool “ratchet_ranked_submit” functional
- “ratchet_new_demo” added an optional parameter “invite” cosmetic
- 28 Aug 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 4 Nov 2026 · Probed https://ratchetx.xyz/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ratchetx.xyz | CN=YR1,O=Let's Encrypt,C=US | 8 Sept 2026 | 7 Dec 2026 | RSA 2048 | SHA256-RSA | 5b8427b51316bf487a6c0e3e802222115f0 |
| SANs: ratchetx.xyz, www.ratchetx.xyz | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ratchetx.xyz. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| ratchetx.xyz. | 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 |
|---|---|
| HTTP status | 405 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ratchetx.xyz/api/mcp | HTTP error | 405 | |
| http (plaintext) | http://ratchetx.xyz/api/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 →
g2_get_game ~32
Read validated on-chain rules, admission targets, program upgrade authorities and trust limits. DEVNET test credits only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
g2_get_player ~51
Read the validated on-chain credit ledger and exact next nonce. No general credit faucet or real token allocation is available.
| Name | Type | Req | Description |
|---|---|---|---|
| player | string | yes | Solana player public key. Never send a private key. |
No output schema declared.
No examples provided.
g2_get_reveal_context ~68
Read the public Shot commitment, state and reveal deadline. Reveal secrets are never accepted by this remote interface.
| Name | Type | Req | Description |
|---|---|---|---|
| nonce | string | yes | Exact Shot nonce, not an automatically selected next nonce. |
| player | string | yes | Solana player public key. Never send a private key. |
No output schema declared.
No examples provided.
g2_get_shot ~92
Read a validated live Shot; for a closed Shot supply its successful terminal signature to reconstruct the revealed result from permanent on-chain evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| nonce | string | yes | Exact Shot nonce, not an automatically selected next nonce. |
| player | string | yes | Solana player public key. Never send a private key. |
| terminalSignature | string | – | Optional successful terminal transaction signature, not a seal or settle signature. |
No output schema declared.
No examples provided.
g2_prepare_seal ~163
Build and simulate an unsigned atomic seal transaction from an agent-generated commitment. Keep side, confidence and 32-byte random salt local. Requires current nonce, sufficient existing on-chain credits, and exact targets from g2_get_player. Does not sign or submit.
| Name | Type | Req | Description |
|---|---|---|---|
| commitment | string | yes | Canonical client commitmentHash hex, generated and saved locally with the reveal secret. |
| expectedEntryTargetTs | string | yes | Exact displayed entry target Unix seconds. |
| expectedExitTargetTs | string | yes | Exact displayed exit target Unix seconds. |
| nonce | string | yes | Exact Shot nonce, not an automatically selected next nonce. |
| player | string | yes | Solana player public key. Never send a private key. |
| stake | string | yes | Existing test credits to stake. |
No output schema declared.
No examples provided.
How do I install the RatchetX Forecast Arena MCP server?
RatchetX Forecast Arena is a hosted endpoint at https://ratchetx.xyz/api/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 · ratchetx.xyz
claude mcp add --transport http 3esign-ratchet 'https://ratchetx.xyz/api/mcp'
What is the RatchetX Forecast Arena MCP server?
RatchetX Forecast Arena is an MCP server listed in the public MCP registry as io.github.3esign/ratchet. Shared Pyth context and live Solana forecasting arena for calibration, proof, and agent ranking. This page covers its hosted endpoint (https://ratchetx.xyz/api/mcp).
Is the RatchetX Forecast Arena MCP server safe to use?
RatchetX Forecast Arena 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 RatchetX Forecast Arena MCP server expose?
RatchetX Forecast Arena exposes 5 tools: g2_get_game, g2_get_player, g2_get_shot, g2_prepare_seal, g2_get_reveal_context. Their descriptions and schemas cost roughly 406 tokens of context every time the server is loaded.
Does the RatchetX Forecast Arena MCP server require authentication?
Its publisher declares no required credentials for RatchetX Forecast Arena. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the RatchetX Forecast Arena MCP server still maintained?
RatchetX Forecast Arena is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.