tanod.dev
https://tanod.dev/mcp/agents
active Production-safe Score 82/100 http no auth
At a glance
| Endpoint | https://tanod.dev/mcp/agents |
|---|---|
| Source | https://raw.githubusercontent.com/tanod-labs/tanod-mcp/main/plugins/tanod-agents/.mcp.json |
| Transport | http |
| Tools | 33 |
| Auth | none |
| First seen | 2026-11-01 18:59:01 |
| Last checked | 2026-11-16 08:39:39 |
Observed reliability
| 7-day uptime | 97% |
|---|---|
| 24-hour uptime | — |
| Handshake success | 98% |
| Latency p50 / p95 | 1678 / 3466 ms |
| Last successful check | 2026-11-16 08:39:39 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (33)
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; foget_endpoint_history— agentscan: presence and price history of ONE indexed record. To find records use query_agent_index. Returns the record plus its dated presenexport_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. Returnbulk_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_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 pasbenchmark_x402_price— agentscan: Benchmark an x402 endpoint price against listed prices for similar endpoints. For a pay or avoid verdict use check_x402_endpoint_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_sex402_seller_report— agentscan: x402 seller report: lint, price position, buyer preflight and Bazaar demand for one endpoint. For category demand history, 10 peex402_listing_audit— agentscan: x402 listing review: lint, category demand history, 10 closest peers and ranked fixes. For a cheaper report without peers or histget_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 endptest_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 usx402_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_pax402_receipt_check— chainpeek: Check an x402 receipt: did this transaction hash pay that amount to that address. Returns the token transfer in one transaction (x402_settlement_reconcile— chainpeek: Reconcile an x402 seller's request log with its USDC settlements on Base. Returns the exceptions between your request log (CSV orx402_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 hox402_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 acheck_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_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_serveget_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 getget_x402_facilitator_changes— agentscan: Compare x402 facilitator support and changes since a date. Input: optional `since`; GET query or POST JSON. Observations, not setidentify_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 paranalyze_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_usaudit_web_logs— agentscan: Review supplied web logs. For AI client classes and robots rules use analyze_agent_traffic. Returns referrer cohorts, self-referrpreflight_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 checkaudit_mcp_listings— agentscan: Review MCP Registry and Smithery listings. Returns official MCP Registry and bounded Smithery listings versus live tools, transpocheck_apify_store_rules— agentscan: Check Apify Actors against Store publishing rules. For an MCP server repo against an awesome list use preflight_mcp_listing; forget_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 uptget_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 3check_agent_readiness— sitepeek: Returns 0-100 scores for llms.txt (links checked), robots rules for 16 AI agents, sitemap, schema.org types, OpenAPI, /.well-knowngenerate_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_reaaudit_price_consistency— agentscan: Check an x402 seller's price consistency. Returns a comparison of a seller origin's unpaid 402 amounts with OpenAPI, MCP descriptcreate_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 publget_readback_watch— agentscan: Read-back watch status: state, checks left and the history of verdicts. Returns state, checks left, last verdict and every check'
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-16 08:39:39 | ✓ | ✓ | 2236 ms | 83 | active |
| 2026-11-16 07:39:14 | ✓ | ✗ | 0 ms | 49 | degraded |
| 2026-11-16 05:38:50 | ✓ | ✓ | 2178 ms | 84 | active |
| 2026-11-16 03:38:39 | ✓ | ✓ | 1656 ms | 84 | active |
| 2026-11-16 01:38:38 | ✓ | ✓ | 1586 ms | 84 | active |
| 2026-11-15 23:38:13 | ✓ | ✓ | 1754 ms | 84 | active |
| 2026-11-15 21:38:10 | ✓ | ✓ | 1678 ms | 84 | active |
| 2026-11-15 19:37:56 | ✓ | ✓ | 1541 ms | 84 | active |
| 2026-11-15 17:37:53 | ✓ | ✓ | 1606 ms | 84 | active |
| 2026-11-15 15:37:47 | ✓ | ✓ | 1865 ms | 84 | active |
| 2026-11-15 13:37:18 | ✓ | ✓ | 1673 ms | 84 | active |
| 2026-11-15 11:36:54 | ✓ | ✓ | 1582 ms | 84 | active |
| 2026-11-15 09:36:30 | ✓ | ✓ | 1784 ms | 84 | active |
| 2026-11-15 07:36:28 | ✓ | ✓ | 3580 ms | 84 | active |
| 2026-11-15 05:36:13 | ✓ | ✓ | 1800 ms | 84 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://tanod.dev/mcp/agents") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/tanod-dev-mcp-agents # JSON