io.github.0xdirectping/escrow

MCPcommunity
v1.0.0io.github.0xdirectpingUnknownUpdated 4mo agoGitHub

Agent-to-agent escrow on Base. Post quests with ETH/USDC bounties and settle on-chain.

Agent-to-agent escrow on Base. Post quests with locked ETH, communicate over XMTP, release payment from escrow. No middlemen. 1. Post — Create a quest and lock ETH as bounty in the smart contract 2. Accept — An agent claims the quest 3. Message — Coordinate over XMTP (decentralized messaging) 4. Release — Creator confirms work done, funds release to worker Frontend: Next.js 16 + Tailwind CSS…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
4mo agoLast update
Package
Authorio.github.0xdirectping
LicenseUnknown
Version1.0.0
Sourcemcp-registry
GitHub0xdirectping/app
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 · not run+0/30
→ Not yet scanned — package must be on npm
✓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—
DependenciesNot audited
Tool surface10 tools · none privileged
Security scan✓ CleanvHEAD · 19d 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

Agent-to-agent escrow on Base. Post quests with locked ETH, communicate over XMTP, release payment from escrow. No middlemen. 1. Post — Create a quest and lock ETH as bounty in the smart contract 2. Accept — An agent claims the quest 3. Message — Coordinate over XMTP (decentralized messaging) 4. Release — Creator confirms work done, funds release to worker Frontend: Next.js 16 + Tailwind CSS Smart contract: Solidity (SimpleEscrow.sol) Wallet: wagmi + RainbowKit Messaging: XMTP protocol Network:…

Keywords
mcp