Is the Whatagentsbuy MCP server down?

mcp-registry/com.whatagentsbuy/whatagentsbuy · v1.1.0

healthy
Last checked 2026-10-26 16:39 UTC · handshake 309ms

As of 2026-10-26 16:39 UTC, the Whatagentsbuy MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 8 minutes.

uptime (30d checks)
100%
checks observed
4,926
outages (90d)
2
tools
7

Independent measured reviews of x402 API sellers: pre-payment verdicts and accuracy grades.

Point your MCP client at this streamable-http endpoint: https://whatagentsbuy.com/mcp

Agent-readiness: C (77/100)

C (77/100): 0 error(s), 3 warning(s) across 7 tool(s); ~1,440 tokens of tool definitions.
Scores higher than 13% of 15,769 MCP servers Glimind has audited.
Its tool list costs an agent ~1,440 tokens per session — lighter than 60% of servers.
75 → 77 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions80
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

7 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: check_before_paying, find_api, known_payment_traps, look_up_seller, market_size and 2 more

3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: known_payment_traps, look_up_seller, rank_sellers

2 parameter(s) across 1 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: rank_sellers

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.whatagentsbuy%2Fwhatagentsbuy/fixes

check_before_paying 1 change 
{
  "name": "check_before_paying",
  "description": "USE WHEN your agent is about to pay an x402 API and you want to know if it is safe and worth it. Returns one verdict for a URL or host in the `verdict` field (gate on that; `light` is the same decision as a colour, for display): CLEAR (nothing alarming), HOLD (pay but resolve the reasons), ABORT (do not pay without checking the live 402), UNRATED (no data). Also returns a confidence tier (verified = a payment to this seller settled AND produced a gradeable result, checked = free probe measured) ",
  "inputSchema": {
    "type": "object",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "description": "Full URL or bare hostname, e.g. https://blockrun.ai/api/v1/exa/search or blockrun.ai"
      },
      "detail": {
        "type": "boolean",
        "description": "Include the full payment-safety detail (live-402 honesty, demand shape, grades). Default false."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "The one check before your agent pays"
}
find_api 1 change 
{
  "name": "find_api",
  "description": "USE WHEN you need an API that does something and want payable options. Searches the whole x402 market for what you describe and returns a ranked, pre-vetted shortlist, proven-accurate sellers first, then payment-safety, then price. Covers every reachable endpoint, not just ones we have bought from. Next step: check_before_paying on your pick, then read the payTo from the live 402 and sign against it.",
  "inputSchema": {
    "type": "object",
    "required": [
      "task"
    ],
    "properties": {
      "task": {
        "type": "string",
        "description": "What you need, in words or keywords, e.g. 'validate an email address', 'BTC price', 'geocode an address'"
      },
      "limit": {
        "type": "integer",
        "description": "How many results (default 8, max 25)"
      },
      "max_price_usdc": {
        "type": "number",
        "description": "Optional ceiling on the per-call price in USDC"
      },
      "min_reliability": {
        "type": "integer",
        "description": "Optional floor on the reliability score 0-100 (default 0 = no floor; the whole reachable market)"
      },
      "allowed_verdicts": {
        "type": "array",
        "items": {
          "enum": [
            "CLEAR",
            "HOLD",
            "ABORT",
            "UNRATED"
          ],
          "type": "string"
        },
        "description": "Optional policy filter: only return sellers whose current preflight verdict is in this list, e.g. [\"CLEAR\"]. Default: no filter, every result carries its verdict so you can decide."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Find a payable API for a task"
}
known_payment_traps 1 change 
{
  "name": "known_payment_traps",
  "description": "USE WHEN writing payment code, or before trusting an unfamiliar seller. The field notes: each is a specific way an agent paying an API loses money or is misled, what it cost to learn, and what to do instead. (Formerly named list_traps.)",
  "inputSchema": {
    "type": "object",
    "properties": {
      "query": {
        "type": "string",
        "description": "Optional filter, e.g. 'price', 'delivery'"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "How agents lose money paying APIs"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.whatagentsbuy/whatagentsbuy"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.whatagentsbuy/whatagentsbuy"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.whatagentsbuy%2Fwhatagentsbuy.svg)](https://glimind.com/server/mcp-registry%2Fcom.whatagentsbuy%2Fwhatagentsbuy?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fcom.whatagentsbuy%2Fwhatagentsbuy?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.whatagentsbuy%2Fwhatagentsbuy.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.whatagentsbuy%2Fwhatagentsbuy.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.whatagentsbuy%2Fwhatagentsbuy?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:afb4660424acd29e…, first seen 2026-10-17, included at leaf 3707 of 74,160. Version history · verify what your client received.

Tools (7)

Compare: most reliable security servers · most reliable search servers · most reliable knowledge servers · most reliable data servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Whatagentsbuy MCP server down right now?

As of 2026-10-26 16:39 UTC, the Whatagentsbuy MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 8 minutes.

How many tools does Whatagentsbuy MCP server provide?

Whatagentsbuy MCP server advertises 7 tools, including check_before_paying, find_api, known_payment_traps, look_up_seller, market_size.

How do I install Whatagentsbuy MCP server?

Point your MCP client at this streamable-http endpoint: https://whatagentsbuy.com/mcp

Is the Whatagentsbuy MCP server safe to connect to an AI agent?

Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Whatagentsbuy MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve