# MoneyTools payment-safety suite (remote · mcp.moneytools.dev)

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

- Trust score: 60/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.moneytools.dev`: 60/100 (this document), [markdown](https://verifymcp.io/servers/dev-moneytools-payment-safety/mcp-payment-safety.md), [page](https://verifymcp.io/servers/dev-moneytools-payment-safety/mcp-payment-safety)

## Channel facts

- Endpoint: `https://mcp.moneytools.dev/mcp/payment-safety`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.11.11`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 78% of tool parameters carry a description.
  - Structured output schemas are declared (33% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

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

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "dev-moneytools-payment-safety": {
      "url": "https://mcp.moneytools.dev/mcp/payment-safety"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-moneytools-payment-safety": {
      "type": "http",
      "url": "https://mcp.moneytools.dev/mcp/payment-safety"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-moneytools-payment-safety]
url = "https://mcp.moneytools.dev/mcp/payment-safety"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-moneytools-payment-safety": {
      "type": "remote",
      "url": "https://mcp.moneytools.dev/mcp/payment-safety",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-moneytools-payment-safety --url 'https://mcp.moneytools.dev/mcp/payment-safety' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-moneytools-payment-safety:
    url: "https://mcp.moneytools.dev/mcp/payment-safety"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-moneytools-payment-safety": {
      "Transport": "http",
      "Url": "https://mcp.moneytools.dev/mcp/payment-safety"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-moneytools-payment-safety -t streamable-http -u 'https://mcp.moneytools.dev/mcp/payment-safety'
```

### Other

```json
{
  "mcpServers": {
    "dev-moneytools-payment-safety": {
      "type": "http",
      "url": "https://mcp.moneytools.dev/mcp/payment-safety"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 60, 0)

- [security] 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
- [functional] Server version: 2.11.19 → 2.11.20

### 2026-11-20 (score 60, +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.

### 2026-11-19 (score 59, 0)

- [functional] Server version: 2.11.18 → 2.11.19

### 2026-11-18 (score 59, 0)

- [functional] Server version: 2.11.16 → 2.11.18

### 2026-11-17 (score 59, +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.

### 2026-11-16 (score 58, 0)

- [functional] Server version: 2.11.13 → 2.11.16

### 2026-11-15 (score 58, +1)

- [functional] Server version: 2.11.11 → 2.11.13

### 2026-11-13 (score 57, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (6)

### `x402_precheck` (~143 tokens)

Pre-check an x402 payment

[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).

Input parameters:

- `method` (string): HTTP method the endpoint expects; default GET
- `url` (string, required): x402 endpoint you plan to pay

Output parameters:

- `options` (array)
- `reasons` (array)
- `riskScore` (integer|null)
- `summary` (string)
- `verdict` (string)
- `warnings` (array)

### `x402_verify_settlement` (~219 tokens)

Verify a USDC settlement

[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).

Input parameters:

- `amount` (string, required): 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, required): expected recipient 0x address
- `txHash` (string, required): 0x transaction hash (66 chars)

Output parameters:

- `confirmations` (integer)
- `reasons` (array)
- `valid` (boolean)
- `verdict` (string)

### `approval_request` (~295 tokens)

Ask your human to approve a payment

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.

Input parameters:

- `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)

### `approval_status` (~115 tokens)

Approval status

Check whether the human approved, denied or let the request expire (free). Approved results include receipt_jws (also aliased as proof).

Input parameters:

- `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)

### `approval_verify` (~43 tokens)

Verify an approval proof

Verify a Relay receipt_jws (free). The legacy 'proof' argument is also accepted.

Input parameters:

- `proof` (string)
- `receipt_jws` (string)

### `ledger_gateway` (~76 tokens)

Spend ledger (Pay Gateway receipts)

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]

Input parameters:

- `currency` (string)
- `days` (number)
- `month` (string): YYYY-MM

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-moneytools-payment-safety/mcp-payment-safety#diagnostics

## Score history

- 2026-11-21: 60
- 2026-11-20: 60
- 2026-11-19: 59
- 2026-11-18: 59
- 2026-11-17: 59
- 2026-11-16: 58
- 2026-11-15: 58
- 2026-11-14: 57
- 2026-11-13: 57
- 2026-11-12: 56

## Common questions

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

## Links

- Remote endpoint: https://mcp.moneytools.dev/mcp/payment-safety
- Website: https://moneytools.dev/products/payment-safety/
- Changelog RSS feed: https://verifymcp.io/servers/dev-moneytools-payment-safety/mcp-payment-safety.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-moneytools-payment-safety/mcp-payment-safety/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-moneytools-payment-safety/mcp-payment-safety.json
- HTML version of this page: https://verifymcp.io/servers/dev-moneytools-payment-safety/mcp-payment-safety
