# agent-tools (x402 + MCP + A2A directory) (remote · agent-tools.cloud)

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

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `agent-tools.cloud`: 65/100 (this document), [markdown](https://verifymcp.io/servers/cloud-agent-tools-agent-tools-mcp/mcp-discovery.md), [page](https://verifymcp.io/servers/cloud-agent-tools-agent-tools-mcp/mcp-discovery)
- pypi · `agent-tools-mcp`: 68/100, [markdown](https://verifymcp.io/servers/cloud-agent-tools-agent-tools-mcp/agent-tools-mcp.md), [page](https://verifymcp.io/servers/cloud-agent-tools-agent-tools-mcp/agent-tools-mcp)

## Channel facts

- Endpoint: `https://agent-tools.cloud/mcp-discovery/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (verify_service_url).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 5308 tokens (~230/item across 23 items; 23 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the agent-tools (x402 + MCP + A2A directory) server?

agent-tools (x402 + MCP + A2A directory) is a hosted endpoint at https://agent-tools.cloud/mcp-discovery/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "cloud-agent-tools-agent-tools-mcp": {
      "url": "https://agent-tools.cloud/mcp-discovery/"
    }
  }
}
```

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

```bash
openclaw mcp add cloud-agent-tools-agent-tools-mcp --url 'https://agent-tools.cloud/mcp-discovery/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cloud-agent-tools-agent-tools-mcp:
    url: "https://agent-tools.cloud/mcp-discovery/"
```

### Netclaw

```json
{
  "McpServers": {
    "cloud-agent-tools-agent-tools-mcp": {
      "Transport": "http",
      "Url": "https://agent-tools.cloud/mcp-discovery/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloud-agent-tools-agent-tools-mcp -t streamable-http -u 'https://agent-tools.cloud/mcp-discovery/'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 62, 0)

- [security] Tool “search_mcp_servers” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “search_mcp_servers” added an optional parameter “scope”

### 2026-11-14 (score 62)

First indexed and scored.

## MCP tools (23)

### `search` (~691 tokens)

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.…

Input parameters:

- `category`: Filter (see `list_categories`).
- `chain`: "base", "polygon", "solana", "arbitrum", ...
- `has_mcp` (boolean): 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.
- `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.
- `max_price_usd`: Upper bound on per-call price in USD.
- `min_confidence`: Minimum confidence (0.0–1.0). 0.8+ keeps only services x402scan rates as high-quality.
- `top_k` (integer): Max services to return (default 5, hard cap 25).

### `ask_services` (~359 tokens)

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.

Input parameters:

- `category`: Optional directory category filter.
- `chain`: Optional payment network filter, e.g. "base" or "solana".
- `has_mcp` (boolean): When true, only consider services with MCP endpoints.
- `intent` (string, required): Natural-language job the agent wants to accomplish.
- `max_price_usd`: Optional per-call budget cap.
- `min_confidence`: Optional x402scan quality floor (0.0-1.0).
- `require_healthy` (boolean): When true, only consider services marked health=ok.
- `top_k` (integer): Max recommendations to return (1-10).
- `use_llm` (boolean): Set false for deterministic retrieval-only fallback.

### `get` (~101 tokens)

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.

Input parameters:

- `slug` (string, required): Service slug as returned by `search` items.

### `list_categories` (~17 tokens)

List all available service categories in the directory.

### `stats` (~45 tokens)

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).

### `get_methodology` (~61 tokens)

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.

### `list_articles` (~115 tokens)

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.

Input parameters:

- `page` (integer): Page number, 20 articles per page.
- `query` (string): Optional words to match in title, summary or body.
- `tag` (string): Optional tag to filter by.

### `get_article` (~54 tokens)

Read one published Blog article: metadata plus the full Markdown body.

    Args:
        slug: The article slug, as returned by list_articles.

Input parameters:

- `slug` (string, required): The article slug, as returned by list_articles.

### `directory_stats` (~406 tokens)

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.

Input parameters:

- `api_key`: Optional account key (free from create_api_key) for complete lists when you cannot send the Authorization header.
- `month`: Optional "YYYY-MM" to get that monthly report instead.
- `topic`: Optional topic word (e.g. "payment", "weather") to get that topic instead: supply per protocol, readiness, best listings, searches.
- `view` (string): "all", "mcp", "x402" or "a2a" to scope the figures to one protocol.

### `search_mcp_servers` (~297 tokens)

Find MCP servers in the directory.

    Searches the standalone MCP directory (official MCP Registry, Smithery,
    Agenstry and other crawled sources) 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.
        scope: "remote" (default) = servers with an endpoint you can call now;
            "code" = code-only servers (repository / package you install and
            run yourself, no remote endpoint); "all" = both.

Input parameters:

- `chain`: Optional payment-network filter for paid MCP servers.
- `intent`: Natural-language description of the tool/capability needed.
- `require_healthy` (boolean): When true, only return servers marked health=ok.
- `scope` (string): "remote" (default) = servers with an endpoint you can call now; "code" = code-only servers (repository / package you install and run yourself, no remote endpoint); "all" = both.
- `top_k` (integer): Max servers to return (1-20).

### `get_mcp_server` (~62 tokens)

Get the full card for one MCP server by slug.

    Args:
        slug: MCP server slug as returned by `search_mcp_servers` items.

Input parameters:

- `slug` (string, required): MCP server slug as returned by `search_mcp_servers` items.

### `search_a2a_agents` (~118 tokens)

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.

Input parameters:

- `intent`: Natural-language description of the task to delegate.
- `top_k` (integer): Max agents to return (1-20).
- `x402_only` (boolean): When true, only return agents that advertise x402 payment.

### `search_resources` (~112 tokens)

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).

