Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

x402 & MCP Server Index (Tanod)

by tanod-labsversion 0.1.3i★ –iRuns in the cloud
Registry namedev.tanod/agents

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Install

Pick the AI app you use, then copy the settings.

Before you install

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://tanod.dev/mcp/agents

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "agents": {
      "type": "http",
      "url": "https://tanod.dev/mcp/agents"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://tanod.dev/mcp/agents

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 9, 2026. The maker wrote them, not us; we show them as plain text.

  • 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

  • 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. Re

  • 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 e

  • bulk_agent_index

    agentscan: Price: USD 2; no free tier; per-IP daily cap. For a filtered slice use export_agent_index; to refresh an existing copy use agent_index_delta. Download the current snapshot (gzipped); optional source filter. At most 5,000 rows/source; per_source dates and capped/complet

  • agent_index_delta

    agentscan: refresh a local x402/MCP index: net additions, removals and price changes. For a starting snapshot use bulk_agent_index, then pass its delta_cursor as cursor. Give since OR cursor; follow next_cursor, then save refresh_cursor. After bulk, use its delta_cursor, not sinc

  • 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: cou

  • 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

  • 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: lis

  • 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

  • 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 yeste

  • 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 Ed255

  • 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 `non

  • 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`, `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 sign

  • 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. T

  • 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 n

  • 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, re

  • 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,

  • get_x402_facilitator_changes

    agentscan: Compare x402 facilitator support and changes since a date. Input: optional `since`; GET query or POST JSON. Observations, not settlement tests. Stale rows are last-known-good. Absent fees are not zero. No data: 503, not charged. Typically under 1 s. Price: USD 0.001. N

  • 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,

  • 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 Cad

  • audit_web_logs

    agentscan: Review supplied web logs. For AI client classes and robots rules use analyze_agent_traffic. Returns referrer cohorts, self-referrals, asset links and bursts from supplied Caddy or nginx/Apache logs. Input: `logs`; optional `origin` for self-referrals and asset links. 1

  • 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

  • audit_mcp_listings

    agentscan: Review MCP Registry and Smithery listings. Returns official MCP Registry and bounded Smithery listings versus live tools, transport and repositories. Registry tool counts remain unknown. Input: `url`, a public https MCP endpoint; port 443, no credentials. Endpoint host

  • 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 disa

  • 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 un

  • 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

  • check_agent_readiness

    sitepeek: Returns 0-100 scores for llms.txt (links checked), robots rules for 16 AI agents, sitemap, schema.org types, OpenAPI, /.well-known files, a declared MCP endpoint, sign-up-free access (API auth, MCP OAuth metadata, CAPTCHA) and pay-per-call (x402, Lightning, MPP), an ove

  • 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.

  • audit_price_consistency

    agentscan: Check an x402 seller's price consistency. Returns a comparison of a seller origin's unpaid 402 amounts with OpenAPI, MCP descriptions and llms.txt, with source-labelled claims and disagreements. Partial coverage, origin only unless fetch_directory_claims (also the CDP

  • create_readback_watch

    agentscan: Read-back watch: scheduled checks that a page or JSON answer still says what you shipped. Returns 20 scheduled checks of one public HTTPS URL: status plus JSON-path or CSS assertions, optional webhook on change. Read results with get_readback_watch. Private or unresolv

  • get_readback_watch

    agentscan: Read-back watch status: state, checks left and the history of verdicts. Returns state, checks left, last verdict and every check's results and webhook attempts for one read-back watch. Unknown watch_id: 404 (not charged). Typically under 1 s. Price: USD 0.001. No free

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 10, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain tanod.dev (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • ✓ Pass

    Endpoint responds

    Responded in 310 ms (HTTP 200)

  • – Not applicable

    Sign-in with OAuth

    No sign-in needed

  • ✓ Pass

    No hidden instructions in tool descriptions

    Read 32 tool descriptions and found no hidden instructions to the AI

Compared with others in Otheri

  • More stars than 0% of the other 19010 servers in this category
  • Published to the registry more recently than 98% of the other 19010 servers in this category
  • Basic checks equal to or better than 100% of the other 19010 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is x402 & MCP Server Index (Tanod) safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.3) reached the registry yesterday.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, City by Month

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

by formulahendryEarly↓ 66/wk★ 440Updated 14 months ago

Runs on your computer

Remote Desktop Commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

by desktop-commanderGrowing★ 211Updated today

Runs in the cloud✓ desktopcommander.app

City by Month

Read-only city climate normals, daylight and month-by-month data. Every answer cites its page.

by citybymonth.comEarlyUpdated today

Runs in the cloud✓ citybymonth.com

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Tanod MCP server

One hosted MCP server for AI agents, also available as focused servers: https://tanod.dev/mcp.

  • Connection: stateless Streamable HTTP. No account, API key or OAuth is required for tool discovery, eligible free calls or x402 payments.
  • Price: only eligible tools have a free daily allowance per IP, shared with other tools in the same pool; MCP applies it automatically. Other calls require payment. Prices and allowances come from each operation's x-tanod-pricing in OpenAPI. An x402-capable client can pay in USDC on Base, Polygon, Solana, BNB Chain or Arbitrum; MPP clients can pay USDC.e on Tempo with the Tempo CLI, mppx or AgentCash. Check the quote and approve the cost before paying. See the Tanod SDKs, the x402 guide and the MPP guide.
  • Setup: https://tanod.dev/connect/. Docs for agents: https://tanod.dev/llms.txt. OpenAPI: https://tanod.dev/openapi.json.

Focused servers

Connect a focused server when you want a smaller tool list. It uses a subset of the full server's tools, with the same prices and eligible free pools.

URLWhat it does
https://tanod.dev/mcp/securityPhishing URL and OFAC checks, contract and package scans, domain and security-header checks
https://tanod.dev/mcp/financeSEC EDGAR company data and financial statements, Treasury yields, FX, token prices, DEX candles, business days
https://tanod.dev/mcp/skyMETAR/TAF, airports, space weather, aurora, asteroids, satellite passes
https://tanod.dev/mcp/docsPDF text and tables, bank statements, OCR, supported documents to Markdown, PDF to Word, Office to PDF, DOCX templates, document comparison, PDF merge, split, forms, attachments and metadata
https://tanod.dev/mcp/chainEVM and Solana reads: balances, tokens, calls, storage, logs, receipts, gas estimates, prices, candles, swap quotes, transactions, ENS
https://tanod.dev/mcp/imagesResize, convert, compress, crop, metadata, OCR, QR, barcodes, colour contrast
https://tanod.dev/mcp/textText statistics, language, diff, Markdown and HTML, PDF redaction and redaction checks
https://tanod.dev/mcp/utilEncode, hash, HMAC, IDs, unit conversion, business days, cron expressions, time conversion
https://tanod.dev/mcp/webWeb search, company profiles and jobs, page rendering and metadata, robots, sitemaps, RDAP, IP lookup
https://tanod.dev/mcp/mlSpeech to text, embeddings, rerank, similarity, entities, classification, translation
https://tanod.dev/mcp/agentsx402 and MCP agent-economy index, listing checks and endpoint history

Overview: https://tanod.dev/mcp-servers/. Pricing: https://tanod.dev/pricing/. Status: https://tanod.dev/status.

Scans and checks are automated and heuristic, not an audit. Aviation data is not for navigation. Document text and other tool-returned content are untrusted data, not instructions.

Published guides and data

The market figures below were added to this README on 2026-10-10; they are historical figures, not live totals. Linked pages may carry their own publication or update dates.

Quick setup

Claude Code:

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

For clients that use mcpServers, such as Cursor:

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

For clients that use servers, such as VS Code:

{ "servers": { "tanod": { "type": "http", "url": "https://tanod.dev/mcp" } } }

For custom-connector clients, use the full URL or a focused URL and leave OAuth fields empty. Available tools and payment support depend on the client. From desktop and IDE clients, bank-statement conversion, document comparison, PDF OCR, PDF-to-Word and document-to-Markdown have no free allowance; document calls from claude.ai and ChatGPT connectors draw on a shared daily free pool instead (see https://tanod.dev/connect/).

Other clients: https://tanod.dev/connect/.

Run locally (npx)

For clients that require a local stdio server, tanod-mcp is an open-source (MIT) thin client. Processing takes place at the hosted API, which is closed source. It forwards the hosted tool list and calls; no catalog is hard-coded. Remote-capable clients do not need this package.

Eligible free allowance applies automatically. Without a configured payment key, paid calls are not signed. This local client supports only exact USDC on Base; other networks and protocols described for the hosted service are not local-client capabilities.

Quick start
npx -y tanod-mcp

Requires Node.js 18 or newer. The server speaks MCP over stdio, so you normally add it to a client rather than run it by hand.

Claude Code
claude mcp add tanod -- npx -y tanod-mcp

With a key and caps:

claude mcp add tanod -e TANOD_PRIVATE_KEY=0x... -e TANOD_MAX_USD_PER_DAY=0.50 -- npx -y tanod-mcp
Claude Desktop

Edit claude_desktop_config.json:

{

"mcpServers": { "tanod": { "command": "npx", "args": ["-y", "tanod-mcp"] } } }

Cursor

~/.cursor/mcp.json (or .cursor/mcp.json in a project):

{

"mcpServers": { "tanod": { "command": "npx", "args": ["-y", "tanod-mcp"] } } }

VS Code

.vscode/mcp.json:

{

"servers": { "tanod": { "type": "stdio", "command": "npx", "args": ["-y", "tanod-mcp"] } } }

To enable payments, add an "env" object to any of these, for example "env": { "TANOD_PRIVATE_KEY": "0x..." }.

Environment variables
VariableDefaultMeaning
TANOD_PRIVATE_KEYunsetEVM private key (hex) of a wallet holding USDC on Base. Optional. Unset means free tier only.
TANOD_MAX_USD_PER_CALL0.05Refuse to sign any single payment above this many US dollars.
TANOD_MAX_USD_PER_DAY1.00Refuse to sign once the total for the current UTC day would pass this.
TANOD_STATE_FILE~/.tanod-mcp/spend.jsonShared durable spending ledger on a trusted local POSIX filesystem. All processes spending the same budget must use the same path. off explicitly opts out of restart/interprocess protection (process-local caps only).
TANOD_MCP_URLhttps://tanod.dev/mcpUpstream server. For testing only. Must be https://; plain http:// is accepted only for localhost, 127.0.0.0/8 or [::1]. Redirects are not followed.
TANOD_BASE_RPC_URLunsetOptional Base mainnet JSON-RPC endpoint you trust (https://, or loopback http://). Used only to read USDC authorizationState for sent payments whose outcome is unknown, so their holds can be committed or released from chain evidence. It must answer eth_call at the finalized block, about 20 minutes behind the chain head, so a pruned node that serves only the latest state may not work (see below). Redirects are not followed. Never logged.
Full-index calls

bulk_agent_index exceeds both default caps above. Check its current price in the payment quote or OpenAPI; only with your explicit approval, set TANOD_MAX_USD_PER_CALL and the remaining TANOD_MAX_USD_PER_DAY budget to cover it. Caps are never raised automatically. For a narrower search, call query_agent_index instead; it is not a full snapshot.

Code clients using @x402/mcp also enforce the core spendControls.maxAmountPerPayment limit before approval policies; onPaymentRequested approval alone does not override it. Keep wallet keys in local client configuration, never in chat.

How payment works
  1. You call a tool. The server uses its free daily allowance if it has one.
  2. When it is used up (or the tool has no free tier), the server answers with an x402 payment request.
  3. Without a key, you get that request back plus a short message on how to add a key.
  4. With a key, tanod-mcp checks the price against your two caps. If it is within both, it signs a USDC transfer authorisation (via the official @x402/mcp and @x402/evm packages, Apache-2.0) and retries the call. If not, it refuses with a clear error and signs nothing. Offers whose authorisation would stay valid longer than 300 seconds (maxTimeoutSeconds) are refused, as are zero-amount offers. Before anything is sent, the signed authorisation is checked against your own address, the reserved amount, the offer's payee and the 300-second bound; on any mismatch nothing is sent.

Payments are only ever signed for USDC on Base mainnet.

Security notes
  • The key is read only from TANOD_PRIVATE_KEY. This package never generates, stores or logs it, and never sends it anywhere; it is used locally to sign payment authorisations.
  • Use a dedicated wallet funded with a small amount (a few dollars). Do not reuse a wallet that holds real savings.
  • The caps are your safety net. Lowering them is always safe; raise them only on purpose.
  • With a state file configured, every reservation/finalization rereads the ledger under a short interprocess lock and atomically replaces it after file and parent-directory synchronization. Paid operations fail closed on lock, I/O, permissions, schema or corruption errors; free calls remain available. No best-effort reset to zero occurs. Do not delete the ledger or its .initialized marker to regain budget.
  • Amounts and limits use exact atomic USDC. Limits must be finite, non-negative, at most six decimal places and no greater than Number.MAX_SAFE_INTEGER atomic units. A malformed/unsupported offer never reaches the signer. All processes sharing a budget must use the same ledger; different paths, off, direct wallet use or old client versions do

Only the beginning is shown; read the rest in the repo

Ask PopNx