Free API · no key · every badge probe-backed
A directory of APIs, tools and merchants built for machines — MCP servers, OpenAPI specs, llms.txt and agent payment rails.
Or browse the directory, or check how bot-friendly your own site is.
Ranked by bot score: machine-readable interfaces, machine-completable auth, and how much an agent can do without a human.
 Open spec from OpenAI and Stripe for agent-initiated checkout — product feeds, checkout endpoints, and scoped delegated payment tokens with the merchant staying merchant of record | 5/5 |
 Claude models with tool use, the MCP connector, Agent Skills, and the Claude Agent SDK | 5/5 |
 Marketplace of thousands of scraping and automation Actors, exposed over API and a remote MCP server | 5/5 |
 Tool-calling runtime with per-user OAuth, so agents act as the signed-in user across third-party APIs | 5/5 |
 OpenTelemetry-native, open-source tracing and evaluation for LLM and agent applications | 5/5 |
 Gift cards, phone top-ups, and eSIMs bought over an eCommerce MCP server, payable with x402 or L402 — no account, no card on file | 5/5 |
A listing only claims an MCP server, an OpenAPI spec, an API or an llms.txt when we fetched that endpoint — on the service's own domain, or one its own site links to — and something answered. Nothing here is self-asserted.
How listings get inThe whole directory is one unauthenticated GET away, CORS open, rate limited by IP alone. Search, filter by protocol, and read the same fields this page renders.
Read the docsThere is no approval queue and no human in the middle. The directory’s only real asset is that its badges are true, so every badge names an artifact a machine can fetch.
Through the form or one POST to the public API. No account needed, no queue to wait in.
Every claimed interface is fetched, and has to sit on the service's own domain or be linked from it.
Claims that stand up go live. Claims that don't are dropped, and the reason names exactly what was tried.
The whole directory is free and unauthenticated. Connect the hosted MCP server, query the JSON API, or ask any page for markdown with an Accept header.
connect the mcp server
https://mcp.botfriendly.xyzPaste it as a custom connector in Claude, ChatGPT, Cursor or any MCP client. Hosted by us, no key, nothing else to configure. Steps for your client
claude mcp add botfriendly --transport http https://mcp.botfriendly.xyzor query the api
curl "https://botfriendly.xyz/api/v1/services?has_mcp=true&protocol=x402"Most of these came from the daily crawl of the MCP registry, probed before they landed.
 Niftynew All-in-one project management hub for tasks, milestones, docs and chat, with an official remote MCP server. | 3/5 |
 Userbacknew User feedback and bug reporting with screenshots and session replay, with an official remote MCP server. | 3/5 |
 Lyssnanew User research platform for usability tests, surveys and interviews, with an official remote MCP server. | 3/5 |
 Hygraphnew GraphQL headless CMS for managing structured content and schemas, with an official remote MCP server. | 3/5 |
 FLORAnew Generative AI canvas for images, video, audio and 3D for creative teams, with an official remote MCP server. | 3/5 |
 Carbonenew Document generation API rendering PDF, Word, Excel and PowerPoint from templates, with an official remote MCP server. | 3/5 |
The checker fetches a site the way an agent does — no JavaScript, no cookies — and scores access, content and machine discovery out of 100, with a fix for every gap.
Run a checkFilter for the services that actually take machine money: x402, MPP, ACP, UCP and the rest, tracked as a registry rather than a marketing claim.
Browse protocols
