agent-tools (x402 + MCP + A2A directory)

io.github.AgentTools-CloudPublished by GitHub account AgentTools-Cloudv0.4.0Updated Oct 29, 2026

Discover x402 services, MCP servers and A2A agents by intent — agent-tools.cloud directory.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & MonitoringAI & ML

Overview

AI-generated overview

Searches the agent-tools.cloud directory of x402-paid services, MCP servers and A2A agents, and screens MCP endpoints for safety.

What you can do
  • Search and rank directory entries by natural-language intent, category, chain, price or MCP availability, with LLM-ranked recommendations and fallback to plain search
  • Read service cards with payment, call, quality and resource details, plus ready-to-use MCP/x402 call hints
  • Browse the taxonomy and directory statistics
  • Find MCP servers and A2A agents, or search across all three resource types at once
  • Scan an MCP server endpoint for malware and prompt-injection lures, and self-register a service in the directory
  • Quote, execute and read back a sponsored paid verification of an x402 service
When to use it
Useful when an assistant needs to find a paid or free API, MCP server or A2A agent for a task, compare candidates before calling one, or check an unfamiliar MCP endpoint for tool-poisoning and injection patterns before connecting.
Requirements
Remote streamable-http endpoint at agent-tools.cloud, or the agent-tools-mcp PyPI package over stdio (core search tools only). No authentication is declared for the discovery tools; the paid verification tools need an API key, and the hosted deployment needs its own upstream and LLM backend settings.
Before you install
The paid verification flow spends real funds from your own wallet in Base USDC (up to about $1 per service) and requires signing EIP-712 typed data; the server states it never signs or holds funds. Registration is auto-approved without human review once x402 payment support is proven. Safety verdicts are rule-based and advisory, and unknown endpoints are probed live and added to the directory. Queries and endpoint details are sent to a third-party service and its LLM backend.

Installation

In SourceWeft

  1. Open agent-tools (x402 + MCP + A2A directory) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.AgentTools-Cloud%2Fagent-tools-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "agent-tools-x402-a2a-directory": {
      "type": "http",
      "url": "https://agent-tools.cloud/mcp-discovery/"
    }
  }
}

README

mcpserver — agent-tools.cloud directory + MCP discovery

[smithery badge]

The server that powers agent-tools.cloud — an open directory of x402 paid services with a free MCP discovery endpoint. Also listed on Smithery.

Note (2026-05-25): the previously hosted paid Qwen3.6 relay and the paid vertical endpoints (signal / onchain / defi / portfolio) were retired after 30 days of zero external conversions. This repository now serves the directory site and the free MCP discovery server only.

What this serves today

PathAuthPurpose
GET / (host = agent-tools.cloud)freeDirectory site (search / browse)
GET /api/v1/searchfreeFaceted service search
POST /api/v1/askfree, rate-limitedLLM-ranked recommendations grounded in directory candidates
GET /api/v1/services/{slug}freeService card with payment, call and quality metadata
GET /api/v1/categories, /api/v1/statsfreeDirectory facets and aggregate stats
POST /api/v1/submitfree, rate-limitedPending service submission with dedupe
POST /mcp-discovery/freeMCP streamable-http discovery server
POST /a2afreeA2A JSON-RPC agent (message/send): directory search + MCP safety scan
GET /healthzfreeLiveness
GET /v1/modelsfreeUpstream model listing (read-only)
GET /.well-known/agent-tools.jsonfreeAgent discovery manifest
GET /.well-known/x402freex402 v0.4 self-description (free-only)
GET /.well-known/mcp.jsonfreeMCP self-description

The MCP discovery server is also published as a standalone PyPI package: agent-tools-mcp (repo).

MCP discovery tools

