# BotFriendly

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

- name: xyz.botfriendly/botfriendly
- version: 0.1.1
- connection class: R0 (autonomous)
- trust: 83/100 flags: no-repository
- quality: 79/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/xyz.botfriendly%2Fbotfriendly
- tools: https://api.protogrid.dev/v1/servers/xyz.botfriendly%2Fbotfriendly/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

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


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% +updated-26d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 79/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 71 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: submit_service (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_categories (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_featured (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 1,971 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: 4 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 7, about 1,971 tokens to load them all
- tool set hash: 58d9f55399e5776d262b349202875a2e
- tools last changed: 2026-10-08T01:17:37.143Z
- badge: [![protogrid quality](https://protogrid.dev/badge/xyz.botfriendly/botfriendly.svg)](https://protogrid.dev/servers/xyz.botfriendly/botfriendly)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-08 `search_services` changed (inputSchema)
- 2026-10-07 `submit_service` changed (description, inputSchema)
  - before: 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 its MCP server or OpenAPI spec completes a handshake — one of has_mcp_server or has_openapi_spec is required; llms.txt, skill files and feeds only add badges. The url must be the product, not an article (/blog/, /news/ and similar are rejected), and a domain can add at most 2 listings a day and 3 in total. Every listing needs an icon — pass icon_url, or leave it out and the service's own site is checked for one.
  - after: Submit a service to the BotFriendly directory. There is no review queue: each interface URL must be on the service's own domain, or linked from the service's own site, and is fetched during the call; the listing publishes immediately if its MCP server, OpenAPI spec or API completes a handshake — one of has_mcp_server, has_openapi_spec or has_api is required; llms.txt, skill files and feeds only add badges. The url must be the product, not an article (/blog/, /news/ and similar are rejected), and a domain can add at most 2 listings a day and 3 in total. Every listing needs an icon — pass icon_url, or leave it out and the service's own site is checked for one.
- 2026-10-07 `get_protocol_stats` changed (description)
  - before: 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.
  - after: Get every protocol on botfriendly.xyz/protocols with adoption stats: how agents call a service and prove who sent them (MCP, OpenAPI, A2A, XAA) 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 count — how many listed services support it, or null for protocols that aren't a listing attribute (A2A, XAA).
- 2026-10-05 `submit_service` changed (description)
  - before: 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.
  - after: 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 its MCP server or OpenAPI spec completes a handshake — one of has_mcp_server or has_openapi_spec is required; llms.txt, skill files and feeds only add badges. The url must be the product, not an article (/blog/, /news/ and similar are rejected), and a domain can add at most 2 listings a day and 3 in total. Every listing needs an icon — pass icon_url, or leave it out and the service's own site is checked for one.

Full history: https://api.protogrid.dev/v1/servers/xyz.botfriendly%2Fbotfriendly/changes

## Remotes

- https://mcp.botfriendly.xyz (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (7)

- `check_site`: 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.
- `get_featured`: Get site-wide featured/promoted services (max 3). These are paid placements clearly marked as ads.
- `get_protocol_stats`: Get every protocol on botfriendly.xyz/protocols with adoption stats: how agents call a service and prove who sent them (MCP, OpenAPI, A2A, XAA) 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 count — how many listed services support it, or null for protocols that aren't a listing attribute (A2A, XAA).
- `get_service`: Get full details for a specific service by its slug, including all protocol support, URLs, auth method, billing, and metadata.
- `list_categories`: List every BotFriendly category with its id (the search_services category value), human label, aliases (older slugs still accepted), description and service count.
- `search_services`: 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.
- `submit_service`: Submit a service to the BotFriendly directory. There is no review queue: each interface URL must be on the service's own domain, or linked from the service's own site, and is fetched during the call; the listing publishes immediately if its MCP server, OpenAPI spec or API completes a handshake — one of has_mcp_server, has_openapi_spec or has_api is required; llms.txt, skill files and feeds only add badges. The url must be the product, not an article (/blog/, /news/ and similar are rejected), and a domain can add at most 2 listings a day and 3 in total. Every listing needs an icon — pass icon_url, or leave it out and the service's own site is checked for one.