Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MoneyTools Settle

REMOTE · SETTLE.MONEYTOOLS.DEV

Call before signing an x402 payment: advisory budget check, 0.005 USDC/call

+3 this week 69 Trust /100

Last scanned (22 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 3705 tokens (~217/item across 17 items; 17 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 Management37
  • Stability observed for 11 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 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 18 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

Changelog

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 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.

  • 16 Nov 26 +1
    • Server version: 1.1.12 → 1.1.14 functional
  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “settle_report” rewrote its description, which is the text the model reads security
    • Tool “settle_subscribe_info” rewrote its description, which is the text the model reads security
    • Tool “settle_verify” rewrote its description, which is the text the model reads security
    • Tool “spend_cap_get” rewrote its description, which is the text the model reads security
    • Tool “spend_cap_set” rewrote its description, which is the text the model reads security
    • Tool “spend_check” rewrote its description, which is the text the model reads security
    • Tool “spend_log” rewrote its description, which is the text the model reads security
    • Tool “spend_record” rewrote its description, which is the text the model reads security
    • Server version: 1.1.9 → 1.1.12 functional
  • 11 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 10 Nov 26 64

    First indexed and scored.

Diagnostics

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://settle.moneytools.dev/mcp

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 7 Nov 2026 5 Feb 2027 ECDSA 256 ECDSA-SHA256 4e4d3708afd0dbf5133af623b7f08413
SANs: moneytools.dev, settle.moneytools.dev, *.settle.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 settle.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://settle.moneytools.dev/mcp Verified 200
http (plaintext) http://settle.moneytools.dev/mcp Served over HTTP 200
MCP tools · 17 exposed · ~3,610 tokens

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 →

Tool Tokens
receipt_create ~205

Create a delivery receipt (status paid) for an order/request ref; idempotent per ref. Needs a key mts_ (X-API-Key header or apiKey argument). No key? call settle_trial_key (free, 50 calls/7 days). Full plan 1 USDC/30d incl. 1,000 calls via x402.

NameTypeReqDescription
amountUsdstring–USD amount as decimal string, e.g. "0.25".
apiKeystring–Your MoneyTools Settle key mts_… (alternative to the X-API-Key header). No key: call settle_trial_key.
notestring–Free-text note (max 200 chars).
refstring–Your order / request id (idempotency key).
txstring–Settlement tx hash on Base, 0x + 64 hex.
webhookstring–Public https URL we POST to when the status resolves.

No output schema declared.

No examples provided.

receipt_get ~137

Read a delivery receipt and its history. Needs a key mts_ (X-API-Key header or apiKey argument). No key? call settle_trial_key (free, 50 calls/7 days). Full plan 1 USDC/30d incl. 1,000 calls via x402.

NameTypeReqDescription
apiKeystring–Your MoneyTools Settle key mts_… (alternative to the X-API-Key header). No key: call settle_trial_key.
receiptIdstring–Receipt id str_… (or use ref).
refstring–Your order / request id (idempotency key).

No output schema declared.

No examples provided.

receipt_update ~193

Move a receipt paid -> delivered | failed | refunded (refundTx optional). Needs a key mts_ (X-API-Key header or apiKey argument). No key? call settle_trial_key (free, 50 calls/7 days). Full plan 1 USDC/30d incl. 1,000 calls via x402.

NameTypeReqDescription
apiKeystring–Your MoneyTools Settle key mts_… (alternative to the X-API-Key header). No key: call settle_trial_key.
notestring–Free-text note (max 200 chars).
receiptIdstring–Receipt id str_… (or use ref).
refstring–Your order / request id (idempotency key).
refundTxstring–Refund tx hash on Base, 0x + 64 hex.
statusstring–New status (see tool description).

No output schema declared.

No examples provided.

settle_gate_claim ~232

Idempotency gate: claim an EIP-3009 authorization (payer+nonce) before settling. claimed:false means duplicate — do not settle again. Needs a key mts_ (X-API-Key header or apiKey argument). No key? call settle_trial_key (free, 50 calls/7 days). Full plan 1 USDC/30d incl. 1,000 calls via x402.

NameTypeReqDescription
apiKeystring–Your MoneyTools Settle key mts_… (alternative to the X-API-Key header). No key: call settle_trial_key.
assetstring–Token contract, default Base USDC.
networkstring–CAIP-2 network, default eip155:8453 (Base).
noncestring–EIP-3009 authorization nonce, 0x + 64 hex.
payerstring–Payer / agent wallet address 0x… (40 hex).
paymentPayloadstring–The x402 PAYMENT-SIGNATURE / X-PAYMENT payload (base64 JSON or object).

No output schema declared.

No examples provided.

settle_gate_complete ~156

Mark a claimed authorization settled or failed (failed allows a retry). Needs a key mts_ (X-API-Key header or apiKey argument). No key? call settle_trial_key (free, 50 calls/7 days). Full plan 1 USDC/30d incl. 1,000 calls via x402.

NameTypeReqDescription
apiKeystring–Your MoneyTools Settle key mts_… (alternative to the X-API-Key header). No key: call settle_trial_key.
gateIdstring–Gate id from settle_gate_claim.
statusstring–New status (see tool description).
txstring–Settlement tx hash on Base, 0x + 64 hex.

No output schema declared.

No examples provided.

settle_key_status ~109

Show remaining calls/expiry of your MoneyTools Settle key. Needs a key mts_ (X-API-Key header or apiKey argument). No key? call settle_trial_key (free, 50 calls/7 days). Full plan 1 USDC/30d incl. 1,000 calls via x402.

NameTypeReqDescription
apiKeystring–Your MoneyTools Settle key mts_… (alternative to the X-API-Key header). No key: call settle_trial_key.

No output schema declared.

No examples provided.

settle_report ~129

Paid, read-only, no arguments: x402 settlement health report for Base USDC — Base RPC head/latency, PayAI facilitator reachability, settlement-watch outcomes (24h); with a key also your receipts/open watches/caps/spend. $0.005 USDC per call via x402 over MCP (unpaid call returns PaymentRequired; retry with params._meta["x402/payment"]), or 1 call of your Settle key (apiKey).

NameTypeReqDescription
apiKeystring–Optional Settle key mts_… (pays with 1 call instead of x402).

No output schema declared.

No examples provided.

settle_subscribe_info ~77

Pricing: pay per call via x402 with no key (spend_check / spend_cap_get / spend_cap_set / spend_record / settle_verify / spend_log 0.005 USDC). Optional upgrade: 1 USDC / 30 days incl. 1,000 calls, or a free trial key. Read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

settle_trial_key ~69

Get a free MoneyTools Settle trial key right now (50 calls, 7 days, 1 per client per day; bucketed by IPv6 /64 or CF-Worker zone) with ready-to-run first calls. Pass the returned apiKey as the apiKey argument of any tool.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

settle_verify ~321

0.005 USDC per call via x402, no key (unpaid call returns PaymentRequired; retry with params._meta["x402/payment"]). Verify an x402 settlement on Base USDC right now (by tx hash, or payer+nonce / paymentPayload via USDC.authorizationState). Returns settled|failed|pending|not_settled|expired|unknown. Needs a key mts_ (X-API-Key header or apiKey argument). No key? call settle_trial_key (free, 50 calls/7 days). Full plan 1 USDC/30d incl. 1,000 calls via x402.

NameTypeReqDescription
amountstring–Expected amount in USDC atomic units (6 decimals), e.g. "10000" = 0.01 USDC.
apiKeystring–Your MoneyTools Settle key mts_… (alternative to the X-API-Key header). No key: call settle_trial_key.
noncestring–EIP-3009 authorization nonce, 0x + 64 hex.
payTostring–Seller receiving address 0x….
payerstring–Payer / agent wallet address 0x… (40 hex).
paymentPayloadstring–The x402 PAYMENT-SIGNATURE / X-PAYMENT payload (base64 JSON or object).
txstring–Settlement tx hash on Base, 0x + 64 hex.
validBeforenumber–Authorization validBefore (unix seconds).

No output schema declared.

No examples provided.

settle_watch ~296

Watch a timed-out/unknown x402 settlement: re-checked on-chain for up to 24h; POSTs your webhook when it becomes settled/failed/expired. Needs a key mts_ (X-API-Key header or apiKey argument). No key? call settle_trial_key (free, 50 calls/7 days). Full plan 1 USDC/30d incl. 1,000 calls via x402.

NameTypeReqDescription
amountstring–Expected amount in USDC atomic units (6 decimals), e.g. "10000" = 0.01 USDC.
apiKeystring–Your MoneyTools Settle key mts_… (alternative to the X-API-Key header). No key: call settle_trial_key.
noncestring–EIP-3009 authorization nonce, 0x + 64 hex.
payTostring–Seller receiving address 0x….
payerstring–Payer / agent wallet address 0x… (40 hex).
paymentPayloadstring–The x402 PAYMENT-SIGNATURE / X-PAYMENT payload (base64 JSON or object).
txstring–Settlement tx hash on Base, 0x + 64 hex.
validBeforenumber–Authorization validBefore (unix seconds).
webhookstring–Public https URL we POST to when the status resolves.

No output schema declared.

No examples provided.

settle_watch_status ~119

Status of a settlement watch. Needs a key mts_ (X-API-Key header or apiKey argument). No key? call settle_trial_key (free, 50 calls/7 days). Full plan 1 USDC/30d incl. 1,000 calls via x402.

NameTypeReqDescription
apiKeystring–Your MoneyTools Settle key mts_… (alternative to the X-API-Key header). No key: call settle_trial_key.
watchIdstring–Watch id stw_… from settle_watch.

No output schema declared.

No examples provided.

spend_cap_get ~196

0.005 USDC per call via x402, no key (unpaid call returns PaymentRequired; retry with params._meta["x402/payment"]). Advisory (complements your wallet's enforced hard limits): read the spend caps of a payer address plus what it spent in the last 24h (and in a session). Needs a key mts_ (X-API-Key header or apiKey argument). No key? call settle_trial_key (free, 50 calls/7 days). Full plan 1 USDC/30d incl. 1,000 calls via x402.

NameTypeReqDescription
apiKeystring–Your MoneyTools Settle key mts_… (alternative to the X-API-Key header). No key: call settle_trial_key.
payerstring–Payer / agent wallet address 0x… (40 hex).
sessionIdstring–Your session / run id.

No output schema declared.

No examples provided.

spend_cap_set ~359

0.005 USDC per call via x402, no key (unpaid call returns PaymentRequired; retry with params._meta["x402/payment"]). Advisory spend caps that complement your wallet's enforced hard limits (Coinbase Agentic Wallet / CDP spendControls); cannot block payments. Set per-call / per-day (rolling 24h) / per-session USD limits and optional allow-lists (payTo, hosts, networks) for a payer wallet address (replaces the previous policy for that payer). Optional ownerLock secret so the agent cannot loosen the caps later. Advisory and non-custodial. Needs a key mts_ (X-API-Key header or apiKey argument). No key? call settle_trial_key (free, 50 calls/7 days). Full plan 1 USDC/30d incl. 1,000 calls via x402.

NameTypeReqDescription
allowHostsarray–Allowed seller hostnames.
allowNetworksarray–Allowed CAIP-2 networks.
allowPayToarray–Allowed seller payTo addresses.
apiKeystring–Your MoneyTools Settle key mts_… (alternative to the X-API-Key header). No key: call settle_trial_key.
ownerLockstring–Owner secret (>=12 chars); once set, caps can only be loosened with it.
payerstring–Payer / agent wallet address 0x… (40 hex).
perCallUsdstring–Max USD per single payment, e.g. "0.10".
perDayUsdstring–Max USD per rolling 24h.
perSessionUsdstring–Max USD per sessionId.

No output schema declared.

No examples provided.

spend_check ~365

0.005 USDC per call via x402, no key (unpaid call returns PaymentRequired; retry with params._meta["x402/payment"]). Advisory pre-sign check (your wallet's own hard limits still apply; we cannot block a payment): 'would this payment exceed my cap?'. Pass the 402 PAYMENT-REQUIRED (header or body) or amountUsd, plus payer and optional sessionId/host. Returns allow|deny with reasons and remaining budget; reserve:true also logs it as pending. Needs a key mts_ (X-API-Key header or apiKey argument). No key? call settle_trial_key (free, 50 calls/7 days). Full plan 1 USDC/30d incl. 1,000 calls via x402.

NameTypeReqDescription
amountUsdstring–USD amount as decimal string, e.g. "0.25".
apiKeystring–Your MoneyTools Settle key mts_… (alternative to the X-API-Key header). No key: call settle_trial_key.
hoststring–Seller hostname, e.g. api.example.com.
networkstring–CAIP-2 network, default eip155:8453 (Base).
payTostring–Seller receiving address 0x….
payerstring–Payer / agent wallet address 0x… (40 hex).
paymentRequiredstring–The 402 PAYMENT-REQUIRED header (base64) or the 402 JSON body.
refstring–Your order / request id (idempotency key).
reserveboolean–true = log this payment as pending if allowed.
sessionIdstring–Your session / run id.

No output schema declared.

No examples provided.

spend_log ~240

0.005 USDC per call via x402, no key (unpaid call returns PaymentRequired; retry with params._meta["x402/payment"]). Spend log / receipts for a payer address: totals (settled, pending, refunded), top sellers and the latest receipts over the last N days (1-31; read from Settle's own receipt records, not from Base RPC history). Needs a key mts_ (X-API-Key header or apiKey argument). No key? call settle_trial_key (free, 50 calls/7 days). Full plan 1 USDC/30d incl. 1,000 calls via x402.

NameTypeReqDescription
apiKeystring–Your MoneyTools Settle key mts_… (alternative to the X-API-Key header). No key: call settle_trial_key.
daysnumber–Look-back window in days (1-31, Settle receipt records).
limitnumber–Max receipts returned.
payerstring–Payer / agent wallet address 0x… (40 hex).
sessionIdstring–Your session / run id.

No output schema declared.

No examples provided.

spend_record ~407

0.005 USDC per call via x402, no key (unpaid call returns PaymentRequired; retry with params._meta["x402/payment"]). Record an x402 payment the agent made (or update a reserved one by spendId/ref): status settled|failed|pending|refunded, tx; verify:true checks a Base tx on-chain (read-only). Builds the spend log / receipts. Needs a key mts_ (X-API-Key header or apiKey argument). No key? call settle_trial_key (free, 50 calls/7 days). Full plan 1 USDC/30d incl. 1,000 calls via x402.

NameTypeReqDescription
amountUsdstring–USD amount as decimal string, e.g. "0.25".
apiKeystring–Your MoneyTools Settle key mts_… (alternative to the X-API-Key header). No key: call settle_trial_key.
hoststring–Seller hostname, e.g. api.example.com.
networkstring–CAIP-2 network, default eip155:8453 (Base).
notestring–Free-text note (max 200 chars).
payTostring–Seller receiving address 0x….
payerstring–Payer / agent wallet address 0x… (40 hex).
paymentRequiredstring–The 402 PAYMENT-REQUIRED header (base64) or the 402 JSON body.
refstring–Your order / request id (idempotency key).
sessionIdstring–Your session / run id.
spendIdstring–Spend id sp_… from spend_check reserve.
statusstring–New status (see tool description).
txstring–Settlement tx hash on Base, 0x + 64 hex.
verifyboolean–true = verify tx on Base (read-only).

No output schema declared.

No examples provided.

Install

How do I install the MoneyTools Settle MCP server?

MoneyTools Settle is a hosted endpoint at https://settle.moneytools.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 · settle.moneytools.dev

# add to Claude Code
claude mcp add --transport http dev-moneytools-settle 'https://settle.moneytools.dev/mcp'
Common questions

What is the MoneyTools Settle MCP server?

MoneyTools Settle is an MCP server listed in the public MCP registry as dev.moneytools/settle. Call before signing an x402 payment: advisory budget check, 0.005 USDC/call. This page covers its hosted endpoint (https://settle.moneytools.dev/mcp).

Is the MoneyTools Settle MCP server safe to use?

MoneyTools Settle scores 69 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 Settle MCP server expose?

MoneyTools Settle exposes 17 tools: settle_report, settle_verify, settle_watch, settle_watch_status, settle_gate_claim, and 12 more. Their descriptions and schemas cost roughly 3,610 tokens of context every time the server is loaded.

Does the MoneyTools Settle MCP server require authentication?

No. We connected to MoneyTools Settle without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the MoneyTools Settle MCP server still maintained?

MoneyTools Settle 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 Settle MCP server?

VerifyMCP ran 13 checks on MoneyTools Settle, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.