BotFriendly

xyz.botfriendlyPublished by botfriendly.xyzOfficial publisherv0.1.1Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

A remote MCP server for the BotFriendly directory that lets an assistant find, inspect, score and submit services, APIs and tools built for AI agents.

What you can do
Search the directory of bot-friendly services and APIs, filtering by category, payment or commerce protocol support and auth method, with promoted listings shown first and marked as ads. Read full details for a service by slug, including protocol support, URLs, auth method, billing and metadata. List all categories with ids, labels, aliases, descriptions and service counts. Fetch site-wide featured or promoted services, which are paid placements. Get adoption statistics for agent access and payment protocols. Score how bot-friendly a website is by fetching it without JavaScript or cookies and checking access, content and machine discovery. Submit a new service to the directory.
When to use it
Useful when an assistant needs to discover agent-ready APIs, merchants or tools, compare their payment and auth protocols, or judge whether a website is accessible to agents before integrating with it.
Requirements
A remote streamable HTTP endpoint; no package, environment variables or headers are declared, and no authentication is declared. The check_site and submit_service tools fetch external websites over the network.
Before you install
submit_service publishes a listing immediately with no review queue, so submitted data goes public; interface URLs must be on the service's own domain or linked from its site and are fetched during the call. Search results and featured entries include paid placements marked as ads, so ranking is not purely organic. check_site fetches third-party sites on your behalf.

Installation

In SourceWeft

  1. Open BotFriendly in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/xyz.botfriendly%2Fbotfriendly/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

7

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.

Parameterspagesortqueryhas_mcpcategoryno_humanpromotedprotocolmin_scoreaccepts_mppauth_methodaccepts_x402

get_service

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

Parametersslugrequired

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.

Takes no parameters.

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

Takes no parameters.

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.

Parametersurlrequiredformat

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.

Parametersurlrequirednamerequiredtagsapi_urlhas_apicategoryrequiredicon_urlaccepts_mppauth_methoddescriptionrequiredicon_base64accepts_x402+6 more

Version history

2
  1. v0.1.1LatestSep 25, 2026
  2. v0.1.0Sep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.