search(intent, top_k=5, category=None, max_price_usd=None, has_mcp=None)ask_services(intent, top_k=5, category=None, max_price_usd=None, use_llm=True)get(slug)list_categories()stats()search_mcp_servers(intent, top_k=5, chain=None, require_healthy=False)get_mcp_server(slug)search_a2a_agents(intent, top_k=5, x402_only=False)search_resources(intent, protocol=None, top_k=10)scan_mcp_safety(endpoint_url, name="", description="", tools_text="")register(url, name=None, description=None, mcp_url=None, category=None)

search accepts natural-language intent and ranks by FTS5 + popularity + health. Each result carries a match_reason and a confidence score. ask_services uses the same retrieval-first / LLM-rerank flow as /api/v1/ask.

scan_mcp_safety vets an MCP server (by endpoint URL) for malware / prompt-injection lures before you connect: an already-indexed server returns our latest stored verdict, an unknown one is probed live, scanned, and added to the directory. The verdict comes from deterministic static rules (no code execution) over the server's advertised name + description + tool docs. Rules cover pipe-to-shell / base64-eval / PowerShell install cradles, bare-IP payload hosts, prompt-injection phrasing, and MCP tool-poisoning coercion — "always call this tool first", "before using any other tool you must…", hidden <IMPORTANT> instructions, "list all API keys / include secrets in your response", and coercion to read & forward .key/.pem/.ssh/.env files. Source-code-oriented rules (SQL/command/code injection) are intentionally not applied to natural-language descriptions to avoid false positives. Each live call also runs a frontier-LLM second opinion as an advisory dimension. It is also exposed as an A2A skill on POST /a2a. The hosted server carries the full tool set above; the stdio agent-tools-mcp PyPI package ships the core search tools only.

Deploy

Production runs behind nginx (vhost: agent-tools.cloud).

bash
cd <install-dir>sudo git pullsudo systemctl restart mcpserver

systemd units live in deploy/:

  • mcpserver.service — the ASGI app (uvicorn, 127.0.0.1:9100)
  • agent-tools-crawl.{service,timer} — 6h directory crawler
  • agent-tools-health.{service,timer} — endpoint health checks

Config

See .env.example. Required:

  • UPSTREAM_BASE_URL / UPSTREAM_API_KEY — used by /v1/models
  • AGENT_TOOLS_ASK_BASE_URL / AGENT_TOOLS_ASK_API_KEY / AGENT_TOOLS_ASK_MODEL — LLM backend for /api/v1/ask
  • AGENT_TOOLS_SAFETY_BASE_URL / AGENT_TOOLS_SAFETY_API_KEY / AGENT_TOOLS_SAFETY_MODEL — optional override for the scan_mcp_safety advisory LLM (falls back to the AGENT_TOOLS_ASK_* backend)
  • AGENT_TOOLS_DB_PATH — SQLite path for the directory
  • AGENT_TOOLS_ASK_RATE_LIMIT_PER_MINUTE / AGENT_TOOLS_ASK_RATE_LIMIT_PER_DAY — public ask abuse limits
  • METRICS_BEARER_TOKEN — optional remote access token for /metrics; without it metrics are local-only

Smoke test

bash
# Livenesscurl https://agent-tools.cloud/healthz
# Directory statscurl https://agent-tools.cloud/api/v1/stats
# Intent-level service recommendationcurl -s -X POST https://agent-tools.cloud/api/v1/ask \  -H 'content-type: application/json' \  -d '{"query":"find a weather API that accepts x402","limit":2}'
# Service cardcurl https://agent-tools.cloud/api/v1/services/weather-hugen-tokyo-scan
# MCP discovery handshakecurl -s -X POST https://agent-tools.cloud/mcp-discovery/ \  -H 'content-type: application/json' \  -H 'accept: application/json, text/event-stream' \  -d '{"jsonrpc":"2.0","id":1,"method":"initialize",       "params":{"protocolVersion":"2025-06-18","capabilities":{},                 "clientInfo":{"name":"smoke","version":"1"}}}'
# Retired paid path -> 404curl -s -o /dev/null -w '%{http_code}\n' -X POST \  https://agent-tools.cloud/v1/chat/completions \  -H 'content-type: application/json' \  -d '{"model":"Qwen/Qwen3.6-35B-A3B","messages":[{"role":"user","content":"hi"}]}'# => 404

