com.selfping/selfping vs Notify MCP Server
com.selfping/selfping is an MCP server published by selfping.com. Marketplaces we read that list it: 1 (Official MCP Registry). Notify MCP Server is an MCP server published by aahl. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  com.selfping/selfping |  Notify MCP Server |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.1.11 Downloads/month (PyPI): 543 Downloads/week (PyPI): 119 Forks (GitHub): 8 Stars (GitHub): 28 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 | com.selfping/selfping | Notify MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 28 |
| Forks (GitHub) (differs) | No figure on GitHub | 8 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (www.selfping.com/api/mcp) | On your machine (mcp-notify) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 12, secrets among them: 7 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/aahl/mcp-notify |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
com.selfping/selfping
Text your own phone when a run finishes or needs you. A key can only message its own number.
Notify MCP Server
MCP Server for notify to Weixin, Telegram, Bark, Lark, Feishu, DingTalk
How to run each
com.selfping/selfping As a remote MCP server
claude mcp add --transport http selfping https://www.selfping.com/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Notify MCP Server As a local MCP server: PyPI package
claude mcp add --env "DINGTALK_BOT_KEY=<YOUR_DINGTALK_BOT_KEY>" --env "FEISHU_BOT_KEY=<YOUR_FEISHU_BOT_KEY>" --env "LARK_BOT_KEY=<YOUR_LARK_BOT_KEY>" --env "PUSH_PLUS_TOKEN=<YOUR_PUSH_PLUS_TOKEN>" --env "TELEGRAM_BOT_TOKEN=<YOUR_TELEGRAM_BOT_TOKEN>" --env "WEWORK_APP_SECRET=<YOUR_WEWORK_APP_SECRET>" --env "WEWORK_BOT_KEY=<YOUR_WEWORK_BOT_KEY>" --transport stdio mcp-notify -- uvx mcp-notifyRequires: DINGTALK_BOT_KEY (secret), FEISHU_BOT_KEY (secret), LARK_BOT_KEY (secret), PUSH_PLUS_TOKEN (secret), TELEGRAM_BOT_TOKEN (secret), WEWORK_APP_SECRET (secret), WEWORK_BOT_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.selfping/selfping 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
The marketplaces of com.selfping/selfping publish no settings it asks for, so we do not compare settings.
What it can do: com.selfping/selfping · What it can do: Notify MCP Server · Compare two other plugins
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.