io.github.nexus-mcp-infra/x402-receipt-verifier

MCPcommunity
v1.0.0io.github.nexus-mcp-infraUnknownUpdated 2d agoGitHub

Audits NEXUS's own x402 payment logs against its own delivery logs and issues a signed proof-of-deli

Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). 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 →
2d agoLast update
Package
Authorio.github.nexus-mcp-infra
LicenseUnknown
Version1.0.0
Sourcemcp-registry
GitHubnexus-mcp-infra/x402-receipt-verifier
SBOMCycloneDX 1.6 ↓
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 runHow 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

Not probed yet

Forge has not completed a tools/list handshake against this endpoint, so it holds no observation of what the server exposes. Nothing here says it exposes nothing.

About

Audits NEXUS's own x402 payment logs against its own delivery logs and issues a signed proof-of-deli

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.