# paysafe-x402

PaySafe — a payment security firewall for x402 micropayment traffic. Advisory scanning: PII/secret leaks, replay, overpayment, prompt-injection-triggered payments, counterparty reputation. Non-custodial. Includes an MCP server: npx paysafe-x402

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 1.1.2
- **Author:** Unknown
- **License:** MIT
- **npm:** paysafe-x402
- **Source:** https://github.com/corbinallison/paysafe
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 13 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-15T08:44:04.901Z
- **Version scanned:** 1.4.2
- **CVEs:** none found by OSV at scan time

## Tools

12 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `scan_outgoing_payment`
- `scan_incoming_payment`
- `check_counterparty_reputation`
- `report_payment_outcome`
- `report_counterparty`
- `dispute_reputation`
- `mint_api_key`
- `rotate_api_key`
- `check_approval_status`
- `get_plans`
- `subscribe_plan`
- `verify_verdict_attestation`

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"paysafe-x402\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"paysafe-x402\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on your machine; read-only tool surface.
- Floor 13, ceiling 31 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/paysafe-x402
- Install plan: https://forgeregistry.com/api/v1/packages/paysafe-x402/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/paysafe-x402
- HTML page: https://forgeregistry.com/registry/paysafe-x402
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.