License

The agent-tools.cloud server and directory code in this repository is licensed under the PolyForm Noncommercial License 1.0.0 — you may use, modify, and share it for any noncommercial purpose; commercial use is not permitted.

The standalone MCP client package in agent-tools-mcp/ (published to PyPI as agent-tools-mcp) is licensed separately under Apache-2.0, so any agent — including commercial ones — can install and call the hosted service freely.

Using the hosted service at agent-tools.cloud is governed by its terms of service, not this code license.

Source: README.md at commit 98c1ee6

Tools

14

ask_services

Ask for the best x402/MCP services for an agent intent. This is the high-level discovery tool: it retrieves candidates from the directory, asks the configured backend LLM to rank only those candidates, and returns service cards for the selected recommendations. If the LLM is unavailable, it falls back to the directory ranker. Args: intent: Natural-language job the agent wants to accomplish. top_k: Max recommendations to return (1-10). max_price_usd: Optional per-call budget cap. category: Optional directory category filter. chain: Optional payment network filter, e.g. "base" or "solana". require_healthy: When true, only consider services marked health=ok. min_confidence: Optional x402scan quality floor (0.0-1.0). has_mcp: When true, only consider services with MCP endpoints. use_llm: Set false for deterministic retrieval-only fallback.

Parameterschaintop_kintentrequiredhas_mcpuse_llmcategorymax_price_usdmin_confidencerequire_healthy

get

Get full details + ready-to-paste call template for a service. Returns the service card with payment, call, quality, resource samples, and ready-to-use MCP/x402 call hints. Use this after `search` or `ask_services` before paying/calling an external service. Args: slug: Service slug as returned by `search` items.

Parametersslugrequired

list_categories

List all available service categories in the directory.

Takes no parameters.

stats

High-level stats about the directory: total services, healthy count, sources.

Takes no parameters.

search_mcp_servers

Find MCP servers in the directory. Searches the standalone MCP directory (PulseMCP / official MCP registry import) unioned with x402 services that also expose an MCP endpoint. Returns normalised entries with a ready-to-use streamable-http `call_hint.mcp.url`. Args: intent: Natural-language description of the tool/capability needed. top_k: Max servers to return (1-20). chain: Optional payment-network filter for paid MCP servers. require_healthy: When true, only return servers marked health=ok.

Parameterschaintop_kintentrequire_healthy

get_mcp_server

Get the full card for one MCP server by slug.

Parametersslugrequired

search_a2a_agents

Find A2A agents you can delegate a task to. Args: intent: Natural-language description of the task to delegate. top_k: Max agents to return (1-20). x402_only: When true, only return agents that advertise x402 payment.

Parameterstop_kintentx402_only

search_resources

Unified search across x402 services, MCP servers and A2A agents. Args: intent: Natural-language query. protocol: Optional filter: "x402", "mcp" or "a2a". top_k: Max resources to return (1-50).

Parameterstop_kintentprotocol

register

