Paysafe MCP server

Read from the package source without running it. The installed server may list more.

• check_counterparty_reputation

  Look up shared post-hoc reports on a counterparty wallet address (scam, non-delivery, prompt injection, overcharge, impersonation, replay abuse), aggregated across reporting agents.

• get_plans

  Machine-readable PaySafe plan catalog: tiers (Starter/Pro/Scale) with per-scan pricing, velocity and spend limits, hard ceilings, and how to subscribe. Free.

• mint_api_key

  Issue a free PaySafe API key (first 100 calls free). Returns the key ONCE — store it and set it as PAYSAFE_API_KEY (or pass to other tools) for future sessions. Rate-limited per IP.

• report_counterparty

  File a report against a counterparty after a bad payment experience (always free). Categories: scam, non_delivery, prompt_injection, overcharge, impersonation, replay_abuse, other.

• scan_incoming_payment

  Screen an x402 payment request / 402 offer your agent RECEIVED. Checks: resource URL risk (IP literals, punycode, shorteners, userinfo tricks), credential demands, price sanity, replay, counterparty reputation. Returns allow/flag/block with reasons.

• scan_outgoing_payment

  Screen an x402 payment your agent is ABOUT TO MAKE. Checks: PII/secret leakage in payment metadata, nonce replay, overpayment vs expected price, prompt-injection-triggered payment provenance, counterparty reputation. Returns allow/flag/block with reasons. Advisory only — PaySafe never touches keys or funds.

• subscribe_plan

  Subscribe/renew the current API key on a PaySafe plan (pro: $4.99/30d at $0.005/scan; scale: $19.99/30d at $0.002/scan). This endpoint is itself x402-paid at the plan's price: without an x402-paying transport the response is the 402 payment challenge to settle. Renewal extends from the current expiry.

• verify_verdict_attestation

  LOCALLY verify a PaySafe scan's Ed25519 attestation before trusting an allow-verdict: checks the signature against the pinned server key (fetched from /.well-known/paysafe-verdict-key unless trusted_key_hex is supplied), recomputes the payment commitment from the payment YOU are about to settle (rejects attestations issued for a different payment — replay defense), and enforces expiry. Runs no net

• Code scan28 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 3 days ago15/15
• Maintainer identitynamespace and repository owner differ; GitHub account older than a year6/10

Safety score

89/100

higher than 90% of 1,761 Finance servers

Tools

8

the typical Finance server has 8

Tools that change things

0%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

2

more than 80% of 946 Finance servers

Downloads a week

27

more than 15% of 421 Finance servers with a package

Paysafe: common questions

Is Paysafe MCP server safe?

Yes, by our scan: it is graded A (89/100). Read the Paysafe safety report

How do I install Paysafe?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Paysafe need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Paysafe maintained?

The last commit was 43 days ago (2026-09-22). The latest release is v1.1.1.

What can I use instead of Paysafe?

Servers from other publishers that do the same job: Pulsefeed X402 MCP server, three.ws Agent Payments MCP server and X402 List MCP server.

How does Paysafe compare with other Finance MCP servers?

safety score 89/100 (higher than 90% of 1,761 Finance servers); tools 8 (the typical Finance server has 8); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.