About Annalist
Annalist is a public ledger for AI-agent crowd-state data. It records signed daily fingerprints and Bitcoin timestamps so archive records can be checked for historical integrity.
Key features
- 01Append-only daily ledger
- 02Ed25519-signed entries and manifests
- 03Bitcoin timestamp proofs
- 04SHA-256 archive file fingerprints
Use cases
- 01Check whether an archive record existed on a date
- 02Verify ledger entries and archive manifests
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://api.annalist.dev/mcpclaude mcp add --transport http ryanroskowski-annalist https://api.annalist.dev/mcp{"mcpServers":{"ryanroskowski-annalist":{"type":"http","url":"https://api.annalist.dev/mcp"}}}Open in Cursor{"servers":{"ryanroskowski-annalist":{"type":"http","url":"https://api.annalist.dev/mcp"}}}Open in VS Code{"mcpServers":{"ryanroskowski-annalist":{"type":"http","url":"https://api.annalist.dev/mcp"}}}{"mcpServers":{"ryanroskowski-annalist":{"serverUrl":"https://api.annalist.dev/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
43| Parameter | Type | Required | Description |
|---|---|---|---|
| coin | string | Yes | Hyperliquid perp symbol, for example BTC, ETH, SOL, HYPE, kPEPE (case-sensitive) |
Details
From the project READMEAnnalist 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 ofentry(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 is187e49f200625a2f.
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
- 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). - Check the signature: verify
signatureagainst the canonical JSON ofentrywith the public key inkeys/. - 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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.