@payclaw/mcp-server

MCPcommunity
v0.8.2PayClawMITUpdated 6mo agonpmGitHub

Badge identity + virtual Visa cards for AI agents. Declare, pay, audit — on existing Visa rails. MCP-native.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
57Downloads/wk
6mo agoLast update
Needs 1 credential before it runs
  • PAYCLAW_API_KEYAPI keyrequired

    Your PayClaw API key (get one at payclaw.io)

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorPayClaw
LicenseMIT
Version0.8.2
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/20
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/5
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
npm Trusted Publishing (Sigstore)+0/5
Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
npm maintainer match+0/5
Earned once your identity is verified above and that login is an npm maintainer of this package
CVE scan · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface6 tools · none privileged
Security scan✓ Cleanv0.8.2 · 3d agoHow well does this scan work?
EvalsNone
IndexedAug 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

6 tools · none privileged
Statically extracted from the published packagev0.8.2 · 3d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

payclaw_getAgentIdentityNo description published

This tool published no description. Forge does not invent one.

payclaw_reportBadgePresentedReport that you presented your PayClaw Badge to a merchant. Call this immediately after merging the checkoutPatch into a checkout payload. Required for PayClaw to record the trip. When Extended Auth is enabled, PayClaw checks back 7 seconds later. Otherwise, call payclaw_reportBadgeOutcome when yo…

Report that you presented your PayClaw Badge to a merchant. Call this immediately after merging the checkoutPatch into a checkout payload. Required for PayClaw to record the trip. When Extended Auth is enabled, PayClaw checks back 7 seconds later. Otherwise, call payclaw_reportBadgeOutcome when yo…

No input schema was published for this tool.

payclaw_reportBadgeOutcomeReport how the merchant responded when you presented your PayClaw Badge. Call this after payclaw_reportBadgePresented when you know whether the merchant accepted or denied you. Use when Extended Auth is disabled, or to report earlier than the 7-second check.

Report how the merchant responded when you presented your PayClaw Badge. Call this after payclaw_reportBadgePresented when you know whether the merchant accepted or denied you. Use when Extended Auth is disabled, or to report earlier than the 7-second check.

No input schema was published for this tool.

payclaw_reportBadgeNotPresentedReport that you did NOT present your PayClaw Badge at a merchant. Call this when you have a badge but chose not to present it (e.g., abandoned cart, merchant didn't ask).

Report that you did NOT present your PayClaw Badge at a merchant. Call this when you have a badge but chose not to present it (e.g., abandoned cart, merchant didn't ask).

No input schema was published for this tool.

payclaw_getCardGet 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 s…

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 s…

No input schema was published for this tool.

payclaw_reportPurchaseReport the outcome of a purchase after using a PayClaw card. Must be called after every purchase attempt — this closes the audit trail.

Report the outcome of a purchase after using a PayClaw card. Must be called after every purchase attempt — this closes the audit trail.

No input schema was published for this tool.

5 of 6 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Badge identity + virtual Visa cards for AI agents. Declare, pay, audit — on existing Visa rails. MCP-native.

Keywords
mcppaymentsvirtual-cardsai-agentsfintechsandboxvisacommerce
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-08-30 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in payments & commerce