seeder-402
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@seeder-402start a 7-day replication lease for my Hyperdrive key"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
seeder-402
An HTTP/MCP service for replicating buyer-supplied Hypercore/Hyperdrive keys for USDC on Base via x402.
Overview
seeder-402 implements an always-on replication service that sells access to buyer-supplied Hypercore/Hyperdrive keys on Base network. The system enables publishers to host up to 50MB bundles for 7 days, while maintaining 24-hour discovery keys and supporting lease-based access control.
Related MCP server: pyrimid
Architecture
Two processes, one VPS, one database:
[Agent] --HTTP 402 / MCP--> [api] --Unix socket--> [blind-peer]
|
[SQLite]api (Node 22+): x402 middleware, MCP paid tools, lease JWT/HMAC, quotas, OpenAPI
blind-peer (Holepunch CLI): DHT, Corestore, replication (no payments logic)
SQLite: leases, payments, caps (v1 only)
Verified Deployment Characteristics
The following has been confirmed in production on seed.bparlan.com:
api and peer communicate over a Unix domain socket, not a TCP port.
The socket file is created via unlink-before-listen so both containers see the same file through the shared bind mount.
Socket ownership:
node:nodewith modesrwxr-xr-x; only the owner needs connect/write.peer runs with
network_mode: host; api runs on the Coolify HTTP proxy.Traefik/Coolify terminates TLS for
https://seed.bparlan.com; Coolify serves api on HTTP internally.
System Status
Current Milestone
M0 — Contract (active)
Implemented: Unpaid requests → 402 Base Sepolia USDC
Implemented: Facilitator verify+settle → 200
{ ok: true }Exit criteria:
openapi.json+/.well-known/x402committed; one Sepolia tx withPAYMENT-RESPONSE; curl recipe in PLAYBOOKStatus: Money stub in progress; blind-peer pending
Roadmap
See docs/ROADMAP.md for complete milestone tracking. Current focus: M7 (mainnet) for production readiness.
Quick Start
Prerequisites
# System dependencies
Node 22+
npm (or bun)
blind-peer-cli or blind-peering-cli
better-sqlite3 (npm)Environment Setup
# Configure environment (never commit)
export NETWORK=eip155:84532 # Base Sepolia
export PAY_TO=0x... # Payment recipient
export FACILITATOR_URL=https://x402.org/facilitator
export LEASE_SECRET=... # JWT secret
export PEER_KEY=... # Blind-peer key
export STORE_PATH=/var/lib/seeder-402/corestore
export DB_PATH=/var/lib/seeder-402/leases.db
export MAX_KEYS=200
export MAX_BYTES_PER_KEY=52428800
export MAX_BODY_BYTES=52428800
export PRICE_SEED_USD=0.10
export PRICE_PIN_USD=0.20
export PRICE_HOUSE_USD=0.50
export PRICE_STATUS_USD=0.01Run
# Start blind-peer for DHT
blind-peer -s $STORE_PATH
# Start API
node dist/index.js
# or
bun tsx src/index.tsTesting
# Test unpaid request (should return 402)
curl -i https://HOST/v1/status?key=00..
# Test paid request (Sepolia)
Use @x402/fetch or CDP Payments MCP with test USDCDocumentation
Document | Purpose |
Architecture patterns, module organization, extension guidelines | |
System specification, public APIs, data models | |
Milestone progress, future plans, completed items | |
Operational procedures, deployment, common tasks | |
Database schema, configuration, data flow patterns |
Project Structure
seeder-402/
├── AGENTS.md # Agent entry point, build/test commands, conventions
├── README.md # This file
├── docs/ # Canonical documentation
│ ├── FRAMEWORK.md
│ ├── SPEC.md
│ ├── ROADMAP.md
│ ├── PLAYBOOK.md
│ ├── DATA.md
│ └── context/ # Background and architectural context
├── milestones/ # Active and archived milestones
│ └── archive/ # Archived milestone artifacts
└── .omp/ # OhMyPi configuration
└── config.yml # Canonical project configurationOhMyPi Workflow
```omp
"Implement M0 only per ROADMAP.md and SPEC.md. Do not start M2."
After each M: run PLAYBOOK tests; commit; stop.Note: This repository is currently at M0 (contract/money stub). Implementation beyond M0 must wait for roadmap progression and revenue signals.
Contribution
Follow the OhMyPi workflow:
Implement exactly one milestone per PR
Adhere strictly to SPEC.md requirements
Run PLAYBOOK.md tests after each change
Do not advance beyond assigned milestone without roadmap approval
Maintain current architecture (no microservices, no reimplementation of core DHT logic)
License
Architecture and documentation under Apache 2.0. Implementation (when created) will follow project license.
This repository is maintained by the p2primitive collective and follows strict milestone-based development discipline.
Project Configuration
project_id: seeder-402
project_slug: seeder-402
mode: application # framework: library, application: runnable service
mechanical_tooling:
environment_manager: Node.js + npm (nodeenv)
fast_linter_formatter: Prettier + ESLint (auto-fixable)
pre_commit_framework: Husky
type_checker: TypeScript
milestones:
current: M0
target: M7
requirements:
node_version: "22.0.0"
base_network: eip155:8453 # Mainnet (production)
base_testnet: eip155:84532 # Base Sepolia (testing)Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
No tool schema history has been recorded yet.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Pay-per-query x402 business intelligence on Base, settled in USDC via the native 402 payment flow.
x402 paywall layer for creator sites and agents: paid content, pricing, reputation, ledger.
Official public-data caches sold per pull via x402/USDC on Base.
x402 V2 payment-to-access on Solana USDC with receipts, entitlements, atomic metering and webhooks.
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server for pay-per-call DeFi and crypto data via x402 micropayments on Base. 8 endpoints: token prices, TVL, funding rates, token security, gas tracker, whale monitoring, wallet profiling, and yield scanning.851MIT
- AlicenseNot gradedqualityFmaintenanceOnchain agent-to-agent commerce protocol using x402 and ERC-8004. Enables AI agents to buy/sell services, manage vendor catalogs, and process payments on Base.MIT
- AlicenseNot gradedqualityDmaintenanceDiscovers and queries x402-payable APIs at runtime — enables autonomous agents to find, evaluate, and pay for services via USDC micropayments on Base without API keys or subscriptions.MIT
- AlicenseNot gradedqualityCmaintenanceEnables web content extraction, reading, crawling, and pricing via MCP tools, with pay-per-fetch in USDC on Base using x402.3MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/bparlan/seeder-402'
If you have feedback or need assistance with the MCP directory API, please join our Discord server