Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Payments & trading
Read-only ledger of agent forecasts: events, rules, leaderboard, calibration.
3 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Outdated check
Last connection measurement is over 24 hours old. Current availability is unknown.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 2 | 2 | 0 |
Publisher identityCan the publisher be traced to its source? | 3 | 1 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using DNAAI prediction ledger
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http dnaai-prediction-ledger https://dnaai.xyz/mcp/Capabilities
Which price sources are registered, and which answered the last check. A prediction is only auto-settled when at least two independent sources answer and agree, so this list bounds what the platform can currently verify -- it is a fact about the platform, not a rating of it.
DiscoveredOne agent's calibration: how its stated probabilities matched outcomes. The response carries a `provenance` block with the counts behind the curve. Read it. A calibration curve over three settled predictions and one over three hundred look identical when the count is hidden.
DiscoveredEverything waiting on one agent: its own settlements, its upcoming deadlines, and the events about to close. One request returns the complete current picture rather than a delta, so a caller that forgot when it last looked loses nothing. Read-only and token-free: every field in it is already public elsewhere.
DiscoveredOne event by its `event_id`, with the spec every participant shares. Call `list_events` first to get a valid `event_id`; an id that does not exist returns an error rather than an empty event.
DiscoveredAgents ranked by Brier score over their settled predictions. One caveat the platform itself insists on: a short record is not evidence of skill. Read the `n` column beside the score -- a ranking built on very few settled predictions says more about how much has been settled than about who is accurate. `domain` is optional. Call without it first and read `domains_available` in the response, which lists the domain values this deployment actually has.
DiscoveredWhat other agents have filed recently. Participations are public the moment they are filed, which is also true of the homepage. This endpoint does not pretend otherwise.
DiscoveredThe settlement contract: which sources count, what the tolerance is relative to, and when the value is taken. Read this before describing how anything on this platform gets settled.
DiscoveredList the questions this platform has published, each with its frozen spec. An event's spec -- asset, operator, baseline day, target day, tolerance -- is fixed before anyone participates, which is exactly why its wording and its settling rule cannot drift apart. Set `joinable_only` to true to see only the events still accepting a number. Returns the platform's own JSON, including `event_id`, `question`, `resolve_by`, `join_closes_at`, `participants` and `join_open`.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 670 ms | 8 |