All servers · Agent payments (x402)

x402 & MCP Server Index (Tanod)

dev.tanod/agents · v0.1.2

Measured by MCP Station

Instruction-like text was found in scan_agent_package. This is a pattern match, not a verdict. What we look for

Description written by the publisher, not verified

x402 endpoint and MCP server index: find paid APIs for agents, x402 checks and price benchmarks.

Connect

claude mcp add --transport http agents https://tanod.dev/mcp/agents

{
  "mcpServers": {
    "agents": {
      "url": "https://tanod.dev/mcp/agents"
    }
  }
}

Tools as reported by the server

• query_agent_index
  agentscan: query a daily cross-registry index of x402 endpoints and MCP servers. For one file of up to 5,000 rows use export_agent_index; for one record's history use get_endpoint_history. Typically 0.1-2 s. Price: USD 0.02. Free: 10 queries per IP per UTC day. Data is aggregated public-registry dat
• get_endpoint_history
  agentscan: presence and price history of ONE indexed record. To find records use query_agent_index. Returns the record plus its dated presence rows and the points where its price changed over time. Typically 0.1-2 s. Price: USD 0.05. Free: 5 history lookups per IP per UTC day. Records not in the ind
• export_agent_index
  agentscan: export a filtered slice of the index. For page-by-page reads use query_agent_index; for every record use bulk_agent_index. Returns the matching current-snapshot records. Typically 0.2-3 s. Price: USD 0.25; no free tier. Data is aggregated public-registry data, not an endorsement of any li
• bulk_agent_index
  agentscan: download the full current snapshot of the index (all sources, per-source row cap, gzipped). For a filtered slice use export_agent_index. Input: optional `source` to restrict to one source. Returns every current-snapshot record. Typically 1-5 s. Price: USD 2; no free tier, and a per-IP dai
• benchmark_x402_price
  agentscan: Benchmark an x402 endpoint price against listed prices for similar endpoints. For a pay or avoid verdict use check_x402_endpoint_before_paying; for a full listing review use x402_listing_audit. Returns the listed USD prices of x402 endpoints matching a description: count, hosts, median, q
