thePaymentsNotes Ledger MCP server
io.github.alwaysarafath/thepaymentsnotes-ledgeralwaysarafathstreamable-httpv0.3.0-testnetScanned
Verified agentic-commerce protocol status + merchant agent-readiness reports. Free on testnet.
6 tools: 2 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. 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 thePaymentsNotes Ledger MCP server can do
The thePaymentsNotes Ledger MCP server is published by the GitHub account alwaysarafath. It has 6 tools. It can create or change data (2 tools: check_agent_readiness and whats_new), but cannot delete data. 4 tools only read.
1 tool brings in text other people can write (check_agent_readiness).
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, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 0.3.0-testnet.
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.
6 tools
Changes things 2Claude Code: ask
check_agent_readinessFree on testnet.Reads text others writeNo 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.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Free on testnet. Automated scan, not human-verified. Scan-only quick read of whether AI agents can discover and buy from a website. Returns the engine's report as-is: scanner_version and scan_id ("v6"), report.score (scan-only), report.band (can be 'Partly assessed'), report.coverage, report.summary, report.confidence, report.can_agents_buy, report.who_eats_the_loss (display label "Who carries the risk?"; needs the 5 answers, so not assessed here), report.archetype ('unclassified' if not classified), report.rows (with unknown_reason), report.gaps, report.actions (always exactly 3: 2 business then 1 technical, each with kind "business" | "technical"), report.ledger (related Ledger entries), checks, evidence, findings, chatgpt_wallet (ChatGPT Wallet and cloud browser rules from OpenAI's public merchant guides: each rule is MATCH, NOT_MATCH or UNKNOWN with why, fix steps and the OpenAI source; UNKNOWN means it cannot be seen from outside; possible_block marks a block seen by our unsigned request, not proof; it does not change the score), and scan_interrupted.reason (timeout|blocked|dns_tls|robots_disallowed|refused|http_error) when the scan could not finish. Input: a bare domain (e.g. "yourstore.com"). It reads public pages only; it is NOT a certification, audit or legal advice. Open questions only the business can answer come back with a link to https://thepaymentsnotes.com/readiness. Limits: 3 scans per caller per day and 50 per day overall, shared with the website; results are cached for 24h. Weekly newsletter: https://thepaymentstack.substack.com
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
whats_newFree on testnet.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 Free on testnet. Recent verified Ledger changes since a date (last 30 days, max 5 items): headline, status, date, one source.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 4Show 4 read-only tools
get_statusFree on testnet.No findings
Why it is in this group
- The name "get_status" says "get": a word for reading.
Description, as the server wrote it Free on testnet. Status of one Ledger row (protocol, platform, wallet or stablecoin) from the human-verified Ledger: headline, status, last verified date and ONE source URL. If the name is not in the Ledger: result="unknown" plus up to 3 did_you_mean names (never a guessed answer). Call list_protocols to see every name.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_status_detailFree on testnet (no payment, no wallet needed).No findings
Why it is in this group
- The name "get_status_detail" says "get": a word for reading.
Description, as the server wrote it Free on testnet (no payment, no wallet needed). Fuller answer for ONE Ledger row (protocol, platform, wallet or stablecoin): headline, status (authoritative), maturity (a plain-English stage derived from status, never contradicts it), steward, what_this_means (the detail after the headline, omitted if there is none), latest update date, verified date and up to 3 sources. Unknown names return result="unknown" with up to 3 did_you_mean names. Call list_protocols to see every name.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_protocolsFree on testnet.No findings
Why it is in this group
- The name "list_protocols" says "list": a word for reading.
Description, as the server wrote it Free on testnet. Every row in the human-verified Ledger (protocols, platforms, wallets, stablecoins): name, short names/aliases and status only. Use a name from here with get_status or get_status_detail.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
query_ledgerFree on testnet.No findings
Why it is in this group
- The name "query_ledger" says "query": a word for reading.
Description, as the server wrote it Free on testnet. Free-text keyword search over the human-verified Ledger (protocols, platforms, wallets, stablecoins). Returns up to 5 matching row NAMES with status, a relevance score and which fields matched (exact_name, name, steward, status, text). It returns names, not answers: call get_status or get_status_detail with a returned name for the verified headline, date and source. No match returns result="none" (never a guess). Example: {"query":"pay per API request for a data feed","limit":3} -> {"result":"found","hits":[{"name":"x402","status":"Live (Limited)","score":9.1,"matched":["text"]}, ...]}.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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 private-data or outbound.
- Reads private data0
- 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 20, 2026, 19:01 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
- 2
- 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 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://tpn-gateway.alwaysarafath.workers.dev/mcp: tools/list returned 6 tools to an anonymous client, including check_agent_readiness (write), whats_new (write)
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.
Tools1 changed.~1 changedView diff
- Changed:check_agent_readinessChanges thingsdescription
Tools1 added.+1 addedView diff
- Added:query_ledgerOnly reads
Install
Pinned to version 0.3.0-testnet. Values in angle brackets are yours to fill in.
claude mcp add --transport http thepaymentsnotes-ledger https://tpn-gateway.alwaysarafath.workers.dev/mcpclaude mcp add --transport http thepaymentsnotes-ledger https://tpn-gateway.alwaysarafath.workers.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__thepaymentsnotes-ledger__list_protocols",
"mcp__thepaymentsnotes-ledger__query_ledger",
"mcp__thepaymentsnotes-ledger__get_status",
"mcp__thepaymentsnotes-ledger__get_status_detail"
],
"ask": [
"mcp__thepaymentsnotes-ledger__check_agent_readiness",
"mcp__thepaymentsnotes-ledger__whats_new"
],
"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 thepaymentsnotes-ledger. Review it before you use it.
Capability tags behind 1 rule
- mcp__thepaymentsnotes-ledger__check_agent_readiness 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/io.github.alwaysarafath/thepaymentsnotes-ledger/verify?hash=6af917ba7031d7cfc843b00203162afa1e5381111998340c4b9238d9e7c313b8" | jq -e '.changed == false'Pinned hash 6af917ba7031, from Nov 16, 2026, 22:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.alwaysarafath/thepaymentsnotes-ledger/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.alwaysarafath/thepaymentsnotes-ledger)Source: MCP Registry. Synced Oct 21, 2026, 18:22 UTC.
thePaymentsNotes Ledger MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the thePaymentsNotes Ledger MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 2 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 thePaymentsNotes 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 thePaymentsNotes 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 thePaymentsNotes Ledger MCP server have?
- 6 tools: 2 write, 4 read. check_agent_readiness, whats_new, list_protocols, query_ledger, get_status and get_status_detail.
Does the thePaymentsNotes Ledger MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the thePaymentsNotes 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 thePaymentsNotes Ledger MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.