MoneyTools payment-safety suite
REMOTE · MCP.MONEYTOOLS.DEV
Call before paying any x402 seller: 402/OFAC precheck, verify, approval, ledger
Available components
Last scanned (19 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 21 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 Security46
- 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 1 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability56
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1060 tokens (~176/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 Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
- Structured output schemas are declared (33% of tools); any adoption earns full credit.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
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “x402_precheck” rewrote its description, which is the text the model reads security
- Tool “x402_verify_settlement” rewrote its description, which is the text the model reads security
- Server version: 2.11.19 → 2.11.20 functional
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 0
- Server version: 2.11.18 → 2.11.19 functional
- 18 Nov 26 0
- Server version: 2.11.16 → 2.11.18 functional
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 0
- Server version: 2.11.13 → 2.11.16 functional
- 15 Nov 26 +1
- Server version: 2.11.11 → 2.11.13 functional
- 13 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
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 21 Nov 2026 · Probed https://mcp.moneytools.dev/mcp/payment-safety
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=moneytools.dev | CN=WE1,O=Google Trust Services,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 5197e04c599067f7136ea382f4c80923 |
| SANs: moneytools.dev, mcp.moneytools.dev, *.mcp.moneytools.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 mcp.moneytools.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| moneytools.dev. | No DS | 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://mcp.moneytools.dev/mcp/payment-safety | Verified | 200 | |
| http (plaintext) | http://mcp.moneytools.dev/mcp/payment-safety | Served over HTTP | 200 |
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 →
approval_request Ask your human to approve a payment ~295
Create a human approval request (Approval Relay). Show approveUrl / approve_url to your human, then poll approval_status. Served by Approval Relay at relay.moneytools.dev (0.005 USDC, 3 free/day; signed Ed25519 receipt). Old field names (title, approveUrl, id, agentToken, proof) are still accepted and returned as aliases. approve.moneytools.dev stays available for existing HTTP/MCP callers.
| Name | Type | Req | Description |
|---|---|---|---|
| action_summary | string | – | Plain-language description of the action (preferred) |
| amountUsd | number | – | Optional context folded into action_summary |
| callback_url | string | – | Optional https callback that receives the signed receipt |
| details | string | – | Optional extra context folded into action_summary |
| expires_in_s | integer | – | Seconds until expiry (default 3600) |
| host | string | – | Optional context folded into action_summary |
| network | string | – | – |
| notify | object | – | Legacy; notify.webhook is used as callback_url if set |
| payTo | string | – | Optional context folded into action_summary |
| requester | string | – | Optional label shown to the approver |
| risk | string | – | Risk level shown to the approver (default med) |
| title | string | – | Alias of action_summary (legacy approval_request field) |
| ttlMinutes | number | – | Legacy alias of expires_in_s (minutes, 5-1440) |
No output schema declared.
No examples provided.
approval_status Approval status ~115
Check whether the human approved, denied or let the request expire (free). Approved results include receipt_jws (also aliased as proof).
| Name | Type | Req | Description |
|---|---|---|---|
| agentToken | string | – | Legacy; ignored for Relay requests (apr-… ids) |
| approval_id | string | – | – |
| id | string | – | – |
| wait | integer | – | Optional long-poll seconds for get/status (Relay max 25 without SSE) |
| wait_seconds | integer | – | Optional long-poll seconds for get/status (Relay max 25 without SSE) |
No output schema declared.
No examples provided.
approval_verify Verify an approval proof ~43
Verify a Relay receipt_jws (free). The legacy 'proof' argument is also accepted.
| Name | Type | Req | Description |
|---|---|---|---|
| proof | string | – | – |
| receipt_jws | string | – | – |
No output schema declared.
No examples provided.
ledger_gateway Spend ledger (Pay Gateway receipts) ~76
Totals, by supplier, by day and exceptions for payments relayed by the MoneyTools Pay Gateway for this API key (free; needs X-API-Key). Currency default USD. [served by ledger.moneytools.dev]
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | – |
| days | number | – | – |
| month | string | – | YYYY-MM |
No output schema declared.
No examples provided.
x402_precheck Pre-check an x402 payment ~143
[FREE tier 20/day, then $0.005] Before paying an x402 endpoint: fetch it, validate its HTTP 402 payment requirements (scheme, network, payTo, amount, asset) and screen payTo against the OFAC SDN crypto-address list. Returns verdict ok|warn|block|not_402. Free to try: 20 MCP calls/day per client, no API key or wallet needed (beyond that: prepaid credits via header X-API-Key, see server instructions).
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | – | HTTP method the endpoint expects; default GET |
| url | string | yes | x402 endpoint you plan to pay |
| Name | Type | Req | Description |
|---|---|---|---|
| options | array | yes | – |
| reasons | array | yes | – |
| riskScore | integer|null | – | – |
| summary | string | – | – |
| verdict | string | yes | – |
| warnings | array | yes | – |
No examples provided.
x402_verify_settlement Verify a USDC settlement ~219
[FREE tier 20/day, then $0.005] Verify an on-chain USDC settlement: tx hash on network (base, base-sepolia, polygon, arbitrum, avalanche, bsc) paid amount to payTo. Returns verdict valid|invalid|pending|not_found. Free to try: 20 MCP calls/day per client, no API key or wallet needed (beyond that: prepaid credits via header X-API-Key, see server instructions).
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | decimal USDC, e.g. 0.01 |
| from | string | – | expected payer 0x address (optional) |
| match | string | – | exact (default) or atLeast |
| minConfirmations | integer | – | default 2 |
| network | string | – | base | base-sepolia | polygon | arbitrum | avalanche | bsc |
| payTo | string | yes | expected recipient 0x address |
| txHash | string | yes | 0x transaction hash (66 chars) |
| Name | Type | Req | Description |
|---|---|---|---|
| confirmations | integer | – | – |
| reasons | array | – | – |
| valid | boolean | – | – |
| verdict | string | yes | – |
No examples provided.
How do I install the MoneyTools payment-safety suite MCP server?
MoneyTools payment-safety suite is a hosted endpoint at https://mcp.moneytools.dev/mcp/payment-safety, 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 · mcp.moneytools.dev
claude mcp add --transport http dev-moneytools-payment-safety 'https://mcp.moneytools.dev/mcp/payment-safety'
What is the MoneyTools payment-safety suite MCP server?
MoneyTools payment-safety suite is an MCP server listed in the public MCP registry as dev.moneytools/payment-safety. Call before paying any x402 seller: 402/OFAC precheck, verify, approval, ledger. This page covers its hosted endpoint (https://mcp.moneytools.dev/mcp/payment-safety).
Is the MoneyTools payment-safety suite MCP server safe to use?
MoneyTools payment-safety suite scores 60 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 MoneyTools payment-safety suite MCP server expose?
MoneyTools payment-safety suite exposes 6 tools: x402_precheck, x402_verify_settlement, approval_request, approval_status, approval_verify, ledger_gateway. Their descriptions and schemas cost roughly 891 tokens of context every time the server is loaded.
Does the MoneyTools payment-safety suite MCP server require authentication?
No. We connected to MoneyTools payment-safety suite without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MoneyTools payment-safety suite MCP server still maintained?
MoneyTools payment-safety suite is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the MoneyTools payment-safety suite MCP server?
VerifyMCP ran 12 checks on MoneyTools payment-safety suite, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about MoneyTools payment-safety suite: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.