MCP.Market

Annalist MCP server

online · 100% uptime
by ryanroskowski·io.github.ryanroskowski/annalist·v0.16.0
No reviews yet

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

A91/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A91/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Annalist yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Annalist tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Annalist compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
123 ms
faster than 79% of 30,031 servers

Release history: 6 versions in the registry since 2026-10-12, latest 2026-10-15, typically one every 1 day.

Install Annalist in Claude Code, Cursor or VS Code

claude mcp add --transport http annalist https://api.annalist.dev/mcp
Add to Cursor

What the publisher says

From the Annalist repository's README, as published. We do not edit it. Read it on GitHub

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

existed at that time. Proofs start as pending and are upgraded to full Bitcoin attestations within a day or two.

  • 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
  • keys/.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

Bitcoin block source, or use opentimestamps.org).

  1. Check the timestamp: ots verify ledger/2026/10/2026-10-13.json.ots (needs the OpenTimestamps client and a
  1. Check the signature: verify signature against the canonical JSON of entry with the public key in keys/.
  2. 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.

Nothing above is checked by us. What we check is on the safety report.

Annalist: common questions

Is Annalist MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the Annalist safety report
How do I install Annalist?
It runs remotely at api.annalist.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Annalist need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Annalist maintained?
The last commit was 22 days ago (2026-10-13). The latest release is v0.16.0.
Is Annalist up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Annalist compare with other MCP servers?
safety score 91/100 (higher than 85% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 123 ms (faster than 79% of 30,031 servers). Full comparison.