io.github.payclaw/spend
NPM · @PAYCLAW/MCP-SERVER · SCANNED AUG 3
Agents are not bots. PayClaw proves it — then lets them pay. Badge + Spend on existing Visa rails.
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 →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
- 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
- Actively maintained (last published 148 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability32
- AI-judged instruction clarity (poor).Fail
- 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @payclaw/mcp-server
claude mcp add payclaw-spend -- npx -y @payclaw/mcp-server
codex mcp add payclaw-spend -- npx -y @payclaw/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"payclaw-spend": {
"type": "local",
"command": [
"npx",
"-y",
"@payclaw/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add payclaw-spend --command npx --arg -y --arg @payclaw/mcp-server
mcp_servers:
payclaw-spend:
command: "npx"
args: ["-y", "@payclaw/mcp-server"] {
"mcpServers": {
"payclaw-spend": {
"command": "npx",
"args": [
"-y",
"@payclaw/mcp-server"
]
}
}
} 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.
- 3 Aug 26 +3
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +36
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Security disclosure: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → poor ▲ functional
- First check of Schema quality: unverified functional
- Licence: MIT functional
- 31 Jul 26 −6
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 39
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@payclaw/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.