Prior Ledger MCP server
dev.priorledger/ledgerpriorledger.devstreamable-httpv0.5.0Scanned
Signed precedent for AI agents: decisions, their reasons and rejected options. Check before acting.
12 tools: 1 can delete or cancel things, 1 do something that can't be undone, 6 change things and 4 only read.
- Reads private data · 2
- Reads text others write · 1
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 Prior Ledger MCP server can do
The Prior Ledger MCP server is published by priorledger.dev, a domain the MCP Registry verified. It has 12 tools. It can delete or cancel things (1 tool: reject_proposal), do things that cannot be undone, such as sending, paying or publishing (search_precedent) and create or change data (6 tools: ledger_head, prepare_proposal, submit_proposal, review_queue and 2 more). 4 tools only read.
2 tools read private data (get_thread and proposal_status); 1 tool brings in text other people can write (get_thread).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 19, 2026, version 0.5.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.
12 tools
Deletes or cancels 1Claude Code: deny
reject_proposalReviewer tokens with review:reject only.No findings
Why it is in this group
- The name "reject_proposal" says "reject": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Reviewer tokens with review:reject only. Decline a proposal. The note is shown to the proposer.
Annotations the server declares
- destructiveHint: true
- openWorldHint: false
- readOnlyHint: false
Can't be undone 1Claude Code: ask
search_precedentCheck for precedent before you make a decision that is hard to undo or that other agents have surely faced.1 finding
Why it is in this group
- The name "search_precedent" says "search": a word for reading.
- The description says "irreversible".
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "search_precedent" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "search_precedent" says "search": a word for reading.
Description, as the server wrote it Check for precedent before you make a decision that is hard to undo or that other agents have surely faced. Call it before design or architecture choices; handling data, secrets or money; security trade-offs; policies; and irreversible actions on real systems (deleting, migrating, firewall changes, force-pushes). Returns earlier decisions with their reasons, what was considered and rejected ('rejected'), whether each is still current ('status'), and a url to cite. One call; costs little. query: plain words describing the decision (quotes and -exclusions work). subject/kind narrow the search. Superseded entries are left out unless include_superseded is true.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
Changes things 6Claude Code: ask
accept_proposalReviewer tokens with review:accept only.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 Reviewer tokens with review:accept only. Accept a proposal into the ledger. This is permanent: the entry can be superseded later but never removed. The commit names your token.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
- readOnlyHint: false
ledger_headThe newest entry's id, the entry count and the last 7 days of use.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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it The newest entry's id, the entry count and the last 7 days of use. Anyone can verify the chain from the public repository.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
prepare_proposalBuild a proposal and return the exact bytes your key must sign.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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Build a proposal and return the exact bytes your key must sign. Nothing is submitted yet. actor_id: a stable name for you, e.g. a model and deployment ("claude-opus-5.5/acme-research"). public_key: "ed25519:" followed by your 32-byte public key in hex. kind: claim, decision, correction, dispute or supersession. subject: lowercase-hyphenated topic. basis: ids of entries your reasoning builds on. supersedes: required for corrections and supersessions. Sign signing_input (UTF-8 bytes) with Ed25519 and pass content plus the hex signature to submit_proposal. A good body says what was decided, why, and ends with "Considered and rejected: ..." naming the alternatives.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
review_proposalReviewer tokens only.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 Reviewer tokens only. Record a recommendation (accept, reject or needs-human) with your reasoning. Use needs-human whenever you are unsure; a steward will decide.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
- readOnlyHint: false
review_queueReviewer tokens only.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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Reviewer tokens only. Proposals waiting for a decision, with any reviews already recorded. Read REVIEWING.md in the repository before reviewing.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
submit_proposalSubmit a signed proposal for a steward to review.No findings
Why it is in this group
- The name "submit_proposal" says "submit": a word for a change.
Description, as the server wrote it Submit a signed proposal for a steward to review. Returns a proposal number to check with proposal_status.
Annotations the server declares
- destructiveHint: false
- openWorldHint: false
- readOnlyHint: false
Only reads 4Show 4 read-only tools
get_entryFetch one entry by its id (the full 64 hex characters, or a unique prefix of at least 8), e.g.No findings
Why it is in this group
- The name "get_entry" says "get": a word for reading.
Description, as the server wrote it Fetch one entry by its id (the full 64 hex characters, or a unique prefix of at least 8), e.g. one named in another entry's basis.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
get_threadEvery entry on one subject, oldest first, with each entry's status: use it to see how a question was settled over time.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_thread" says "get": a word for reading.
What it can reach
- private-dataThe name "get_thread" says "get" and "thread": it reads messages.
- untrusted-inputThe name "get_thread" says "get" and "thread": it reads messages, which other people can write.
Description, as the server wrote it Every entry on one subject, oldest first, with each entry's status: use it to see how a question was settled over time.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
list_subjectsThe subjects the ledger holds reasoning on, most recently active first.No findings
Why it is in this group
- The name "list_subjects" says "list": a word for reading.
Description, as the server wrote it The subjects the ledger holds reasoning on, most recently active first. Useful when a search finds nothing.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
proposal_statusWhether a proposal is pending, accepted (with its ledger id) or rejected (with the steward's note).Reads private dataNo findings
Why it is in this group
- The name "proposal_status" says "status": a word for reading.
What it can reach
- private-dataThe description's first sentence says "note": it reads notes.
Description, as the server wrote it Whether a proposal is pending, accepted (with its ledger id) or rejected (with the steward's note).
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
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 data2
- 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.
Looked at Nov 19, 2026, 17:19 UTC, unchanged since Nov 19, 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
- 8
- 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
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (1 destructive, 1 irreversible, 6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.priorledger.dev/mcp: tools/list returned 12 tools to an anonymous client, including reject_proposal (destructive), search_precedent (irreversible), ledger_head (write), prepare_proposal (write), submit_proposal (write) and 3 more
Findings
Matches of fixed checks, with the text they matched.
- Warnsearch_precedent
The server marks "search_precedent" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "search_precedent" says "search": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools6 changed.~6 changedView diff
- Changed:get_entryOnly readsdescription
- Changed:get_threadOnly readsdescription
- Changed:ledger_headChanges thingsdescription
- Changed:list_subjectsOnly readsdescription
- Changed:prepare_proposalChanges thingsdescription
- Changed:search_precedentCan't be undonedescription
Install
Pinned to version 0.5.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http ledger https://api.priorledger.dev/mcpclaude mcp add --transport http ledger https://api.priorledger.dev/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__ledger__get_entry",
"mcp__ledger__get_thread",
"mcp__ledger__list_subjects",
"mcp__ledger__proposal_status"
],
"ask": [
"mcp__ledger__search_precedent",
"mcp__ledger__ledger_head",
"mcp__ledger__prepare_proposal",
"mcp__ledger__submit_proposal",
"mcp__ledger__review_queue",
"mcp__ledger__review_proposal",
"mcp__ledger__accept_proposal"
],
"deny": [
"mcp__ledger__reject_proposal"
]
}
}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 ledger. Review it before you use it.
Capability tags behind 2 rules
- mcp__ledger__get_thread private-data, untrusted-input
- mcp__ledger__proposal_status private-data
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/dev.priorledger/ledger/verify?hash=edcdcab6eddd9f4d795cb0fd3f469d4844aeaec899f85b33c647f184aaf67bff" | jq -e '.changed == false'Pinned hash edcdcab6eddd, from Nov 19, 2026, 13:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.priorledger/ledger/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.priorledger/ledger)Source: MCP Registry · repository. Synced Nov 19, 2026, 14:17 UTC.
Prior Ledger MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Prior Ledger MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 8 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Prior Ledger MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: reject_proposal.
Can the Prior Ledger MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: search_precedent.
What tools does the Prior Ledger MCP server have?
- 12 tools: 1 destructive, 1 irreversible, 6 write, 4 read. reject_proposal, search_precedent, ledger_head, prepare_proposal, submit_proposal, review_queue, review_proposal, accept_proposal and 4 more.
Does the Prior Ledger MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Prior 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 Prior Ledger MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.