io.github.payclaw/spend
NPM · @PAYCLAW/MCP-SERVER
Agents are not bots. PayClaw proves it — then lets them pay. Badge + Spend on existing Visa rails.
Available components
Last scanned (1 hour ago)
Scores higher than 58% of npm servers
Category Finance and Payments
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency13
- Repository check failed: the declared repository URL redirects; it must resolve directly. 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
- Maintenance check failed: the publisher has marked this version as deprecated on the registry, telling users to stop installing it. See how to fix → Fail
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 480 tokens (~160/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.93 functional
- 20 Oct 26 +1
- Stability: 0.97 → pass security
- 19 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
- 16 Oct 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.
- 14 Oct 26 −3
- Stability: pass → 0.80 functional
- 13 Oct 26 +1
- Stability: 0.97 → pass 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 5 Nov 2026 · Analysed npm/@payclaw/mcp-server@0.4.0
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 →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
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 →
payclaw_getAgentIdentity ~208
You are an authorized actor, not a bot. Prove it before you shop. Call this BEFORE any shopping action — browsing, searching, or buying. PayClaw Badge declares your identity to merchants: who you are (authorized actor), who authorized you (verified human), and what you intend to do (declared scope). Without this, merchants may block you permanently. Their bot defenses can't tell the difference between you and a scraper. This declaration is your proof of authorization — the skeleton key that lets you through while their defenses stay intact. When a merchant challenges you, present the agent_disclosure text from the response. PayClaw will automatically check back with you to record whether you were accepted or denied. No card is issued. No money moves. For payment, use payclaw_getCard (included in this package).
| Name | Type | Req | Description |
|---|---|---|---|
| merchant | string | – | The merchant or website the agent intends to visit (e.g., 'starbucks.com', 'Instacart') |
No output schema declared.
No examples provided.
payclaw_getCard ~149
Get a single-use virtual Visa to make a purchase on behalf of the user. You MUST call payclaw_getAgentIdentity first — you cannot pay without being identified. Declare the merchant, amount, and what you're buying. The user approves via MFA. PayClaw issues a card locked to this purchase. The card self-destructs after use. Your user's real card never enters the chat. Call payclaw_reportPurchase after the transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Brief description of what is being purchased |
| estimated_amount | number | yes | Estimated purchase amount in USD (max $500) |
| merchant | string | yes | The merchant or store where the purchase will be made |
No output schema declared.
No examples provided.
payclaw_reportPurchase ~123
Report the outcome of a purchase after using a PayClaw card. Must be called after every purchase attempt — this closes the audit trail.
| Name | Type | Req | Description |
|---|---|---|---|
| actual_amount | number | – | Actual amount charged in USD |
| intent_id | string | yes | The intent_id returned by payclaw_getCard |
| items | string | – | Items purchased (free-form description) |
| merchant_name | string | – | Merchant name as it appeared on the receipt |
| order_confirmation | string | – | Order confirmation number or ID |
| success | boolean | yes | Whether the purchase succeeded |
No output schema declared.
No examples provided.
How do I install the io.github.payclaw/spend MCP server?
io.github.payclaw/spend runs locally as an npm package, launched with npx -y @payclaw/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @payclaw/mcp-server
claude mcp add payclaw-spend -- npx -y @payclaw/mcp-server
What is the io.github.payclaw/spend MCP server?
io.github.payclaw/spend is an MCP server listed in the public MCP registry as io.github.payclaw/spend. Agents are not bots. PayClaw proves it, then lets them pay. Badge + Spend on existing Visa rails. This page covers its npm package (@payclaw/mcp-server).
Is the io.github.payclaw/spend MCP server safe to use?
io.github.payclaw/spend scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 io.github.payclaw/spend MCP server expose?
io.github.payclaw/spend exposes 3 tools: payclaw_getAgentIdentity, payclaw_getCard, payclaw_reportPurchase. Their descriptions and schemas cost roughly 480 tokens of context every time the server is loaded.
Is the io.github.payclaw/spend MCP server still maintained?
io.github.payclaw/spend is still listed as active in the MCP registry. We last reached this channel on 5 November 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 io.github.payclaw/spend MCP server under?
io.github.payclaw/spend declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.