ReceiptRail
REMOTE · AGENTTOLL-RECEIPTS.APP.WORKBUDDY.HOST
Read-only on-chain receipt check for x402 payments; confirm settlement before trusting a tx.
Available components
Last scanned (17 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Crypto and Web3
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 435 tokens (~145/item across 3 items; 3 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 Management69
- Stability check failed: schema churn in the 29 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 31 Oct 26 0
- Stability: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- TLS certificate: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 30 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 28 Oct 26 −4
- Stability: pass → fail ▼ security
- 17 Oct 26 0
- Stability: 0.97 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 −1
- A breaking change shipped without a version bump: still 0.3.0 ▼ security
- Tool “verify_x402_receipt” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 167 → 145 ▲ functional
- Schema quality: excellent → good functional
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 83. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 25 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://agenttoll-receipts.app.workbuddy.host/mcp
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.workbuddy.host,O=Tencent Technology (Shenzhen) Company Limited,L=Shenzhen,ST=Guangdong Province,C=CN | CN=DigiCert Secure Site OV G2 TLS CN RSA4096 SHA256 2022 CA1,O=DigiCert\, Inc.,C=US | 10 Sept 2026 | 27 Mar 2027 | RSA 2048 | SHA256-RSA | 42d0278b23e5092a1c8540bc7c33f21 |
| SANs: *.workbuddy.host, workbuddy.host, *.app-staging.workbuddy.host, *.app-tencent.workbuddy.host, *.app.workbuddy.host, *.apps-staging.workbuddy.host, *.apps.workbuddy.host | ||||||
| CN=DigiCert Secure Site OV G2 TLS CN RSA4096 SHA256 2022 CA1,O=DigiCert\, Inc.,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 15 Dec 2022 | 14 Dec 2032 | RSA 4096 | SHA256-RSA | 4c1b960191fcabedcda9301a6cd78c3 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of agenttoll-receipts.app.workbuddy.host. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| host. | present | 29155 | 13 | Verified |
| workbuddy.host. | 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://agenttoll-receipts.app.workbuddy.host/mcp | Verified | 200 | |
| http (plaintext) | http://agenttoll-receipts.app.workbuddy.host/mcp | HTTPS enforced | 302 | HTTPS://agenttoll-receipts.app.workbuddy.host/mcp |
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 →
get_receipt Get receipt details ~106
Fetch full receipt details: digests, checks, outcome, amount, buyer, seller, timestamp, PDA. Look up by receipt_id, or by x402_payment_ref (always works — the receipt lives on-chain). Read-only, no cost.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_ref | string | – | x402_payment_ref of the transaction (use this if receipt_id unknown; resolved on-chain) |
| receipt_id | string | – | Receipt id, e.g. r_abcdef1234567890 |
No output schema declared.
No examples provided.
issue_receipt Issue delivery receipt ~191
Anchor a SHA-256 digest of delivered content plus the x402 settlement reference on Solana. Returns a permanent, publicly verifiable receipt (poll until outcome === "settled"). Costs 0.001 USDC via x402; if x402_payment_signature is omitted, returns the payment challenge instead (pay 0.001 USDC to the service address, then call again with the payment tx signature).
| Name | Type | Req | Description |
|---|---|---|---|
| buyer | string | – | Optional buyer identifier (wallet address) |
| deliverable_digest | string | yes | SHA-256 hex digest (64 chars) of the delivered content |
| seller | string | – | Optional seller identifier |
| x402_payment_ref | string | yes | Unique reference for this transaction (1-128 chars) |
| x402_payment_signature | string | – | Solana tx signature of the 0.001 USDC payment to the service address. Omit to receive the payment challenge. |
No output schema declared.
No examples provided.
verify_receipt Verify delivery receipt ~114
Verify an AgentToll receipt against live Solana state: PDA owner must be the AgentToll program and the stored digest must match the receipt. Look up by receipt_id, or by x402_payment_ref (always works — the receipt lives on-chain). Read-only, no cost.
| Name | Type | Req | Description |
|---|---|---|---|
| payment_ref | string | – | x402_payment_ref of the transaction (use this if receipt_id unknown; resolved on-chain) |
| receipt_id | string | – | Receipt id, e.g. r_abcdef1234567890 |
No output schema declared.
No examples provided.
How do I install the ReceiptRail MCP server?
ReceiptRail is a hosted endpoint at https://agenttoll-receipts.app.workbuddy.host/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 · agenttoll-receipts.app.workbuddy.host
claude mcp add --transport http xka0085-byte-receiptrail 'https://agenttoll-receipts.app.workbuddy.host/mcp'
What is the ReceiptRail MCP server?
ReceiptRail is an MCP server listed in the public MCP registry as io.github.xka0085-byte/receiptrail. Read-only on-chain receipt check for x402 payments; confirm settlement before trusting a tx. This page covers its hosted endpoint (https://agenttoll-receipts.app.workbuddy.host/mcp).
Is the ReceiptRail MCP server safe to use?
ReceiptRail scores 71 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 ReceiptRail MCP server expose?
ReceiptRail exposes 3 tools: issue_receipt, verify_receipt, get_receipt. Their descriptions and schemas cost roughly 411 tokens of context every time the server is loaded.
Does the ReceiptRail MCP server require authentication?
No. We connected to ReceiptRail without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the ReceiptRail MCP server still maintained?
ReceiptRail 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.