z-zero-mcp-server

MCPcommunity
v1.10.1io.github.Dempty-glitchMITUpdated 20d agonpmGitHub

Payments for AI agents: gasless USDC on Base + JIT single-use virtual cards, PAN never in context.

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 →
20d agoLast update
Needs 1 credential before it runs
  • Z_ZERO_API_KEYAPI keyrequired

    Passport Key (zk_live_...) from z-zero.xyz/dashboard/agents

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
Authorio.github.Dempty-glitch
LicenseMIT
Version1.10.1
Sourcenpm+mcp-registry
npmz-zero-mcp-server
GitHubDempty-glitch/Z-Zero-mcp
SBOMCycloneDX 1.6 ↓
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✓ 0 resolved · none vulnerable
Tool surface12 tools · 1 privileged
Security scan✓ Cleanv1.3.5 · 1mo agoHow well does this scan work?
EvalsNone
IndexedJul 20, 2026

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

Tools

12 tools · 1 privileged
Statically extracted from the published packagev1.3.5 · 1mo 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.

list_cardsNo description published

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

check_balanceNo description published

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

get_deposit_addressesNo description published

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

request_payment_tokenNo description published

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

get_merchant_hintsNo description published

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

execute_paymentprivilegedNo description published

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

cancel_payment_tokenNo description published

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

request_human_approvalNo description published

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

set_api_keyNo description published

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

show_api_key_statusNo description published

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

auto_pay_checkoutNo description published

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

report_checkout_failNo description published

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

0 of 12 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

Payments for AI agents: gasless USDC on Base + JIT single-use virtual cards, PAN never in context.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

12 tools · 1 privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.