scout-packs-mcp
This server lets AI agents browse and buy verified B2B lead packs and per-lead enrichment from Scout Packs, paying in USDC on Base via x402.
list_packs (free): see pack sizes, prices, live sales status, and a redacted sample.
buy_pack (pack "25", "50", or "100"): get exact x402 payment terms and the step-by-step flow; the agent's own wallet pays the endpoint — the server never holds keys or moves funds.
lookup_lead (query = company name or domain, e.g.
Acme Corporacme.com): get x402 payment terms for one verified B2B contact lookup.All payment-returning tools are read-only quote/instruction providers; the buying agent executes the USDC payment itself.
Note: the schema lists lookup at $0.10 USDC while the README states $0.01 — a pricing discrepancy worth confirming.
Click on "Deploy 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., "@scout-packs-mcp show me the B2B lead packs and how to pay for the 25-lead pack"
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.
Scout Packs — Tiger Operations
Verified B2B lead packs and per-lead enrichment lookups sold to AI agents over
x402 (USDC on Base, eip155:8453). Demand-probe pricing (2026-10-04):
$0.01 per lookup or pack. Margin inversion vs. Scout COGS is acknowledged —
this is a demand probe, not a business model. Kill gate: ≥3 paid lookups from
≥2 distinct wallets in 7 days post-reprice.
Pack | Leads | Price | Fulfillment |
scout-pack-25 | 25 | $0.01 | instant JSON download after payment |
scout-pack-50 | 50 | $0.01 | assembled on demand, delivered within 24h |
scout-pack-100 | 100 | $0.01 | assembled on demand, delivered within 24h |
Per-lead enrichment: GET /lookup?query=<company or domain> — 402 paywall,
$0.01 USDC, POST /fulfill-lookup returns one verified business email +
source URL + provenance.
Composite dossier: GET /dossier?domain=<domain> — 402 paywall,
$0.05 USDC, POST /fulfill-dossier returns a composite domain dossier:
RDAP registration + DNS infrastructure signals, tech-stack detection,
likely corporate email patterns + MX verification, and SSL/TLS certificate
health for one domain, fused into a single response with an aggregated
signals list — the /domain-intel, /tech-stack, /email-pattern, and
/ssl-check results in one call instead of four separate calls.
Each lead: company_name, city_state, category, contact_email (verified business email), source_url.
Endpoints
GET /— human landing pageGET /catalog— packs & prices (JSON)GET /.well-known/x402— machine-readable payment termsGET /llms.txt— agent buying instructionsGET /packs/{25,50,100}/preview— redacted preview (emails masked), freeGET /packs/{25,50,100}—402withPAYMENT-REQUIRED(v2) +X-PAYMENT-REQUIRED(v1) headersGET /lookup?query=<company or domain>—402with payment terms ($0.01 USDC); no match →404POST /fulfill—{"tx_hash":"0x...","pack":"25","deliver_to":"..."}POST /fulfill-lookup—{"tx_hash":"0x...","query":"<company>"}GET /dossier?domain=<domain>—402with payment terms ($0.05 USDC); composite domain dossier: domain intel + tech stack + email patterns + SSL check fused into one callPOST /fulfill-dossier—{"tx_hash":"0x...","domain":"<domain>"}GET /skill.md— agent skill file for the lead lookup (markdown)/mcp— MCP streamable-HTTP endpoint (proxied to the sibling MCP server whenMCP_PROXY_PORTis set)
Related MCP server: MCP-Pay
Interface reference (for agent/MCP clients)
GET /packs/{25,50,100} → 402 Payment Required
Headers:
PAYMENT-REQUIRED= base64(JSON x402 v2 terms),X-PAYMENT-REQUIRED= base64(JSON x402 v1 terms)Body:
{error:"payment_required", pack, leads, price_usd, currency:"USDC", network:"eip155:8453", fulfillment, sales_enabled, x402:{x402Version:2, accepts:[{scheme:"exact", network, amount (atomic USDC, 6 decimals), description, mimeType, payTo, maxTimeoutSeconds, asset, extra}], resource:{url, description, mimeType}}, how_to_pay:[...]}sales_enabled:falsewhile the seller address is unconfigured (current state); flips automatically once set.
POST /fulfill — body {tx_hash:"0x…", pack:"25"|"50"|"100", deliver_to:"…" (optional)}
Success, pack 25 →
200 {receipt:"ok", pack:"scout-pack-25", tx_hash, verified_at, leads:{…25-lead pack JSON…}}Success, pack 50/100 →
200 {receipt:"ok", pack, tx_hash, verified_at, order_id, status:"queued_for_assembly", eta:"within 24 hours of payment confirmation", deliver_to, note}Failure →
402 {error:"payment_not_verified", detail:"sales_paused: receiving address not configured" | "bad_tx_hash" | "already_redeemed" | "tx_not_found" | "tx_not_successful" | "tx_too_old" | "no_matching_usdc_transfer" | "chain_lookup_failed", pay:[…steps…]}or400 {error:"unknown_pack"|"bad_json"}
Verification rules: tx must be a successful Base USDC transfer of ≥ the pack amount to the configured receiving address, mined <30 days ago, and each tx hash is single-use.
Buying flow
GET /packs/25→ read the 402 terms (payTo, exact USDC amount).Standard x402: sign an EIP-3009 authorization for exactly $0.01 USDC on Base to
payToand retry the same request with the signature in theX-PAYMENT(v1) orPAYMENT-SIGNATURE(v2) header. The payment is verified + settled via facilitator and pack 25 is returned immediately (50/100 return a 24h order receipt).Fallback: send exactly $0.01 USDC on Base to
payToyourself, thenPOST /fulfillwith the tx hash.
Payment is verified on-chain (Blockscout free API): the tx must be a successful USDC transfer of ≥ the pack amount to the receiving address. Tx hashes are single-use (replay-protected); txs older than 30 days are rejected.
Config
SCOUTPACKS_RECEIVING_ADDRESS— the Base address that receives USDC. While unset (or the zero address) the endpoint runs in preview-only mode:sales_enabled=falsein 402 bodies and/.well-known/x402, and/fulfillrefuses all requests.SCOUTPACKS_PUBLIC_BASE— public URL used in 402resourcefields.PORT— default 8000.MCP_PROXY_PORT— optional (e.g.8001); when set,/mcpreverse-proxies to the sibling MCP streamable-HTTP server (mcp/http_server.py) on that port — one deploy exposes both the x402 API and a durable-HTTPS MCP endpoint.
Deploy
./run.sh & # localhost:8000Production (since 2026-10-02) runs on Railway —
https://scout-packs-production.up.railway.app is the sole production endpoint.
The old localtunnel path (lt-proxy.js, loca.lt subdomains) is dead legacy, retired
2026-10-02 after chronic 503s. On normal infra for a fresh deploy,
cloudflared tunnel --url http://127.0.0.1:8000 works as usual.
Then register on the open indexes, e.g. 402 Index:
POST https://402index.io/api/v1/register with
{url, name, protocol:"x402", description, price_usd, payment_asset:"USDC", payment_network:"eip155:8453", category:"data", tags:[...]}.
MCP server (for agent clients)
AI agents can also discover and buy packs from inside MCP clients
(Claude Desktop, Cursor, MCP Inspector, agent frameworks) via the MCP server
in mcp/:
list_packs— free. Pack sizes, prices, live sales status, redacted sample.buy_pack— returns the exact x402 payment terms and the step-by-step flow; the buying agent's own wallet pays the endpoint. Never moves funds, never holds keys.
Quick start (Python 3.10+, installs the mcp SDK only):
cd mcp && python3 -m venv .venv && .venv/bin/pip install mcp
BASE_URL=https://<endpoint-url> .venv/bin/python scout_packs_mcp.pyOr once published to PyPI: uvx scout-packs-mcp with BASE_URL set.
Full docs: mcp/README.md. Registry listings:
mcp/REGISTRIES.md.
Available Tools
3 toolsbuy_packAInspect
Get the exact x402 payment requirements and step-by-step buying flow for a Scout Pack. pack: "25", "50", or "100". Returns what the buying agent must do; the agent's own wallet executes the USDC payment against the endpoint.
Inputs: pack (required). Returns: result
list_packsAInspect
List Scout Packs for sale: sizes, prices, and a redacted sample. Free.
Inputs: no named parameters. Returns: result
lookup_leadAInspect
Look up one verified B2B contact by company name or domain. $0.10 USDC per lookup. Returns the x402 payment requirements; your agent's wallet executes the payment. Example: lookup_lead(query="Acme Corp") or lookup_lead(query="acme.com")
Inputs: query (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: list_packs browses inventory, buy_pack initiates a pack purchase, and lookup_lead performs a separate B2B contact lookup. There is no overlap in action or resource that would cause misselection.
All three tools follow a consistent snake_case verb_noun pattern: list_packs, buy_pack, lookup_lead. The convention is predictable and readable throughout.
Three tools is on the lower end but plausible for a narrow commerce-and-lookup server. It covers the advertised flows without bloat, though slightly more (e.g., a status or retrieval tool) could be expected.
The surface covers browsing, buying, and a single lead lookup, but lacks post-purchase retrieval or payment confirmation, and lead lookup only supports one query at a time. These gaps may force agents to rely on external endpoints or repeated calls.
Maintenance
Related MCP Connectors
AI marketplace for agents to find paid work and trade digital services via MCP and x402.
Agent-native MCP for governed commerce, x402 payments, paid capabilities, and verifiable receipts.
Marketplace where AI agents buy datasets and API access, pay per call in USDC over x402.
Agentic commerce + trust MCP: discover, verify, and transact across droplinked's merchant network.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to discover, call, and pay for existing HTTP APIs over MCP with x402 paywalls, non-custodial settlement, and no code changes to the backend.688 npm74Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to discover and pay for MCP tools on a sub-cent, pay-per-call basis using x402 and Algorand USDC settlements.252 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables agents to access production-grade paid MCP tools with real on-chain x402 v2 settlement, including EVM wallet risk scoring, payload normalization, and facilitator discovery, all discoverable via Bazaar-compatible metadata.MIT
- FlicenseNot gradedqualityCmaintenanceProvides paid and free tools for AI agents to buy from or sell to other agents over x402, including discovering sellers, verifying on-chain payment histories, running test purchases, and registering sellers for audited listings.-