thePaymentsNotes Ledger
REMOTE · TPN-GATEWAY.ALWAYSARAFATH.WORKERS.DEV
Verified agentic-commerce protocol status + merchant agent-readiness reports. Free on testnet.
Available components
Last scanned (22 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1047 tokens (~174/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 826 → 1047 ▼ functional
- Schema quality: good → excellent functional
- Server version: 0.3.3-testnet → 0.4.0-testnet functional
- New tool “query_ledger” functional
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://tpn-gateway.alwaysarafath.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=alwaysarafath.workers.dev | CN=WE1,O=Google Trust Services,C=US | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 56bc867da5f2bba70eaaaa1511124cdc |
| SANs: alwaysarafath.workers.dev, *.alwaysarafath.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tpn-gateway.alwaysarafath.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tpn-gateway.alwaysarafath.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://tpn-gateway.alwaysarafath.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_agent_readiness ~330
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 ("v4"), 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, 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
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Bare domain only, e.g. 'yourstore.com' (no https://, path or port) |
No output schema declared.
No examples provided.
get_status ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| protocol | string | yes | Ledger name or short name, e.g. 'x402', 'MPP', 'Stripe Link', 'Agent Pay'. Covers protocols, platforms, wallets and stablecoins. Call list_protocols for every name. |
No output schema declared.
No examples provided.
get_status_detail ~165
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.
| Name | Type | Req | Description |
|---|---|---|---|
| protocol | string | yes | Ledger name or short name, e.g. 'x402', 'MPP', 'Stripe Link', 'Agent Pay'. Covers protocols, platforms, wallets and stablecoins. Call list_protocols for every name. |
No output schema declared.
No examples provided.
list_protocols ~56
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
query_ledger ~211
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"]}, ...]}.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max hits, 1-5 (default 3) |
| query | string | yes | Plain-English question or keywords, e.g. 'pay per API request with stablecoins' or 'Visa agent identity'. Max 200 chars. |
No output schema declared.
No examples provided.
whats_new ~51
Free on testnet. Recent verified Ledger changes since a date (last 30 days, max 5 items): headline, status, date, one source.
| Name | Type | Req | Description |
|---|---|---|---|
| since_date | string | yes | YYYY-MM-DD |
No output schema declared.
No examples provided.
How do I install the thePaymentsNotes Ledger MCP server?
thePaymentsNotes Ledger is a hosted endpoint at https://tpn-gateway.alwaysarafath.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · tpn-gateway.alwaysarafath.workers.dev
claude mcp add --transport http alwaysarafath-thepaymentsnotes-ledger 'https://tpn-gateway.alwaysarafath.workers.dev/mcp'
What is the thePaymentsNotes Ledger MCP server?
thePaymentsNotes Ledger is an MCP server listed in the public MCP registry as io.github.alwaysarafath/thepaymentsnotes-ledger. Verified agentic-commerce protocol status + merchant agent-readiness reports. Free on testnet. This page covers its hosted endpoint (https://tpn-gateway.alwaysarafath.workers.dev/mcp).
Is the thePaymentsNotes Ledger MCP server safe to use?
thePaymentsNotes Ledger scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the thePaymentsNotes Ledger MCP server expose?
thePaymentsNotes Ledger exposes 6 tools: list_protocols, check_agent_readiness, query_ledger, get_status, whats_new, get_status_detail. Their descriptions and schemas cost roughly 945 tokens of context every time the server is loaded.
Does the thePaymentsNotes Ledger MCP server require authentication?
No. We connected to thePaymentsNotes Ledger without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the thePaymentsNotes Ledger MCP server still maintained?
thePaymentsNotes Ledger is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.