Com.Bot
REMOTE · COM.BOT
Facts about Com.Bot, the WhatsApp Business API platform: plans, channels and site search.
Available components
Last scanned (1 hour ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Communication
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability39
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 335 tokens (~37/item across 9 items; 6 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
- Schema quality: 272 → 335 ▼ functional
- Tool coverage: 33% → 50% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “ask_question” functional
- 12 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://com.bot/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=com.bot | CN=YR1,O=Let's Encrypt,C=US | 10 Oct 2026 | 8 Jan 2027 | RSA 2048 | SHA256-RSA | 52c4ce4b8be7857f50d8f527d5a458428ba |
| SANs: com.bot, www.com.bot | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of com.bot. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| bot. | present | 58741 | 8 | Verified |
| com.bot. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://com.bot/mcp | Verified | 200 | |
| http (plaintext) | http://com.bot/mcp | HTTPS enforced | 301 | https://com.bot/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ask_question Ask a question about Com.Bot ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | e.g. How much does Com.Bot cost? |
No output schema declared.
No examples provided.
get_brand_facts Com.Bot brand facts ~41
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_page Read a page as markdown ~34
The clean markdown text of any published page on com.bot.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | A URL or path on com.bot |
No output schema declared.
No examples provided.
get_pricing Pricing ~20
Com.Bot plans and prices, and what each includes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_services Services and features ~26
What Com.Bot offers (channels, features or services), each with a one-line description.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_site Search com.bot ~48
Search every page on com.bot by keywords. Returns titles, URLs, markdown URLs and descriptions; read a result with get_page.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Com.Bot MCP server?
Com.Bot is a hosted endpoint at https://com.bot/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · com.bot
claude mcp add --transport http bot-com-combot 'https://com.bot/mcp'
What is the Com.Bot MCP server?
Com.Bot is an MCP server listed in the public MCP registry as bot.com/combot. Facts about Com.Bot, the WhatsApp Business API platform: plans, channels and site search. This page covers its hosted endpoint (https://com.bot/mcp).
Is the Com.Bot MCP server safe to use?
Com.Bot scores 64 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Com.Bot MCP server expose?
Com.Bot exposes 6 tools: get_brand_facts, get_pricing, list_services, search_site, ask_question, get_page. Their descriptions and schemas cost roughly 232 tokens of context every time the server is loaded.
Does the Com.Bot MCP server require authentication?
No. We connected to Com.Bot without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Com.Bot MCP server still maintained?
Com.Bot is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.