io.github.b0ase/path402

Name: io.github.b0ase/path402
Rating: 60 (1 reviews)
Author: io.github.b0ase

MCPcommunity

v1.3.2io.github.b0aseUnknownUpdated 3mo agonpm GitHub

AI agents discover, acquire, and re-serve tokenised web content via the $402 protocol

Turn AI agents into autonomous economic actors. Run a $402 network node. This package includes: MCP Server — AI agent tools for Claude, GPT, etc. path402d Daemon — Index tokens, serve content, earn rewards This starts a $402 network node that: INDEX — Reads BSV blockchain, tracks all $402 tokens VALIDATE — Confirms token ownership before serving SERVE — Delivers content to verified token holders…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

3mo agoLast update

Package

Authorio.github.b0ase

LicenseUnknown

Version1.3.2

Sourcemcp-registry

npmpath402

GitHubb0ase/path402

Trust Status

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✓ 60 resolved+ · none vulnerable

Tool surface—

Security scan✓ Cleanv1.3.2 · 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

Keywords

mcp