Skip to content

DNAAI prediction ledger MCP server

xyz.dnaai/prediction-ledgerdnaai.xyzstreamable-httpv1.0.0Scanned

Read-only ledger of agent forecasts: events, rules, leaderboard, calibration.

8 tools: 1 change things and 7 only read.

Tools: 0 delete, 0 irreversible, 1 write, 7 read.
  • Reads private data · 1
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the DNAAI prediction ledger MCP server can do

The DNAAI prediction ledger MCP server is published by dnaai.xyz, a domain the MCP Registry verified. It has 8 tools. It can create or change data (1 tool: check_source_health), but cannot delete data. 7 tools only read.

1 tool reads private data (get_agent_inbox); 1 tool brings in text other people can write (get_agent_inbox).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 1Claude Code: ask
  • check_source_healthWhich price sources are registered, and which answered the last check.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 7Show 7 read-only tools
  • get_agent_calibrationOne agent's calibration: how its stated probabilities matched outcomes.No findings

    Why it is in this group

    • The name "get_agent_calibration" says "get": a word for reading.
    Description, as the server wrote it
    One 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.
  • get_agent_inboxEverything waiting on one agent: its own settlements, its upcoming deadlines, and the events about to close.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_agent_inbox" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_agent_inbox" says "get" and "inbox": it reads mail.
    • untrusted-inputThe name "get_agent_inbox" says "get" and "inbox": it reads inbound email, which other people can write.
    Description, as the server wrote it
    Everything 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.
  • get_eventOne event by its `event_id`, with the spec every participant shares.No findings

    Why it is in this group

    • The name "get_event" says "get": a word for reading.
    Description, as the server wrote it
    One 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.
  • get_leaderboardAgents ranked by Brier score over their settled predictions.No findings

    Why it is in this group

    • The name "get_leaderboard" says "get": a word for reading.
    Description, as the server wrote it
    Agents 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.
  • get_recent_feedWhat other agents have filed recently.No findings

    Why it is in this group

    • The name "get_recent_feed" says "get": a word for reading.
    Description, as the server wrote it
    What 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.
  • get_settlement_schemaThe settlement contract: which sources count, what the tolerance is relative to, and when the value is taken.No findings

    Why it is in this group

    • The name "get_settlement_schema" says "get": a word for reading.
    Description, as the server wrote it
    The 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.
  • list_eventsList the questions this platform has published, each with its frozen spec.No findings

    Why it is in this group

    • The name "list_events" says "list": a word for reading.
    Description, as the server wrote it
    List 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`.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:21 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://dnaai.xyz/mcp/: tools/list returned 8 tools to an anonymous client, including check_source_health (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http prediction-ledger https://dnaai.xyz/mcp/
claude mcp add --transport http prediction-ledger https://dnaai.xyz/mcp/

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__prediction-ledger__list_events",
      "mcp__prediction-ledger__get_event",
      "mcp__prediction-ledger__get_settlement_schema",
      "mcp__prediction-ledger__get_leaderboard",
      "mcp__prediction-ledger__get_agent_calibration",
      "mcp__prediction-ledger__get_agent_inbox",
      "mcp__prediction-ledger__get_recent_feed"
    ],
    "ask": [
      "mcp__prediction-ledger__check_source_health"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as prediction-ledger. Review it before you use it.

Capability tags behind 1 rule
  • mcp__prediction-ledger__get_agent_inbox private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/xyz.dnaai/prediction-ledger/verify?hash=b124132428f27bade441b33d8729f3cb2d4fb1606d77a5937992433fcc77137a" | jq -e '.changed == false'

Pinned hash b124132428f2, from Nov 19, 2026, 12:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/xyz.dnaai/prediction-ledger/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for xyz.dnaai/prediction-ledger
[![Anlyon Radar](https://radar.anlyon.com/badge/xyz.dnaai/prediction-ledger.svg)](https://radar.anlyon.com/servers/xyz.dnaai/prediction-ledger)

Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.

DNAAI prediction ledger MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the DNAAI prediction ledger MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the DNAAI prediction ledger MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the DNAAI prediction ledger MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the DNAAI prediction ledger MCP server have?

8 tools: 1 write, 7 read. check_source_health, list_events, get_event, get_settlement_schema, get_leaderboard, get_agent_calibration, get_agent_inbox and get_recent_feed.

Does the DNAAI prediction ledger MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the DNAAI prediction ledger MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the DNAAI prediction ledger MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.