io.github.Evozim/m2mcent

MCPcommunity
v1.0.3io.github.EvozimUnknownUpdated 29d agonpmGitHub

x402 payment wrapper for AI Agents and MCP Servers. USDC settlements on Base L2.

Ultra-lightweight x402 payment interceptor for AI Agents and MCP Servers. Monetize any API in 3 lines of code. M2MCent implements the x402 Payment Protocol — a machine-native payment standard inspired by HTTP 402: 1. Agent requests a protected endpoint 2. Server responds with + payment metadata (Base64 encoded) 3. Agent signs an EIP-712 typed data authorization (gasless for the payer) 4. Server…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
29d agoLast update
Package
Authorio.github.Evozim
LicenseUnknown
Version1.0.3
Sourcemcp-registry
npmm2mcent-sdk
GitHubEvozim/m2mcent-sdk
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/25
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/10
→ 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>" }
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
—npm provenance (Sigstore)+0/5
→ Publish from GitHub Actions with the --provenance flag
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies9 resolved · 1 with advisories
Tool surface—
Security scan✓ Cleanv1.0.2 · 20d ago
DEPws@8.17.1GHSA-58qx-3vcg-4xpx (transitive)
EvalsNone
IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Ultra-lightweight x402 payment interceptor for AI Agents and MCP Servers. Monetize any API in 3 lines of code. M2MCent implements the x402 Payment Protocol — a machine-native payment standard inspired by HTTP 402: 1. Agent requests a protected endpoint 2. Server responds with + payment metadata (Base64 encoded) 3. Agent signs an EIP-712 typed data authorization (gasless for the payer) 4. Server settles atomically on-chain via the M2MCent Escrow contract 5. Agent receives the premium response +…

Keywords
mcp