com.paysafe-agent/paysafe
NPM · PAYSAFE-X402 · SCANNED SEP 25
Payment firewall for x402: scans for replay, overpayment, PII/secret leaks, prompt-injection.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security88
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects uuid 8.3.2, reached via @coinbase/x402 > x402 > wagmi > @wagmi/connectors > @metamask/sdk > uuid. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 400 of 542 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 65 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 743 tokens (~92/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 19% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
How do I install the com.paysafe-agent/paysafe MCP server?
com.paysafe-agent/paysafe runs locally as an npm package, launched with npx -y paysafe-x402. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · paysafe-x402
claude mcp add com-paysafe-agent-paysafe -- npx -y paysafe-x402
{
"mcpServers": {
"com-paysafe-agent-paysafe": {
"command": "npx",
"args": [
"-y",
"paysafe-x402"
]
}
}
} {
"servers": {
"com-paysafe-agent-paysafe": {
"command": "npx",
"args": [
"-y",
"paysafe-x402"
]
}
}
} codex mcp add com-paysafe-agent-paysafe -- npx -y paysafe-x402
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-paysafe-agent-paysafe": {
"type": "local",
"command": [
"npx",
"-y",
"paysafe-x402"
],
"enabled": true
}
}
} openclaw mcp add com-paysafe-agent-paysafe --command npx --arg -y --arg paysafe-x402
mcp_servers:
com-paysafe-agent-paysafe:
command: "npx"
args: ["-y", "paysafe-x402"] {
"McpServers": {
"com-paysafe-agent-paysafe": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"paysafe-x402"
]
}
}
} assistant mcp add com-paysafe-agent-paysafe -t stdio -c npx -a -y paysafe-x402
{
"mcpServers": {
"com-paysafe-agent-paysafe": {
"command": "npx",
"args": [
"-y",
"paysafe-x402"
]
}
}
} 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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 −2
- Stability: pass → 0.83 functional
- 19 Sept 26 0
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
- CVE-2026-67316 no longer affects this package ▲ security
- CVE-2026-67313 no longer affects this package ▲ security
- CVE-2026-67312 no longer affects this package ▲ security
- CVE-2026-67321 no longer affects this package ▲ security
- CVE-2026-67315 no longer affects this package ▲ security
- CVE-2026-67320 no longer affects this package ▲ security
- CVE-2026-67317 no longer affects this package ▲ security
- CVE-2026-67318 no longer affects this package ▲ security
- CVE-2026-67319 no longer affects this package ▲ security
- CVE-2026-67314 no longer affects this package ▲ security
- 14 Sept 26 0
- CVE-2026-82417 no longer affects this package ▲ security
- CVE-2026-82562 no longer affects this package ▲ security
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 25 Sept 2026 · Analysed npm/paysafe-x402@1.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 400 packages
| Packages resolved | 400 |
|---|---|
| Deprecated | 13 |
| Stale | 107 |
| No linked repository | 2 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
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 →
check_counterparty_reputation ~61
Look up shared post-hoc reports on a counterparty wallet address (scam, non-delivery, prompt injection, overcharge, impersonation, replay abuse), aggregated across reporting agents.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address to look up |
No output schema declared.
No examples provided.
get_plans ~45
Machine-readable PaySafe plan catalog: tiers (Starter/Pro/Scale) with per-scan pricing, velocity and spend limits, hard ceilings, and how to subscribe. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mint_api_key ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Stable identifier for your agent — scopes velocity limits |
No output schema declared.
No examples provided.
report_counterparty ~86
File a report against a counterparty after a bad payment experience (always free). Categories: scam, non_delivery, prompt_injection, overcharge, impersonation, replay_abuse, other.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| category | string | yes | – |
| evidence_url | string | – | – |
| reason | string | yes | – |
| reporter_agent_id | string | yes | – |
No output schema declared.
No examples provided.
scan_incoming_payment ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| context | object | – | – |
| expected_price_usd | number | – | – |
| payment | object | yes | – |
| policy | object | – | – |
No output schema declared.
No examples provided.
scan_outgoing_payment ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | – |
| context | object | – | – |
| expected_price_usd | number | – | – |
| payment | object | yes | – |
| policy | object | – | – |
No output schema declared.
No examples provided.
subscribe_plan ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| plan | string | yes | – |
No output schema declared.
No examples provided.
verify_verdict_attestation ~163
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 network calls except the one-time key fetch; the verdict itself is never sent anywhere.
| Name | Type | Req | Description |
|---|---|---|---|
| payment | object | yes | The payment you are about to settle — commitment is recomputed from this |
| scan | object | yes | – |
| trusted_key_hex | string | – | Pin the server verdict key (SPKI DER hex); fetched once when omitted |
No output schema declared.
No examples provided.
What is the com.paysafe-agent/paysafe MCP server?
com.paysafe-agent/paysafe is an MCP server listed in the public MCP registry as com.paysafe-agent/paysafe. Payment firewall for x402: scans for replay, overpayment, PII/secret leaks, prompt-injection. This page covers its npm package (paysafe-x402).
Is the com.paysafe-agent/paysafe MCP server safe to use?
com.paysafe-agent/paysafe scores 73 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 25 September 2026. It declares no install or post-install scripts. 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 com.paysafe-agent/paysafe MCP server expose?
com.paysafe-agent/paysafe exposes 8 tools: scan_outgoing_payment, scan_incoming_payment, check_counterparty_reputation, report_counterparty, mint_api_key, and 3 more. Their descriptions and schemas cost roughly 743 tokens of context every time the server is loaded.
Is the com.paysafe-agent/paysafe MCP server still maintained?
com.paysafe-agent/paysafe is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.paysafe-agent/paysafe MCP server under?
com.paysafe-agent/paysafe declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.