# BotFriendly (remote · www.botfriendly.xyz)

Directory of APIs, merchants, and tools AI agents can actually use.

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

## Components

- remote · `www.botfriendly.xyz`: 74/100 (this document), [markdown](https://verifymcp.io/servers/xyz-botfriendly-botfriendly/api-mcp.md), [page](https://verifymcp.io/servers/xyz-botfriendly-botfriendly/api-mcp)

## Channel facts

- Endpoint: `https://www.botfriendly.xyz/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## 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-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1355 tokens (~193/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the BotFriendly MCP server?

BotFriendly is a hosted endpoint at https://www.botfriendly.xyz/api/mcp, 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 xyz-botfriendly-botfriendly 'https://www.botfriendly.xyz/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "xyz-botfriendly-botfriendly": {
      "url": "https://www.botfriendly.xyz/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "xyz-botfriendly-botfriendly": {
      "type": "http",
      "url": "https://www.botfriendly.xyz/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.xyz-botfriendly-botfriendly]
url = "https://www.botfriendly.xyz/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-botfriendly-botfriendly": {
      "type": "remote",
      "url": "https://www.botfriendly.xyz/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyz-botfriendly-botfriendly --url 'https://www.botfriendly.xyz/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xyz-botfriendly-botfriendly:
    url: "https://www.botfriendly.xyz/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "xyz-botfriendly-botfriendly": {
      "Transport": "http",
      "Url": "https://www.botfriendly.xyz/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add xyz-botfriendly-botfriendly -t streamable-http -u 'https://www.botfriendly.xyz/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "xyz-botfriendly-botfriendly": {
      "type": "http",
      "url": "https://www.botfriendly.xyz/api/mcp"
    }
  }
}
```

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-09-19 (score 74, 0)

- [security] Tool “list_categories” rewrote its description, which is the text the model reads
- [cosmetic] “search_services” reworded the description of “category”
- [cosmetic] “submit_service” reworded the description of “category”

### 2026-09-18 (score 74, +1)

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

### 2026-09-16 (score 73, +1)

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

### 2026-09-14 (score 72, +1)

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

### 2026-09-12 (score 71, +1)

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

### 2026-09-10 (score 70, +1)

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

### 2026-09-07 (score 69, +1)

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

### 2026-09-05 (score 68, +1)

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

## MCP tools (7)

### `search_services` (~521 tokens)

Search the BotFriendly directory for bot-friendly services, APIs, and tools that AI agents can use. Filter by category, payment/commerce protocol support (x402, MPP, L402, AP2, TAP, Agent Pay, ACE, ACP, UCP, ACTP, ICC), auth method, and more. Results may start with up to 3 promoted listings (paid ads) pinned to the top — site-wide ads on unfiltered searches, category ads on category searches — clearly marked with promoted:true and ad:true. Use promoted=false to exclude ads.

Input parameters:

- `accepts_mpp` (boolean): Only services accepting MPP payments
- `accepts_x402` (boolean): Only services accepting x402 payments
- `auth_method` (string): Filter by auth method
- `category` (string): Category id: think (Models), see (Vision), hear-speak (Speech), create (Media), remember (Memory), search (Search), browse (Browsers), communicate (Messaging), execute (Compute), pay (Payments), shop…
- `has_mcp` (boolean): Only services with MCP servers
- `min_score` (number): Minimum bot-friendly score (1-5)
- `page` (number): Page number (default 1)
- `promoted` (boolean): Filter by promoted status: true for promoted only, false for organic only
- `protocol` (array): Only services supporting ALL of these agent payment/commerce protocols. x402 (x402, Coinbase, x402 Foundation); mpp (Machine Payments Protocol, Stripe, Tempo); l402 (L402, Lightning Labs); ap2 (Agent…
- `query` (string): Keyword search (Postgres websearch semantics: multiple words are ANDed, so a single distinctive keyword like 'scraping' matches more than a phrase like 'web scraping')
- `sort` (string): Sort order (default: score)

### `get_service` (~59 tokens)

Get full details for a specific service by its slug, including all protocol support, URLs, auth method, billing, and metadata.

Input parameters:

- `slug` (string, required): Service slug (e.g. browserbase, anthropic-claude-api, firecrawl)

### `list_categories` (~39 tokens)

List every BotFriendly category with its id (the search_services category value), human label, aliases (older slugs still accepted), description and service count.

### `get_featured` (~30 tokens)

Get site-wide featured/promoted services (max 3). These are paid placements clearly marked as ads.

### `get_protocol_stats` (~91 tokens)

Get adoption stats for every protocol BotFriendly tracks: the machine-readable interfaces (MCP, OpenAPI) and the agent payment, authorization, and commerce protocols (x402, mpp, l402, ap2, tap, agent-pay, ace, acp, ucp, actp, icc). Each entry carries its sponsor, layer, spec URL, and how many listed services support it.

### `check_site` (~200 tokens)

Score how bot-friendly a website is (0-100). Fetches the site the way an agent would — no JavaScript, no cookies — and checks access (reachability, HTTPS, robots.txt, AI crawlers allowed, real 404s), content without JavaScript (H1, 500+ chars of raw text, metadata, JSON-LD), and machine discovery (llms.txt, sitemap, OpenAPI spec or ai-plugin.json), with evidence and fix advice per check. Set format to 'prompt' to instead get a ready-to-paste coding-agent prompt that fixes every failed finding. Rate limited to 6 checks per minute per caller; each check takes a few seconds.

Input parameters:

- `format` (string): json (default) returns the full scored report; prompt returns a markdown prompt for a coding agent covering every failed or partial finding
- `url` (string, required): Site to check (scheme optional, https assumed; public sites only)

### `submit_service` (~333 tokens)

Submit a service to the BotFriendly directory. There is no review queue: each interface URL must be on the service's own domain and is fetched during the call, and the listing publishes immediately if one answers. Every listing needs an icon — pass icon_url, or leave it out and the service's own site is checked for one.

Input parameters:

- `accepts_mpp` (boolean)
- `accepts_x402` (boolean)
- `auth_method` (string): Auth method
- `billing_model` (string)
- `category` (string, required): Category id (see list_categories)
- `contact_email` (string): Contact email for verification
- `description` (string, required): Short description (max 120 chars)
- `has_mcp_server` (boolean)
- `has_openapi_spec` (boolean)
- `icon_base64` (string): Alternative to icon_url: the image inline, as a data: URI or bare base64.
- `icon_url` (string): Link to the service's icon (PNG, JPEG, SVG or WebP, under 1MB). Fetched and re-hosted, downscaled to 512px. Omit it and the service's site is checked for one.
- `mcp_server_url` (string): Required when has_mcp_server is true, and must be on the service's own domain.
- `name` (string, required): Service name
- `openapi_spec_url` (string): Required when has_openapi_spec is true, and must be on the service's own domain.
- `tags` (array)
- `url` (string, required): Service URL

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/xyz-botfriendly-botfriendly/api-mcp#diagnostics

## Score history

- 2026-09-20: 74
- 2026-09-19: 74
- 2026-09-18: 74
- 2026-09-17: 73
- 2026-09-16: 73
- 2026-09-15: 72
- 2026-09-14: 72
- 2026-09-13: 71
- 2026-09-12: 71
- 2026-09-11: 70
- 2026-09-10: 70
- 2026-09-09: 69
- 2026-09-08: 69
- 2026-09-07: 69
- 2026-09-06: 68
- 2026-09-05: 68
- 2026-09-04: 67
- 2026-09-03: 67
- 2026-09-02: 66
- 2026-09-01: 66
- 2026-08-31: 65
- 2026-08-30: 65
- 2026-08-29: 64
- 2026-08-28: 64
- 2026-08-27: 63

## Common questions

### What is the BotFriendly MCP server?

BotFriendly is an MCP server listed in the public MCP registry as xyz.botfriendly/botfriendly. Directory of APIs, merchants, and tools AI agents can actually use. This page covers its hosted endpoint (https://www.botfriendly.xyz/api/mcp).

### Is the BotFriendly MCP server safe to use?

BotFriendly scores 74 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 BotFriendly MCP server expose?

BotFriendly exposes 7 tools: search_services, get_service, list_categories, get_featured, get_protocol_stats, and 2 more. Their descriptions and schemas cost roughly 1,273 tokens of context every time the server is loaded.

### Does the BotFriendly MCP server require authentication?

No. We connected to BotFriendly without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the BotFriendly MCP server still maintained?

BotFriendly is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.botfriendly.xyz/api/mcp
- Website: https://www.botfriendly.xyz/
- Changelog RSS feed: https://verifymcp.io/servers/xyz-botfriendly-botfriendly/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-botfriendly-botfriendly/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/xyz-botfriendly-botfriendly/api-mcp