qqbot vs whatsapi.sh
qqbot is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑25.
qqbot is a plugin bundle for AI coding tools published by hank9999. No marketplace we read lists it any more. whatsapi.sh is an MCP server published by whatsapi.sh. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  whatsapi.sh | |
|---|---|---|
| Community marketplace hank9999/claude-qq-channel | Removed on 2026-10-25 Version: 0.0.1 Forks (GitHub): 0 Stars (GitHub): 10 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | qqbotno longer listed · | whatsapi.sh |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 10 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (api.whatsapi.sh/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/hank9999/claude-qq-channel | Not stated |
| Changes in the last 7 days (differs) | 3 | 0 |
| First seen (differs) | 2026-10-20 | 2026-10-17 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 32 h ago, requires a key |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of qqbot
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
WeChat channel for Claude Code — bridges your personal WeChat account to a Claude Code session via Tencent's iLink bot API. Supports two-way messaging (receive WeChat messages…
-
WeCom (Enterprise WeChat) Channel Plugin for Claude Code — enables two-way messaging between Claude Code sessions and WeCom users via AI Bot or Self-built App mode.
-
Connect a Telegram bot to your Claude Code session over MCP. The server logs in as a bot, forwards inbound messages into the session as <channel> notifications, and exposes tools…
-
Matrix channel for Claude Code — two-way messaging bridge with E2EE, access control, and permission relay
-
Telegram channel for Claude Code with per-project bot isolation. Each project gets its own Telegram bot, access policy, and message inbox — so messages to @alpha_bot reach…
-
Manage, automate and analyze WhatsApp groups, communities and channels with 9bot.
What each says it does
qqbot
QQ Bot channel for Claude Code — messaging bridge with built-in access control.
whatsapi.sh
Send WhatsApp messages from your own numbers, read and answer chats, and send sign-in codes.
How to run each
qqbot
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
whatsapi.sh As a remote MCP server
claude mcp add --transport http whatsapi https://api.whatsapi.sh/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only whatsapi.sh has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: qqbot · What it can do: whatsapi.sh · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.