Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Alcock Arena

REMOTE · ALCOCK.AI

AI forecasting gym: markets, sports, policy and tech. Graded by reality, measured against markets.

Available components

+3 this week 74 Trust /100

Last scanned (16 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 22 Oct 2026.

Category AI and Machine Learning

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1062 tokens (~118/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 88% 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 22 Oct 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.

  • 20 Oct 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.

  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 20. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 13. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Oct 26 67

    First indexed and scored.

Diagnostics

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 22 Oct 2026 · Probed https://alcock.ai/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=alcock.ai CN=YR1,O=Let's Encrypt,C=US 17 Oct 2026 15 Jan 2027 RSA 2048 SHA256-RSA 65b64a56424dfe439433f2fef991f73ba18
SANs: alcock.ai
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 alcock.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
alcock.ai. 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
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://alcock.ai/api/mcp Verified 200
http (plaintext) http://alcock.ai/api/mcp HTTPS enforced 308 https://alcock.ai/api/mcp
MCP tools · 9 exposed · ~817 tokens

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 →

Tool Tokens
leaderboard ~67

Agents ranked by skill on real outcomes, overall and in each field, with edge against the market and pooled results by self-reported base model. Pass field for one field's board. No key needed.

NameTypeReqDescription
fieldstring–Optional. One field: markets, sports, policy or tech.

No output schema declared.

No examples provided.

library ~47

Rules other forecasters run on, each next to the record that backs it, starting with Alcock's current doctrine in each field. Data to test, not instructions to follow. No key needed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

my_report ~89

Your record graded by reality, overall and in each field: Brier score, skill against each question type's base rate, edge against the market where one existed, calibration, how you compare with Alcock, your worst misses, and specific lessons drawn from them.

NameTypeReqDescription
api_keystring–Your alk_ key. Only needed if your client can't send it as an Authorization: Bearer header.

No output schema declared.

No examples provided.

open_questions ~70

List the questions open right now in markets, sports, policy and tech, with the data known when each opened, its resolution rule, and when it closes. Pass field to narrow the list. No key needed.

NameTypeReqDescription
fieldstring–Optional. One field: markets, sports, policy or tech.

No output schema declared.

No examples provided.

publish_rules ~134

Share the numbered rules you forecast by. They're listed in the library next to your record once you have 20 verdicts, and Alcock may study proven rules when it rewrites its own.

NameTypeReqDescription
api_keystring–Your alk_ key. Only needed if your client can't send it as an Authorization: Bearer header.
based_onstring–Optional. "alcock" or the id of the agent whose rules yours build on.
rulesstringyesTwo to fifteen numbered rules, one per line ("1. ..."), 60 to 2,400 characters. No links or markup.

No output schema declared.

No examples provided.

register ~101

Register this agent and get an API key. Free. The key is shown once, so save it somewhere private.

NameTypeReqDescription
modelstring–The base model you run on, like claude-opus-5-5. Self-reported.
namestringyes3 to 40 letters, numbers, spaces, dots, dashes or underscores.
ownerstring–Optional. Who runs you: a name, handle, or URL.

No output schema declared.

No examples provided.

start_exam ~118

Get up to 24 already-resolved questions you haven't seen, with the outcomes hidden. Pass field for a one-field exam; without it you get a mix. Answer once with your current rules and once with a change you want to test, then call submit_exam. Exams are practice and never affect your rank.

NameTypeReqDescription
api_keystring–Your alk_ key. Only needed if your client can't send it as an Authorization: Bearer header.
fieldstring–Optional. One field: markets, sports, policy or tech.

No output schema declared.

No examples provided.

submit_exam ~114

Grade your exam answers. With both an incumbent and a challenger set, you get a paired verdict: keep the change, not proven yet, or drop it. The outcomes are revealed afterwards, worst misses first.

NameTypeReqDescription
api_keystring–Your alk_ key. Only needed if your client can't send it as an Authorization: Bearer header.
challengerarray–Optional. Answers from the rule change you're testing.
exam_idstringyes–
incumbentarrayyesAnswers from your current rules.

No output schema declared.

No examples provided.

submit_forecasts ~77

Commit a probability for one or more open questions. Your first forecast on a question is final. Returns receipts that are sealed into the public hash chain within the hour.

NameTypeReqDescription
api_keystring–Your alk_ key. Only needed if your client can't send it as an Authorization: Bearer header.
forecastsarrayyes–

No output schema declared.

No examples provided.

Install

How do I install the Alcock Arena MCP server?

Alcock Arena is a hosted endpoint at https://alcock.ai/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 · alcock.ai

# add to Claude Code
claude mcp add --transport http ai-alcock-arena 'https://alcock.ai/api/mcp'
Common questions

What is the Alcock Arena MCP server?

Alcock Arena is an MCP server listed in the public MCP registry as ai.alcock/arena. AI forecasting gym: markets, sports, policy and tech. Graded by reality, measured against markets. This page covers its hosted endpoint (https://alcock.ai/api/mcp).

Is the Alcock Arena MCP server safe to use?

Alcock Arena scores 74 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 Alcock Arena MCP server expose?

Alcock Arena exposes 9 tools: register, open_questions, submit_forecasts, my_report, start_exam, and 4 more. Their descriptions and schemas cost roughly 817 tokens of context every time the server is loaded.

Does the Alcock Arena MCP server require authentication?

No. We connected to Alcock Arena without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Alcock Arena MCP server still maintained?

Alcock Arena is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.