Skip to content

BotFriendly MCP server

xyz.botfriendly/botfriendlybotfriendly.xyzstreamable-httpv0.1.1Scanned

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

7 tools: 2 change things and 5 only read.

Tools: 0 delete, 0 irreversible, 2 write, 5 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 2
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the BotFriendly MCP server can do

The BotFriendly MCP server is published by botfriendly.xyz, a domain the MCP Registry verified. It has 7 tools. It can create or change data (2 tools: check_site and submit_service), but cannot delete data. 5 tools only read.

1 tool reads private data (search_services); 2 tools can send data out of your system (check_site and submit_service).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 0.1.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 2Claude Code: ask
  • check_siteScore how bot-friendly a website is (0-100).Can send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.
  • submit_serviceSubmit a service to the BotFriendly directory.Can send data outNo findings

    Why it is in this group

    • The name "submit_service" says "submit": a word for a change.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.
Only reads 5Show 5 read-only tools
  • get_protocol_statsGet 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…No findings

    Why it is in this group

    • The name "get_protocol_stats" says "get": a word for reading.
    Description, as the server wrote it
    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_serviceGet full details for a specific service by its slug, including all protocol support, URLs, auth method, billing, and metadata.No findings

    Why it is in this group

    • The name "get_service" says "get": a word for reading.
    Description, as the server wrote it
    Get full details for a specific service by its slug, including all protocol support, URLs, auth method, billing, and metadata.
  • list_categoriesList every BotFriendly category with its id (the search_services category value), human label, aliases (older slugs still accepted), description and service count.No findings

    Why it is in this group

    • The name "list_categories" says "list": a word for reading.
    Description, as the server wrote it
    List every BotFriendly category with its id (the search_services category value), human label, aliases (older slugs still accepted), description and service count.
  • search_servicesSearch the BotFriendly directory for bot-friendly services, APIs, and tools that AI agents can use.Reads private dataNo findings

    Why it is in this group

    • The name "search_services" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "search" and "directory": it reads files.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:21 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.botfriendly.xyz: tools/list returned 7 tools to an anonymous client, including check_site (write), submit_service (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.1.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http botfriendly https://mcp.botfriendly.xyz
claude mcp add --transport http botfriendly https://mcp.botfriendly.xyz

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__botfriendly__search_services",
      "mcp__botfriendly__get_service",
      "mcp__botfriendly__list_categories",
      "mcp__botfriendly__get_featured",
      "mcp__botfriendly__get_protocol_stats"
    ],
    "ask": [
      "mcp__botfriendly__check_site",
      "mcp__botfriendly__submit_service"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as botfriendly. Review it before you use it.

Capability tags behind 3 rules
  • mcp__botfriendly__search_services private-data
  • mcp__botfriendly__check_site outbound
  • mcp__botfriendly__submit_service outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/xyz.botfriendly/botfriendly/verify?hash=eec7c51a744a8502ed13d454965e9e4ce4eb5faa5bf0c65bc6bba272f9acfec7" | jq -e '.changed == false'

Pinned hash eec7c51a744a, from Nov 19, 2026, 12:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/xyz.botfriendly/botfriendly/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for xyz.botfriendly/botfriendly
[![Anlyon Radar](https://radar.anlyon.com/badge/xyz.botfriendly/botfriendly.svg)](https://radar.anlyon.com/servers/xyz.botfriendly/botfriendly)

Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.

BotFriendly MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the BotFriendly MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the BotFriendly MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the BotFriendly MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the BotFriendly MCP server have?

7 tools: 2 write, 5 read. check_site, submit_service, search_services, get_service, list_categories, get_featured and get_protocol_stats.

Does the BotFriendly MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the BotFriendly MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_site and submit_service.

Has the BotFriendly MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.