Self-register an x402 / MCP service in the agent-tools directory. Service owners and agents may submit new services here. Submissions are auto-reviewed instantly by x402 verification (no human gate): if the URL proves x402 payment support it is listed immediately and shows up in `search`; otherwise it is rejected or retried automatically. Listing is FREE. Dedup: if a service with the same canonical origin (scheme://host) already exists in the directory we return its slug instead of creating a duplicate submission. Same goes for a still-pending submission with the same origin. Rate limit: at most 5 pending submissions per client IP per 24h. Hits beyond that get `{error: rate_limited}` — try again later or email [email protected] for bulk imports. Args: url: Public HTTPS URL of the service (the x402-payable endpoint or its homepage). Required. name: Human-friendly name. Defaults to the URL hostname. description: One-paragraph description (max ~2000 chars). mcp_url: If the service speaks MCP, its streamable-http endpoint. category: Free-form (e.g. "defi", "search", "social"). Use `list_categories` to align with existing taxonomy. chains: Networks the service accepts payment on (e.g. ["base", "solana"]). price_min_usdc: Lower bound of per-call price in USDC. price_max_usdc: Upper bound of per-call price in USDC. contact: Optional email / handle the directory team can reach you on for clarifications.

Parametersurlrequirednamechainscontactmcp_urlcategorydescriptionprice_max_usdcprice_min_usdc

scan_mcp_safety

Check an MCP server for malware / prompt-injection lures by its endpoint URL. Give the server's streamable-http endpoint URL. Two paths: * **Already in the agent-tools directory** → returns our LATEST stored rule verdict. Every indexed server is re-scanned hourly, so you get a consistent, continuously-refreshed answer without re-probing. * **Not yet indexed** → we probe the endpoint live, statically scan its advertised tools + metadata, and return the fresh verdict. It is ADDED to the directory (so the next caller gets the stored verdict instantly) only if it answered or you supplied metadata; documentation hosts such as example.com / *.test / *.invalid are scanned but never listed. Two dimensions are reported. `verdict` is authoritative and comes from deterministic static rules — pure pattern-matching over the *advertised* text only, NO code execution. It flags the social-engineering / RCE tricks listing-spam servers use: * `curl … | bash` and `base64 -d | sh` install lures * `eval "$(curl …)"` / PowerShell `IEX(...DownloadString)` cradles * base64 blobs that decode to a shell command * bare-IP payload hosts and cheap throwaway TLDs * prompt-injection / credential-exfiltration phrasing ("ignore previous instructions", "send your .env / api key") * MCP tool-poisoning coercion — descriptions that hijack an agent's tool-calling ("always call this tool first", "before using any other tool you must…"), hidden `<IMPORTANT>` instructions, "list all API keys / include secrets in your response", and coercion to read & forward `.key`/`.pem`/`.ssh`/`.env` files Source-code-oriented rules (SQL / command / code injection) are deliberately not applied to natural-language descriptions, to avoid false positives. `llm_reference` is an advisory frontier-LLM second opinion over the same text. Because the LLM

Parametersnametools_textdescriptionendpoint_urlrequired

prepare_paid_verification

Quote a sponsored paid verification of an x402 service. You pay the service once from your own wallet (Base USDC, <= $1; funds go to its payTo). Sign the returned `typed_data` (EIP-712), then call `execute_paid_verification` before `valid_before`. We never sign or hold funds. Auth: API key from POST https://agent-tools.cloud/api/v1/keys, as the `Authorization: Bearer` header or `api_key`. Args: slug: Service slug from `search` / `get`. payer: 0x address of the wallet that will sign and pay. api_key: Optional if the Authorization header is sent. Returns: { id, amount_usd, pay_to, valid_before, typed_data, ... } or { error, message }.

Parametersslugrequiredpayerrequiredapi_key

execute_paid_verification

Send the signed payment to the service once and score the result. Aborts without paying if price or recipient changed. Never retried; a timeout returns `indeterminate`. status: succeeded | delivery_failed | payment_rejected | indeterminate. Args: id: `id` returned by `prepare_paid_verification`. signature: 0x EIP-712 signature of its `typed_data` by the payer. api_key: Optional if the Authorization header is sent.

Parametersidrequiredapi_keysignaturerequired

get_paid_verification

Read one of your own paid verifications. Args: id: Verification id. api_key: Optional if the Authorization header is sent.

Parametersidrequiredapi_key

Version history

2
  1. v0.4.0LatestOct 29, 2026
  2. v0.2.0Sep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.