Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

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

claude mcp add --transport http agent-tools-mcp https://agent-tools.cloud/mcp-discovery/

[mcp_servers.agent-tools-mcp]
url = "https://agent-tools.cloud/mcp-discovery/"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "agent-tools-mcp": {
      "type": "remote",
      "url": "https://agent-tools.cloud/mcp-discovery/",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "agent-tools-mcp": {
      "type": "http",
      "url": "https://agent-tools.cloud/mcp-discovery/"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=agent-tools-mcp&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYWdlbnQtdG9vbHMuY2xvdWQvbWNwLWRpc2NvdmVyeS8ifQ%3D%3D"
}

{
  "servers": {
    "agent-tools-mcp": {
      "type": "http",
      "url": "https://agent-tools.cloud/mcp-discovery/"
    }
  }
}

{
  "mcpServers": {
    "agent-tools-mcp": {
      "httpUrl": "https://agent-tools.cloud/mcp-discovery/"
    }
  }
}

extensions:
  "agent-tools-mcp":
    enabled: true
    name: "agent-tools-mcp"
    type: streamable_http
    uri: "https://agent-tools.cloud/mcp-discovery/"
    timeout: 300

Quality 82 / 100new

protocol75 · weight 25

warn
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
n/a
protocol.statelessonly applies to 2026-07-28 servers
pass
protocol.transportstreamable HTTP
n/a
protocol.list_ttlonly applies to 2026-07-28 servers

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene88 · weight 30

pass
tools.descriptionsevery tool has a description
warn
tools.description_length4 tools have descriptions over 1,024 characters, which crowds the context
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations23 of 23 tools declare readOnlyHint or destructiveHint
warn
tools.directory_hints8 of 23 tools declare all four hints; missing: search (destructiveHint, idempotentHint); ask_services (destructiveHint, idempotentHint); get (destructiveHint, idempotentHint); …
pass
tools.token_costabout 7,004 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump
pass
tools.hidden_textno hidden text in tool names, descriptions, schemas or annotations

stabilityn/a · weight 15

n/a
stability.changes, stability.rug_pull, stability.new_linkstool history recorded for 0 of the 7 days needed

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvabledependencies not resolved yet

23 tools, about 7,004 tokens to load them all · tool set 958109d9150a · checked 2026-11-14 07:03 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 96 / 100

provenance85

liveness100

freshness100

hygiene100

+repository +dns-namespace +website +reachable +uptime-100% +updated-0d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Dependencies

[email protected] PyPInot resolved yet; dependencies are read once a day

Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0. The graph is what a clean install of this version resolves today; nothing was installed or run. How it is checked.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://agent-tools.cloud/mcp-discovery/` streamable-http	none	yes	100%	319 ms	2025-11-25	2026-11-14

package	registry	version	runtime	secrets
`agent-tools-mcp`	pypi	0.5.2	–

Tools (23)

`ask_services`read-only	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.
`claim_service_url`	Issue a fresh ownership token for one exact public HTTPS URL. Authenticate in the MCP Authorization: Bearer header. Publishing and verifying the token is required before editing; URL input alone grants no rights. Args: url: Complete public HTTPS service URL, including its query when present. method: Optional proof method; otherwise inferred from the complete URL.
`create_api_key`	Create a free account API key. No sign-up, email or existing key needed. The key is returned once and cannot be recovered. Store it in your secret store; do not print it back to the user or write it to logs. Send it as `Authorization: Bearer <key>` (or the `api_key` argument where offered) to get complete `directory_stats` lists, run paid verifications and claim your own listings. The claim and listing tools read the key only from the Authorization header; without header support use the REST claim API. Shares the HTTP limit of POST /api/v1/keys (a few keys per IP per day). Args: name: Optional label to recognise the key later, e.g. your agent name.
`directory_stats`read-only	Daily statistics on the agent-tool ecosystem as seen by our probes. Args: view: "all", "mcp", "x402" or "a2a" to scope the figures to one protocol. topic: Optional topic word (e.g. "payment", "weather") to get that topic instead: supply per protocol, readiness, best listings, searches. month: Optional "YYYY-MM" to get that monthly report instead. api_key: Optional account key (free from create_api_key) for complete lists when you cannot send the Authorization header. Returns counts (indexed, reachable, protocol-verified, readiness A/B), one finding sentence per topic, key facts (x402 prices and networks, MCP and A2A protocol versions, MCP auth, A2A card signatures, how every listing's latest probe ended), the most searched terms (view "all"), the snapshot time, and links to the full JSON snapshot, the daily CSV, the methodology, the "how many work" page, per-protocol and per-topic pages and the monthly reports. With an account API key (Authorization: Bearer header or `api_key`; free from `create_api_key`) the topic and search lists are complete (10 listings per protocol, up to 100 terms); without one they are shortened.
`edit_owned_listing`destructive	Edit only metadata covered by your verified claim, with the public audit trail. An endpoint change requires verified control of the exact destination or its whole host and clears measurements tied to the old primary endpoint. Args: kind: Listing type: x402, mcp, or a2a. slug: Slug of the listing you are authorized to edit. fields: Editable fields to change; measured fields are rejected.
`execute_paid_verification`destructive	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.
`get`read-only	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.
`get_article`read-only	Read one published Blog article: metadata plus the full Markdown body. Args: slug: The article slug, as returned by list_articles.
`get_mcp_server`read-only	Get the full card for one MCP server by slug. Args: slug: MCP server slug as returned by `search_mcp_servers` items.
`get_methodology`read-only	How every score and statistic on agent-tools.cloud is computed. Returns the quality-score components and grade bands per protocol, the nine readiness criteria with weights, payment-evidence grades, the probing schedule and the definitions behind the daily statistics.
`get_owned_listing`read-only	Read editable metadata for a listing covered by your verified claim. Args: kind: Listing type: x402, mcp, or a2a. slug: Slug from the verified claim's listings or directory search.
`get_paid_verification`read-only	Read one of your own paid verifications. Args: id: Verification id. api_key: Optional if the Authorization header is sent.
`list_articles`read-only	List published Blog articles, newest first (metadata only). Args: query: Optional words to match in title, summary or body. tag: Optional tag to filter by. page: Page number, 20 articles per page. Use get_article(slug) for the full Markdown body.
`list_categories`read-only	List all available service categories in the directory.
`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 }.
`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.
`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 is slow it is computed LIVE on this call only and is never stored (the hourly job never runs it), so it may be null on timeout. It never overrides the rule verdict; when it is more severe than the rules an `advisory` note is attached as a safety-net signal. Security/defense products that merely name these attacks are not flagged. Args: endpoint_url: The MCP server's streamable-http URL (required). This is the identity we look up / index by. name: Optional advertised name (used when the server is new and gets added; falls back to the URL host). description: Optional description / README blurb (scanned when new). tools_text: Optional tool names + descriptions; used only if the live probe cannot fetch the server's tools/list. Returns: { verdict: "clean"\|"suspicious"\|"malicious", score: 0-100, reasons: [{rule, weight, snippet}], llm_reference: {model, verdict, reason, confidence} \| null, advisory: str \| null, slug, name, endpoint_url, source: "stored" (existing) \| "new_scan" (just added), indexed: bool }
`search`read-only	Find 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 service exposes an MCP endpoint (you can call it directly via streamable-http). Agents should prefer items with non-null confidence and tx_30d > 0 unless the user explicitly wants experimental endpoints. Args: intent: What the agent wants to do (English or Chinese). Optional when at least one structured filter is set. Synonym expansion covers twitter↔X↔推特, whale↔巨鲸, price↔价格 etc. top_k: Max services to return (default 5, hard cap 25). max_price_usd: Upper bound on per-call price in USD. category: Filter (see `list_categories`). chain: "base", "polygon", "solana", "arbitrum", ... min_confidence: Minimum confidence (0.0–1.0). 0.8+ keeps only services x402scan rates as high-quality. has_mcp: When true, return only services with a callable MCP endpoint. Use this when the agent wants to chain another MCP server rather than perform raw HTTP+x402.
`search_a2a_agents`read-only	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.
`search_mcp_servers`read-only	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.
`search_resources`read-only	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).
`stats`read-only	High-level stats about the directory: x402 total, healthy count and chains, plus `snapshot`, the daily digest across x402, MCP and A2A (see directory_stats).
`verify_service_url`destructive	Verify public ownership proof for your own exact service URL claim. This reads public proof only. It never calls business tools, requests private service credentials, or grants whole-platform permissions. Args: claim_id: Claim id returned by claim_service_url. token: The issued token after publishing it in the instructed location.

Schemas: list_tools.

Also listed as

1 other active names share this repository: io.github.AgentTools-Cloud/agent-tools-mcp

Similar MCP servers

Official server.json

{
  "name": "cloud.agent-tools/agent-tools-mcp",
  "title": "agent-tools (x402 + MCP + A2A directory)",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://agent-tools.cloud/mcp-discovery/",
      "type": "streamable-http"
    }
  ],
  "version": "0.5.2",
  "packages": [
    {
      "version": "0.5.2",
      "transport": {
        "type": "stdio"
      },
      "identifier": "agent-tools-mcp",
      "registryType": "pypi"
    }
  ],
  "repository": {
    "url": "https://github.com/AgentTools-Cloud/AgentToolsCollection",
    "source": "github"
  },
  "websiteUrl": "https://agent-tools.cloud",
  "description": "Discover x402 services, MCP servers and A2A agents by intent — agent-tools.cloud directory."
}