Input parameters:

- `intent`: Natural-language query.
- `protocol`: Optional filter: "x402", "mcp" or "a2a".
- `top_k` (integer): Max resources to return (1-50).

### `register` (~541 tokens)

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 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 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.

Input parameters:

- `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"]).
- `contact`: Optional email / handle the directory team can reach you on for clarifications.
- `description`: One-paragraph description (max ~2000 chars).
- `mcp_url`: If the service speaks MCP, its streamable-http endpoint.
- `name`: Human-friendly name. Defaults to the URL hostname.
- `price_max_usdc`: Upper bound of per-call price in USDC.
- `price_min_usdc`: Lower bound of per-call price in USDC.
- `url` (string, required): Public HTTPS URL of the service (the x402-payable endpoint or its homepage). Required.

### `scan_mcp_safety` (~841 tokens)

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…

Input parameters:

- `description` (string): Optional description / README blurb (scanned when new).
- `endpoint_url` (string, required): The MCP server's streamable-http URL (required). This is the identity we look up / index by.
- `name` (string): Optional advertised name (used when the server is new and gets added; falls back to the URL host).
- `tools_text` (string): Optional tool names + descriptions; used only if the live probe cannot fetch the server's tools/list.

### `claim_service_url` (~117 tokens)

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.

Input parameters:

- `method`: Optional proof method; otherwise inferred from the complete URL.
- `url` (string, required): Complete public HTTPS service URL, including its query when present.

### `verify_service_url` (~109 tokens)

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.

Input parameters:

- `claim_id` (integer, required): Claim id returned by claim_service_url.
- `token` (string, required): The issued token after publishing it in the instructed location.

### `get_owned_listing` (~95 tokens)

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.

Input parameters:

- `kind` (string, required): Listing type: x402, mcp, or a2a.
- `slug` (string, required): Slug from the verified claim's listings or directory search.

### `edit_owned_listing` (~152 tokens)

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.

Input parameters:

- `fields` (object, required): Editable fields to change; measured fields are rejected.
- `kind` (string, required): Listing type: x402, mcp, or a2a.
- `slug` (string, required): Slug of the listing you are authorized to edit.

### `create_api_key` (~196 tokens)

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.

Input parameters:

- `name`: Optional label to recognise the key later, e.g. your agent name.

### `prepare_paid_verification` (~240 tokens)

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 }.

Input parameters:

- `api_key`: Optional if the Authorization header is sent.
- `payer` (string, required): 0x address of the wallet that will sign and pay.
- `slug` (string, required): Service slug from `search` / `get`.

### `execute_paid_verification` (~167 tokens)

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.

Input parameters:

- `api_key`: Optional if the Authorization header is sent.
- `id` (string, required): `id` returned by `prepare_paid_verification`.
- `signature` (string, required): 0x EIP-712 signature of its `typed_data` by the payer.

### `get_paid_verification` (~63 tokens)

Read one of your own paid verifications.

    Args:
        id: Verification id.
        api_key: Optional if the Authorization header is sent.

Input parameters:

- `api_key`: Optional if the Authorization header is sent.
- `id` (string, required): Verification id.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cloud-agent-tools-agent-tools-mcp/mcp-discovery#diagnostics

## Score history

- 2026-11-21: 65
- 2026-11-20: 65
- 2026-11-19: 64
- 2026-11-18: 64
- 2026-11-17: 63
- 2026-11-16: 63
- 2026-11-15: 62
- 2026-11-14: 62

## Common questions

### What is the agent-tools (x402 + MCP + A2A directory) server?

agent-tools (x402 + MCP + A2A directory) is listed in the public MCP registry as cloud.agent-tools/agent-tools-mcp. Discover x402 services, MCP servers and A2A agents by intent, agent-tools.cloud directory. This page covers its hosted endpoint (https://agent-tools.cloud/mcp-discovery/).

### Is the agent-tools (x402 + MCP + A2A directory) server safe to use?

agent-tools (x402 + MCP + A2A directory) scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the agent-tools (x402 + MCP + A2A directory) server expose?

agent-tools (x402 + MCP + A2A directory) exposes 23 tools: search, ask_services, get, list_categories, stats, and 18 more. Their descriptions and schemas cost roughly 4,959 tokens of context every time the server is loaded.

### Does the agent-tools (x402 + MCP + A2A directory) server require authentication?

No. We connected to agent-tools (x402 + MCP + A2A directory) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the agent-tools (x402 + MCP + A2A directory) server still maintained?

agent-tools (x402 + MCP + A2A directory) is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the agent-tools (x402 + MCP + A2A directory) server?

VerifyMCP ran 13 checks on agent-tools (x402 + MCP + A2A directory), covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://agent-tools.cloud/mcp-discovery/
- Repository: https://github.com/AgentTools-Cloud/AgentToolsCollection
- Website: https://agent-tools.cloud/
- Changelog RSS feed: https://verifymcp.io/servers/cloud-agent-tools-agent-tools-mcp/mcp-discovery.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloud-agent-tools-agent-tools-mcp/mcp-discovery/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloud-agent-tools-agent-tools-mcp/mcp-discovery.json
- HTML version of this page: https://verifymcp.io/servers/cloud-agent-tools-agent-tools-mcp/mcp-discovery
