Com.Bot MCP server
bot.com/combotcom.botstreamable-httpv1.0.0Scanned
Facts about Com.Bot, the WhatsApp Business API platform: plans, channels and site search.
6 tools: 1 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 Com.Bot MCP server can do
The Com.Bot MCP server is published by com.bot, a domain the MCP Registry verified. It has 6 tools. It can create or change data (1 tool: ask_question), but cannot delete data. 5 tools only read.
1 tool brings in text other people can write (get_page); 1 tool can send data out of your system (get_page).
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 12, 2026, version 1.0.0.
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.
6 tools
Changes things 1Claude Code: ask
ask_questionAnswer a plain-language question about Com.Bot from its verified facts and its own pages (the same answer as fetching com.bot/{question-with-hyphens}).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Answer a plain-language question about Com.Bot from its verified facts and its own pages (the same answer as fetching com.bot/{question-with-hyphens}). Returns markdown with the source page.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 5Show 5 read-only tools
get_brand_factsEvery verified fact about Com.Bot: what it is, pricing, what is included, policies and what not to state.No findings
Why it is in this group
- The name "get_brand_facts" says "get": a word for reading.
Description, as the server wrote it Every verified fact about Com.Bot: what it is, pricing, what is included, policies and what not to state. Use this before describing Com.Bot.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_pageThe clean markdown text of any published page on com.bot.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "get_page" says "get": a word for reading.
What it can reach
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it The clean markdown text of any published page on com.bot.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_pricingCom.Bot plans and prices, and what each includes.No findings
Why it is in this group
- The name "get_pricing" says "get": a word for reading.
Description, as the server wrote it Com.Bot plans and prices, and what each includes.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_servicesWhat Com.Bot offers (channels, features or services), each with a one-line description.No findings
Why it is in this group
- The name "list_services" says "list": a word for reading.
Description, as the server wrote it What Com.Bot offers (channels, features or services), each with a one-line description.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_siteSearch every page on com.bot by keywords.No findings
Why it is in this group
- The name "search_site" says "search": a word for reading.
Description, as the server wrote it Search every page on com.bot by keywords. Returns titles, URLs, markdown URLs and descriptions; read a result with get_page.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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 private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- 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.
Looked at Nov 20, 2026, 18:31 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
- 1
- 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 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://com.bot/mcp: tools/list returned 6 tools to an anonymous client, including ask_question (write)
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 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http combot https://com.bot/mcpclaude mcp add --transport http combot https://com.bot/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__combot__get_brand_facts",
"mcp__combot__get_pricing",
"mcp__combot__list_services",
"mcp__combot__search_site"
],
"ask": [
"mcp__combot__ask_question",
"mcp__combot__get_page"
],
"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 combot. Review it before you use it.
Capability tags behind 1 rule
- mcp__combot__get_page untrusted-input, 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/bot.com/combot/verify?hash=0c27564f329fc12d70acc8ed1d95b4f10f33ab94e9ae7515d15a095eda7c3f2f" | jq -e '.changed == false'Pinned hash 0c27564f329f, from Nov 12, 2026, 06:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/bot.com/combot/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/bot.com/combot)Source: MCP Registry. Synced Oct 21, 2026, 17:46 UTC.
Com.Bot MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Com.Bot MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 1 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 Com.Bot MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Com.Bot 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 Com.Bot MCP server have?
- 6 tools: 1 write, 5 read. ask_question, get_brand_facts, get_pricing, list_services, search_site and get_page.
Does the Com.Bot MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Com.Bot MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): get_page.
Has the Com.Bot MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.