
Agent Tools (x402 + MCP + A2A Directory)
- 1 repo stars
- Updated August 6, 2026
- AgentTools-Cloud/AgentToolsCollection
Discover x402 services, MCP servers and A2A agents by intent - agent-tools.cloud directory.
About
Discover x402 services, MCP servers and A2A agents by intent - agent-tools.cloud directory. Exposes 11 MCP tools including io.github.AgentTools-Cloud/agent-tools-mcp, smoke. Covers setup, configuration, and when-to-use guidance from upstream documentation for agent-tools (x402 + MCP + A2A directory). Install via Claude Desktop, Cursor, or any MCP-compatible client using the upstream server manifest.
- `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
- `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 (x402 + MCP + A2A Directory) by the numbers
- Exposes 11 verified tools (MCP introspection)
- Data as of Aug 10, 2026 (Skillselion catalog sync)
claude mcp add agent-tools-mcp -- uvx agent-tools-mcpAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| repo stars | ★ 1 |
|---|---|
| Package | agent-tools-mcp |
| Transport | STDIO, HTTP |
| Auth | None |
| Tools | 11 |
| Last updated | August 6, 2026 |
| Repository | AgentTools-Cloud/AgentToolsCollection ↗ |
How do I connect agent-tools (x402 + MCP + A2A directory) to my MCP client?
Discover x402 services, MCP servers and A2A agents by intent - agent-tools.cloud directory.
Who is it for?
Teams wiring agent-tools (x402 + MCP + A2A directory) into Claude, Cursor, or custom agents for developer tools.
Skip if: Skip when you need a non-MCP SDK or hosted API without stdio/SSE transport.
What you get
Working agent-tools (x402 + MCP + A2A directory) MCP server with verified tool registration and client config.
- Shortlist of candidate x402 services, MCP servers, or A2A agents
- Directory-backed metadata to compare next steps in validate and build
- Reduced research time before installing specific integrations
By the numbers
- [object Object]
agent-tools (x402 + MCP + A2A directory) capabilities & compatibility
- Capabilities
- agent tools (x402 + mcp + a2a directory) mcp too · agent tools (x402 + mcp + a2a directory) client · agent tools (x402 + mcp + a2a directory) agent w
- Use cases
- orchestration
- Runs
- Remote server
Tools 11
Public tool metadata - what this server can do for an agent.
search7 paramsFind x402 / MCP services matching an intent or filter set. Two usage modes (agents pick whichever fits): A. Natural-language: `search(intent="fetch tweets for @user")` B. Pure browse: `search(has_mcp=True, category="defi", top_k=10)` At least one of `intent`, `category`, `chain`, `has_mcp`, `min_confidence` must be supplied — otherwise the call is rejected (we won't dump 2300+ rows). Results are ranked by: (health=ok AND tx_30d>0) → health=ok → has-quality-signal → confidence → tx_30d → recency. So the highest-quality real-traffic services appear first. Each item includes (when available): - confidence : 0.0–1.0 x402scan quality score. - tx_30d : 30-day x402 payment count (proxy for real usage). - match_snippet : FTS snippet showing where `intent` hit ([[token]]). - match_reason : list[str] of human-readable ranking signals. - mcp_url : populated when the servic
intenttop_kintegermax_price_usdcategorychainmin_confidencehas_mcpboolean
ask_services9 paramsAsk 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.
intentstringrequiredtop_kintegermax_price_usdcategorychainrequire_healthybooleanmin_confidencehas_mcpbooleanuse_llmboolean
get1 paramGet 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.
slugstringrequired
list_categoriesList all available service categories in the directory.
statsHigh-level stats about the directory: total services, healthy count, sources.
search_mcp_servers4 paramsFind 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.
intenttop_kintegerchainrequire_healthyboolean
get_mcp_server1 paramGet the full card for one MCP server by slug.
slugstringrequired
search_a2a_agents3 paramsFind 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.
intenttop_kintegerx402_onlyboolean
search_resources3 paramsUnified 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).
intentprotocoltop_kinteger
register9 paramsSelf-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 contact@agent-tools.cloud 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 hostnam
urlstringrequirednamedescriptionmcp_urlcategorychainsprice_min_usdcprice_max_usdccontact
scan_mcp_safety4 paramsCheck 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, ADD it to the directory, and return the fresh verdict (so the next caller gets the rule verdict instantly from cache). 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(...DownloadStri
endpoint_urlstringrequirednamestringdescriptionstringtools_textstring
README.md
mcpserver — agent-tools.cloud directory + MCP discovery
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
| Path | Auth | Purpose |
|---|---|---|
GET / (host = agent-tools.cloud) |
free | Directory site (search / browse) |
GET /api/v1/search |
free | Faceted service search |
POST /api/v1/ask |
free, rate-limited | LLM-ranked recommendations grounded in directory candidates |
GET /api/v1/services/{slug} |
free | Service card with payment, call and quality metadata |
GET /api/v1/categories, /api/v1/stats |
free | Directory facets and aggregate stats |
POST /api/v1/submit |
free, rate-limited | Pending service submission with dedupe |
POST /mcp-discovery/ |
free | MCP streamable-http discovery server |
POST /a2a |
free | A2A JSON-RPC agent (message/send): directory search + MCP safety scan |
GET /healthz |
free | Liveness |
GET /v1/models |
free | Upstream model listing (read-only) |
GET /.well-known/agent-tools.json |
free | Agent discovery manifest |
GET /.well-known/x402 |
free | x402 v0.4 self-description (free-only) |
GET /.well-known/mcp.json |
free | MCP 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
Currently deployed on latex-tools behind nginx (vhost: agent-tools.cloud).
cd /opt/mcpserver
sudo git pull
sudo 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 crawleragent-tools-health.{service,timer}— endpoint health checks
Config
See .env.example. Required:
UPSTREAM_BASE_URL/UPSTREAM_API_KEY— used by/v1/modelsAGENT_TOOLS_ASK_BASE_URL/AGENT_TOOLS_ASK_API_KEY/AGENT_TOOLS_ASK_MODEL— LLM backend for/api/v1/askAGENT_TOOLS_SAFETY_BASE_URL/AGENT_TOOLS_SAFETY_API_KEY/AGENT_TOOLS_SAFETY_MODEL— optional override for thescan_mcp_safetyadvisory LLM (falls back to theAGENT_TOOLS_ASK_*backend)AGENT_TOOLS_DB_PATH— SQLite path for the directoryAGENT_TOOLS_ASK_RATE_LIMIT_PER_MINUTE/AGENT_TOOLS_ASK_RATE_LIMIT_PER_DAY— public ask abuse limitsMETRICS_BEARER_TOKEN— optional remote access token for/metrics; without it metrics are local-only
Smoke test
# Liveness
curl https://agent-tools.cloud/healthz
# Directory stats
curl https://agent-tools.cloud/api/v1/stats
# Intent-level service recommendation
curl -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 card
curl https://agent-tools.cloud/api/v1/services/weather-hugen-tokyo-scan
# MCP discovery handshake
curl -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 -> 404
curl -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.
Recommended MCP Servers
How it compares
Multi-protocol discovery directory MCP, not a single-domain API integration server.
FAQ
What does Agent Tools (x402 + MCP + A2A Directory) do?
Discover x402 services, MCP servers and A2A agents by intent - agent-tools.cloud directory.
When should I use Agent Tools (x402 + MCP + A2A Directory)?
User asks about Agent Tools (x402 + MCP + A2A Directory) mcp, discover x402 services, mcp servers and a2a agents by intent - agent-t.
Is this MCP server safe to install?
Review the Security Audits panel on this page before installing in production.