Is the MoneyTools payment-safety suite MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 5 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 MoneyTools payment-safety suite MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the MoneyTools payment-safety suite 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.

Does the MoneyTools payment-safety suite MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the MoneyTools payment-safety suite MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): x402_precheck and approval_request.

Has the MoneyTools payment-safety suite MCP server changed its tools?

Not since anlyon.dev started tracking it. Last scanned Nov 12, 2026.

MoneyTools payment-safety suite MCP server

dev.moneytools/payment-safetymoneytools.devstreamable-httpv2.11.11Scanned 2 days ago

Call before paying any x402 seller: 402/OFAC precheck, verify, approval, ledger

6 tools: 5 change things and 1 only read.

Reads private data · 0
Reads text others write · 4
Can send data out · 2
No findings

Tools listed without sign-in. Remote posture

With Anlyon

5 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.

Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. anlyon.dev only lists and labels, and these labels are the same either way.

What the MoneyTools payment-safety suite MCP server can do

The MoneyTools payment-safety suite MCP server is published by moneytools.dev, a domain the MCP Registry verified. It has 6 tools. It can create or change data (5 tools: x402_precheck, x402_verify_settlement, approval_request, approval_verify and 1 more), but cannot delete data. 1 tool only reads.

4 tools bring in text other people can write (x402_precheck, x402_verify_settlement, approval_request and 1 more); 2 tools can send data out of your system (x402_precheck and approval_request).

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.

Last scanned Nov 12, 2026, version 2.11.11.

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 5Creates or changes something that can be changed back.Claude Code: ask

approval_requestCreate a human approval request (Approval Relay).Reads text others writeCan send data outNo findings
Why it is in this group
- The name "approval_request" says "request": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.callback_url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it
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.
Annotations the server declares
- title: Request approval
- readOnlyHint: false
- openWorldHint: true
approval_verifyVerify a Relay receipt_jws (free).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
Verify a Relay receipt_jws (free). The legacy 'proof' argument is also accepted.
Annotations the server declares
- title: Verify approval
- readOnlyHint: true
ledger_gatewayTotals, by supplier, by day and exceptions for payments relayed by the MoneyTools Pay Gateway for this API key (free; needs X-API-Key).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
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]
Annotations the server declares
- title: Gateway ledger
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
x402_precheckBefore 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 li…Reads text others writeCan send data outNo 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.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it
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).
Annotations the server declares
- title: Pre-check an x402 payment
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
x402_verify_settlementVerify an on-chain USDC settlement: tx hash on network (base, base-sepolia, polygon, arbitrum, avalanche, bsc) paid amount to payTo.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
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).
Annotations the server declares
- title: Verify a USDC settlement
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true

Only reads 1Looks things up and changes nothing.Show 1 read-only tool

approval_statusCheck whether the human approved, denied or let the request expire (free).No findings
Why it is in this group
- The name "approval_status" says "status": a word for reading.
Description, as the server wrote it
Check whether the human approved, denied or let the request expire (free). Approved results include receipt_jws (also aliased as proof).
Annotations the server declares
- title: Approval status
- 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 private-data.

Reads private data0: Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4: Brings in text someone else can write: web pages, inbound email, messages, issues and comments.; approval_request
ledger_gateway
x402_precheck
x402_verify_settlement
Can send data out2: Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.; approval_request
x402_precheck

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.

Tools listed without sign-in

Looked at Nov 13, 2026, 11:19 UTC, unchanged since Nov 13, 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: 5
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 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
Matched text
https://mcp.moneytools.dev/mcp/payment-safety: tools/list returned 6 tools to an anonymous client, including x402_precheck (write), x402_verify_settlement (write), approval_request (write), approval_verify (write), ledger_gateway (write)
What this check looks for

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.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 2.11.11. Values in angle brackets are yours to fill in.

claude mcp add --transport http payment-safety https://mcp.moneytools.dev/mcp/payment-safety

claude mcp add --transport http payment-safety https://mcp.moneytools.dev/mcp/payment-safety

Run 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.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__payment-safety__approval_status"
    ],
    "ask": [
      "mcp__payment-safety__x402_precheck",
      "mcp__payment-safety__x402_verify_settlement",
      "mcp__payment-safety__approval_request",
      "mcp__payment-safety__approval_verify",
      "mcp__payment-safety__ledger_gateway"
    ],
    "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 payment-safety. Review it before you use it.

Capability tags behind 4 rules

mcp__payment-safety__x402_precheck untrusted-input, outbound
mcp__payment-safety__x402_verify_settlement untrusted-input
mcp__payment-safety__approval_request untrusted-input, outbound
mcp__payment-safety__ledger_gateway untrusted-input

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://anlyon.dev/api/v1/servers/dev.moneytools/payment-safety/verify?hash=3d92bffb3e143da5075d081943da93bbf87b765dfcb75d5885a029dada830383" | jq -e '.changed == false'

Pinned hash 3d92bffb3e14, from Nov 12, 2026, 13:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/dev.moneytools/payment-safety/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

[![anlyon.dev](https://anlyon.dev/badge/dev.moneytools/payment-safety.svg)](https://anlyon.dev/servers/dev.moneytools/payment-safety)

Source: MCP Registry. Synced Nov 12, 2026, 13:17 UTC.