com.hyperping/hyperping vs nimo
com.hyperping/hyperping is an MCP server published by hyperping.com. Marketplaces we read that list it: 1 (Official MCP Registry). nimo is an MCP server published by marvtub. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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.hyperping/hyperping |  nimo |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 1 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.hyperping/hyperping | nimo |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 1 | 1 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.hyperping.io/v1/mcp) | Remote server (api.heynimo.com/mcp-server) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/hyperping/mcp-server | github.com/marvtub/nimo-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 403 (less than an hour ago) | Responded 20 h ago, requires a key |
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.hyperping/hyperping
Uptime, API and server monitoring with outages, reporting, on-call and status pages.
nimo
Website monitoring: uptime alerts, page speed and Core Web Vitals with the next fix, cron check-ins.
How to run each
com.hyperping/hyperping As a remote MCP server
claude mcp add --transport http hyperping https://api.hyperping.io/v1/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
nimo As a remote MCP server
claude mcp add --transport http nimo https://api.heynimo.com/mcp-serverCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of nimo responded at the last daily 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: com.hyperping/hyperping · What it can do: nimo · 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.