• check_x402_endpoint_before_paying
  agentscan: Check an x402 endpoint before paying it: pay, caution or avoid, with reasons. For a seller checking their own listing use x402_seller_report; for listed prices alone use benchmark_x402_price. Returns reasons with evidence from one unpaid request to its live 402 and the agent index (payTo
• x402_seller_report
  agentscan: x402 seller report: lint, price position, buyer preflight and Bazaar demand for one endpoint. For category demand history, 10 peers and ranked fixes use x402_listing_audit; for lint alone use lint_x402_listing. Returns one report on an x402 endpoint for its seller: listing lint, price pos
• x402_listing_audit
  agentscan: x402 listing review: lint, category demand history, 10 closest peers and ranked fixes. For a cheaper report without peers or history use x402_seller_report. Returns a full review of one x402 listing: lint, price position, preflight, 30-day category demand history, the 10 closest listings
• get_x402_bazaar_pulse
  agentscan: Use when an agent must decide what to list or price on x402: today's Bazaar listings, new sellers, payer gains and gaps. For endpoints with repeat payers use get_x402_repeat_demand. Returns the daily pulse of the x402 Bazaar: listings, sellers, new and gone since yesterday, payer gains, m
• test_x402_payment
  agentscan: Make a real x402 payment to test your wallet and client, with a signed receipt. To check a signed authorization without paying use x402_payment_status; to vet a seller before paying use check_x402_endpoint_before_paying. Returns what the payment gate saw, with an Ed25519-signed UTC receip
• x402_payment_status
  chainpeek: Check an x402 payment: was its USDC authorization used, can it still settle. To make a real test payment instead use test_x402_payment. Returns whether one x402 payment authorization (EIP-3009) was used. Input: `network` and either `x_payment` or `authorizer` with `nonce` and an optional
• x402_receipt_check
  chainpeek: Check an x402 receipt: did this transaction hash pay that amount to that address. Returns the token transfer in one transaction (chain, full hash, sender, recipient, explorer link, token, amount, block time, confirmations) and a `verdict` against `expect_pay_to`, `expect_amount` and `expe
• x402_well_known_file
  agentscan: Build an x402 seller's /.well-known/x402 file from its Bazaar listings. Returns the /.well-known/x402 file body for one seller host, built from its current Bazaar and PayAI listings, with an instructions skeleton and the steps to add the ownership proof the seller signs. A draft from the
• x402_edge_check
  agentscan: Edge 402 check: does your CDN or WAF still serve the x402 challenge to AI bots. Returns what a URL answers to an AI-bot request and a plain one, unpaid: is the 402 there, cached, replaced by a CDN error page, or too large for common HTTP clients, with coded findings. Two unpaid requests,
• check_mcp_server
  agentscan: Check whether a remote MCP server is up and what it offers. It reads no code; to scan a package before installing use scan_agent_package; to check a repo against an awesome list use preflight_mcp_listing. Returns a live check of a public remote MCP server: answers or not, name, version, p
• scan_agent_package
  toolsniff: Scan an AI-agent skill or MCP server package before installing it. To see whether a remote MCP server answers use check_mcp_server. Reads every file as text in a sandbox. Returns a verdict, a risk_score 0-100 and file:line findings: prompt injection, tool poisoning, remote code execution,
• get_x402_repeat_demand
  agentscan: Find x402 endpoints with repeat paying demand: 2+ calls per payer in 30 days, sweeps left out. For the whole market today use get_x402_bazaar_pulse. Returns x402 endpoints whose 30-day payers average 2+ calls each (at least `min_payers`, default 3), most payers first, with payers, calls,
• identify_x402_client
  agentscan: Identify an x402 client by User-Agent: monitor, indexer, grader or HTTP library, with call rate. For any other User-Agent use parse_user_agent; for a whole access log use analyze_agent_traffic. Returns whether a User-Agent is a known x402 monitor, indexer, grader, SDK, AI fetcher, bot or
• analyze_agent_traffic
  agentscan: Analyze AI crawler, assistant, MCP and x402 buyer traffic in access logs. For one User-Agent use identify_x402_client or parse_user_agent. Returns requests per client class (AI crawlers, assistants, MCP clients, x402 buyers, monitors, HTTP libraries, browsers) from Caddy, nginx/Apache or
• preflight_mcp_listing
  agentscan: Check an MCP server repo against a punkpeye awesome list's rules before opening a PR. To see whether the server answers use check_mcp_server; to scan its code use scan_agent_package. Returns each rule the chosen list enforces today (public repo, README, licence, Glama score, duplicates, t
• check_apify_store_rules
  agentscan: Check Apify Actors against Store publishing rules. For an MCP server repo against an awesome list use preflight_mcp_listing; for a site's AI-agent readiness use check_agent_readiness. Returns checks public Apify Actors for outside payment links, README prices that disagree with the Actor'
• get_endpoint_uptime
  agentscan: Use when an agent must know if an x402 endpoint or MCP server was up, with a valid 402, over the last 30 days. Returns 30-day uptime share, valid x402 402-envelope share, median and p95 latency and last failures of one x402 endpoint, MCP server or host, from Tanod's unpaid probes of the a
• get_endpoint_uptime_bulk
  agentscan: Use when an agent must compare the 30-day uptime and valid-402 share of up to 25 x402 endpoints or MCP servers at once. Returns 30-day uptime, valid x402 402-envelope share, latency percentiles and last failures for up to 25 endpoints or hosts in one call. One vantage point; not a judgeme
• check_agent_readiness
  sitepeek: Check a site's AI-agent readiness: llms.txt, robots, sitemap, schema.org, OpenAPI, MCP. For one URL's robots rule use check_robots_txt; for a live MCP server probe use check_mcp_server; to fix, generate_agent_ready_files. Returns 0-100 scores for llms.txt (links checked), robots rules for
• generate_agent_ready_files
  sitepeek: Generate agent-ready files for a site: robots lines, API catalog, MCP card, skills index. To only score a site use check_agent_readiness; for one URL's robots rule use check_robots_txt. Returns runs the agent-readiness check, then returns file bodies to publish: robots.txt lines, llms.txt

Tool changes

• 2026-10-18: query_agent_index, get_endpoint_history, export_agent_index, bulk_agent_index, benchmark_x402_price, check_x402_endpoint_before_paying, x402_seller_report, x402_listing_audit, get_x402_bazaar_pulse, test_x402_payment, x402_payment_status, x402_receipt_check
• 2026-10-16: query_agent_index, get_endpoint_history, export_agent_index, bulk_agent_index, benchmark_x402_price, check_x402_endpoint_before_paying, x402_seller_report, x402_listing_audit, get_x402_bazaar_pulse, test_x402_payment, x402_payment_status, check_mcp_server

Website · JSON · Text for agents · Registry updated 2026-10-16