x402 & MCP Server Index (Tanod)

Was du damit machen kannst

Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.

• Verbindung: Läuft in der Cloud
• Transport: Streamable HTTP
• Kategorie: Sonstiges

Installation

Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.

Du brauchst

• Läuft in der CloudNichts zu installieren; die Verbindung läuft übers Internet

Welche App nutzt du?

https://tanod.dev/mcp/agents

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

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

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

https://tanod.dev/mcp/agents

Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.

Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.

Was er kann

Tool-Namen und -Beschreibungen genau so, wie der Server sie am 8. Nov. 2026 gemeldet hat. Geschrieben hat sie der Entwickler, nicht wir; wir zeigen sie als reinen 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

Basischecksi

Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 8. Nov. 2026

• ! Vorsicht

  Entwickler passt zum Repo

  Die Registry nennt kein Quell-Repo, deshalb können wir den Herausgeber (tanod.dev) nicht dem Code zuordnen

• … Noch nicht geprüft

  Wird noch gepflegt

  Dieses Repo haben wir noch nicht von GitHub gelesen

• … Noch nicht geprüft

  Hat eine Lizenz

  Dieses Repo haben wir noch nicht von GitHub gelesen

• ✓ Bestanden

  Endpunkt antwortet

  Antwort in 311 ms (HTTP 200)

• – Nicht zutreffend

  Anmeldung mit OAuth

  Keine Anmeldung nötig

• ✓ Bestanden

  Keine versteckten Anweisungen in Tool-Beschreibungen

  Wir haben 32 Tool-Beschreibungen gelesen und keine versteckten Anweisungen an die KI gefunden

Im Vergleich mit anderen in Sonstigesi

• Mehr Sterne als 0 % der anderen 18436 Server in dieser Kategorie
• Neuer in der Registry veröffentlicht als 66 % der anderen 18436 Server in dieser Kategorie
• Basischecks gleich gut wie oder besser als bei 36 % der anderen 18436 Server in dieser Kategorie

Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.

Alternativen

Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.

So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti

README vom Entwickler

Keine README im Repo gefunden