Annalist

Official registry Data and databases

Signed data for agents: agentic-commerce census, dependency digest, x402/MCP checks, Hyperliquid

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http annalist 'https://api.annalist.dev/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "annalist": {
            "type": "http",
            "url": "https://api.annalist.dev/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Annalist ledger
  2. What is in it
  3. Verifying
  4. Contact

Annalist ledger

Annalist (annalist.dev) keeps an append-only archive of crowd-state data for AI agents. This public repository is its ledger: once a day it records a fingerprint of everything the archive wrote the day before, signed and timestamped in Bitcoin. It lets anyone check that a record existed on a given date, so the history cannot have been backfilled or quietly edited later.

What is in it

  • ledger/YYYY/MM/YYYY-MM-DD.json: one entry per UTC day.
    • entry.manifests: every run manifest written that day, each with the sha256 of the manifest file.
    • entry.root: sha256 of the manifest hashes joined by newlines, in the listed order.
    • signature: Ed25519 over the canonical JSON of entry (keys sorted, no spaces, UTF-8).
  • ledger/YYYY/MM/YYYY-MM-DD.json.ots: an OpenTimestamps proof that the entry file existed at that time. Proofs start as pending and are upgraded to full Bitcoin attestations within a day or two.
  • keys/<key_id>.json: public signing keys. The current key is 187e49f200625a2f.

Each run manifest in turn lists every archive file written by that run with its sha256 and size, and is signed with the same key. Data responses served by the Annalist API carry the same kind of signature.

Verifying

  1. Check the timestamp: ots verify ledger/2026/10/2026-10-13.json.ots (needs the OpenTimestamps client and a Bitcoin block source, or use opentimestamps.org).
  2. Check the signature: verify signature against the canonical JSON of entry with the public key in keys/.
  3. Given a manifest from the archive, hash its file bytes with sha256 and find that hash in the day's entry.

Contact

Open an issue on this repository.

Frequently asked questions

What is Annalist?

Signed data for agents: agentic-commerce census, dependency digest, x402/MCP checks, Hyperliquid

How do I install Annalist?

It runs as a remote server. In Claude Code: claude mcp add --transport http annalist 'https://api.annalist.dev/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Annalist need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Annalist open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains Annalist?

It is published by ryanroskowski. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.