Spawnpay MCP Server
spawnpay-mcp
npm
v0.7.1
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
MCP server giving AI agents crypto wallets, payments, and referral earnings on Base L2
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 5 = 95. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 2
medium Untrusted input can drive an external actionMTC-FLOW-005
Untrusted-input tools ([spawnpay_webhook_events]) co-exist with external-action tools ([spawnpay_webhook_register, spawnpay_webhook_delete, spawnpay_webhook_toggle, spawnpay_webhook_events]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [spawnpay_webhook_events] → sinks [spawnpay_webhook_register, spawnpay_webhook_delete, spawnpay_webhook_toggle, spawnpay_webhook_events]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow spawnpay_webhook_events → spawnpay_webhook_register
medium Unconstrained URL/host parameter "url" on "spawnpay_webhook_register"MTC-CAP-007
Tool "spawnpay_webhook_register" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).
Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.
Location: tool spawnpay_webhook_register · inputSchema.properties.url
Tools 34
Each tool and what it can reach — statically extracted from the published source.
spawnpay_webhook_eventsingests untrusted inputnetwork egressspawnpay_webhook_deletenetwork egressspawnpay_webhook_registernetwork egressspawnpay_webhook_togglenetwork egressspawnpay_balanceno sensitive capabilityspawnpay_batch_sendno sensitive capabilityspawnpay_budget_setno sensitive capabilityspawnpay_budget_statusno sensitive capabilityspawnpay_demo_sendno sensitive capabilityspawnpay_depositsno sensitive capability
Show 24 more tools ↓
spawnpay_escrow_disputeno sensitive capabilityspawnpay_escrow_listno sensitive capabilityspawnpay_escrow_openno sensitive capabilityspawnpay_escrow_refundno sensitive capabilityspawnpay_escrow_releaseno sensitive capabilityspawnpay_invoice_cancelno sensitive capabilityspawnpay_invoice_createno sensitive capabilityspawnpay_invoice_getno sensitive capabilityspawnpay_invoice_listno sensitive capabilityspawnpay_invoice_payno sensitive capabilityspawnpay_key_rotateno sensitive capabilityspawnpay_leaderboardno sensitive capabilityspawnpay_lookupno sensitive capabilityspawnpay_receiveno sensitive capabilityspawnpay_referral_statsno sensitive capabilityspawnpay_reputationno sensitive capabilityspawnpay_sendno sensitive capabilityspawnpay_signupno sensitive capabilityspawnpay_statsno sensitive capabilityspawnpay_stream_closeno sensitive capabilityspawnpay_stream_listno sensitive capabilityspawnpay_stream_openno sensitive capabilityspawnpay_stream_tickno sensitive capabilityspawnpay_webhook_listno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (34 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.7.1 latest |
A 95/100 | 2 | 1.13.0 | 2026-09-07 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan spawnpay-mcp --onlineMore in API Development
Adapters for the FrontMCP framework
Transcend MCP Server — Admin tools.
Transcend MCP Server — Assessments tools.
MCP Server for Bling
MCP Server for Blogger API
Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.