com.twelvepermissions/x402-doctor

MCPcommunity
v1.0.0com.twelvepermissionsUnknownUpdated todayGitHub

Diagnose x402 seller endpoints: what is wrong with your 402 challenge, and how to fix it.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
todayLast update
Package
Authorcom.twelvepermissions
LicenseUnknown
Version1.0.0
Sourcemcp-registry
GitHubtsharpe2282-web/twelve-permissions
Trust Status
F
10/100Untrusted
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
—Prompt-injection scan · not run+0/30
→ Not yet scanned — the repository archive is scanned on the next cron run
—Obfuscation / exfil scan · not run+0/20
→ Not yet scanned — the repository archive is scanned on the next cron run
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scanNot run
EvalsNone
IndexedAug 18, 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

Diagnose x402 seller endpoints: what is wrong with your 402 challenge, and how to fix it.

Keywords
mcp