Paysafe

com.paysafe-agentPublished by paysafe-agent.comv1.1.1Updated Oct 24, 2026

Payment firewall for x402: scans for replay, overpayment, PII/secret leaks, prompt-injection.

VerifiedSTDIODesktop onlyFinance Security & Monitoring

Server details

Identifier: com.paysafe-agent/paysafe
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to paysafe-agent.com. It runs from a package rather than a hosted endpoint, so there is no endpoint to match against that domain.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/com.paysafe-agent%2Fpaysafe.svg)](https://sourceweft.com/mcp/com.paysafe-agent%2Fpaysafe?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local Paysafe MCP server that acts as a payment firewall for x402, scanning transactions for replay, overpayment, and PII, secret or prompt-injection leaks.

What you can do: Scan x402 payments for replay attempts and overpayment before they go through. Check payment data for leaked PII or secrets. Flag prompt-injection content in payment-related input. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it: Worth considering when an assistant handles x402 payments and you want a local check that flags replays, overpayment, data leaks and prompt injection before money moves.
Requirements: Runs as a local stdio process installed from the npm package paysafe-x402, so Node.js and npm are needed. Desktop only; no web executable. No authentication, environment variables or headers are declared.

Before you install

It inspects payment data, which may include personal or secret information, so review what it reads and where results go. It is a safeguard around payments, not a guarantee; confirm its findings before approving any transaction. The manifest lists no tools, so verify its actual behavior before relying on it.

Installation

In SourceWeft

Open Paysafe in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v1.1.1LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.