io.github.payclaw/payclaw
NPM · @PAYCLAW/MCP-SERVER · SCANNED SEP 20
Virtual Visa cards for AI agents. JIT card issuance, human-approved, MCP-native.
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 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
- 31 of 95 dependencies flagged as unhealthy. 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 196 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 358 tokens (~119/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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
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
How do I install the io.github.payclaw/payclaw MCP server?
io.github.payclaw/payclaw 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-payclaw -- npx -y @payclaw/mcp-server
{
"mcpServers": {
"payclaw-payclaw": {
"command": "npx",
"args": [
"-y",
"@payclaw/mcp-server"
]
}
}
} {
"servers": {
"payclaw-payclaw": {
"command": "npx",
"args": [
"-y",
"@payclaw/mcp-server"
]
}
}
} codex mcp add payclaw-payclaw -- npx -y @payclaw/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"payclaw-payclaw": {
"type": "local",
"command": [
"npx",
"-y",
"@payclaw/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add payclaw-payclaw --command npx --arg -y --arg @payclaw/mcp-server
mcp_servers:
payclaw-payclaw:
command: "npx"
args: ["-y", "@payclaw/mcp-server"] {
"McpServers": {
"payclaw-payclaw": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@payclaw/mcp-server"
]
}
}
} assistant mcp add payclaw-payclaw -t stdio -c npx -a -y @payclaw/mcp-server
{
"mcpServers": {
"payclaw-payclaw": {
"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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 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.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 9 Sept 26 −3
- Security disclosure: fail → unverified ▼ functional
- Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed npm/@payclaw/mcp-server@0.1.4
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 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 ~141
Get a PayClaw identity token before any shopping action. Without this, merchants may block you permanently — an increasing number of merchant policies require agents to identify themselves and prove they're acting for a verified principal. Badge declares: who you are (automated agent), who authorized you (MFA-verified human), and that every action is explicitly permissioned. This is your license plate. Don't shop without it. Call this BEFORE browsing, searching, or buying. The token is your proof of compliance for the entire shopping session. No card is issued. No money moves. For payment, use payclaw_getCard (included in this package).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
payclaw_getCard ~94
Get a PayClaw virtual card to make a purchase on behalf of the user. Returns card details and an intent_id. 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 from payclaw_getCard. Must be called after every purchase attempt.
| 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.
What is the io.github.payclaw/payclaw MCP server?
io.github.payclaw/payclaw is an MCP server listed in the public MCP registry as io.github.payclaw/payclaw. Virtual Visa cards for AI agents. JIT card issuance, human-approved, MCP-native. This page covers its npm package (@payclaw/mcp-server).
Is the io.github.payclaw/payclaw MCP server safe to use?
io.github.payclaw/payclaw scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 io.github.payclaw/payclaw MCP server expose?
io.github.payclaw/payclaw exposes 3 tools: payclaw_getAgentIdentity, payclaw_getCard, payclaw_reportPurchase. Their descriptions and schemas cost roughly 358 tokens of context every time the server is loaded.
Is the io.github.payclaw/payclaw MCP server still maintained?
io.github.payclaw/payclaw is still listed as active in the MCP registry. We last reached this channel on 20 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 io.github.payclaw/payclaw MCP server under?
io.github.payclaw/payclaw declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.