io.github.zekebuilds-lab/captcha-mcp

MCPcommunity
v0.1.1io.github.zekebuilds-labUnknownUpdated 1mo agonpmGitHub

Charge AI agents per-call without accounts. PoW solve = free tier, Lightning = paid tier.

Your MCP server returns 429 when agents pound it. captcha-mcp makes them earn their next call instead. Hand the agent a proof-of-work puzzle (free, ~5s of CPU) or a 3-sat Lightning invoice — both are machine-readable backoff signals an autonomous caller can satisfy without an account, email, or API key. Three tools over stdio or HTTP. Stdlib only. No signup, free fallback, self-hosted, no revenue…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Package
Authorio.github.zekebuilds-lab
LicenseUnknown
Version0.1.1
Sourcemcp-registry
npm@powforge/captcha-mcp
GitHubzekebuilds-lab/captcha-mcp
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—
Dependencies✓ 6 resolved · none vulnerable
Tool surface3 tools · none privileged
Security scan✓ Cleanv0.2.4 · 20d ago
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

Your MCP server returns 429 when agents pound it. captcha-mcp makes them earn their next call instead. Hand the agent a proof-of-work puzzle (free, ~5s of CPU) or a 3-sat Lightning invoice — both are machine-readable backoff signals an autonomous caller can satisfy without an account, email, or API key. Three tools over stdio or HTTP. Stdlib only. No signup, free fallback, self-hosted, no revenue share. 429 Too Many Requests is the wrong shape for the agent era. Three patterns recur across MCP…

Keywords
mcp