LastPing vs io.github.Churman1113/pingcheck-mcp
LastPing is an MCP server published by lastping.dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.Churman1113/pingcheck-mcp is an MCP server published by Churman1113. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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 |   LastPing | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.2 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Listed Version: 0.2.1 Downloads/month (npm): 199 Downloads/week (npm): 47 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 | LastPing | io.github.Churman1113/pingcheck-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 3 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | 2026-10-13 | Not published |
| Where it runs (differs) | Remote server (mcp.lastping.dev/mcp) | On your machine (pingcheck-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| 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/lastping-dev/lastping-app | github.com/churman1113/pingcheck |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 12 h ago, requires a key | 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
LastPing
AI agent monitoring: alerts when your agents fail, stall or need you
io.github.Churman1113/pingcheck-mcp
PingCheck status monitoring for AI agents. Read public pages or your own monitors via pk_ API key.
How to run each
LastPing As a remote MCP server
claude mcp add --transport http lastping https://mcp.lastping.dev/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
io.github.Churman1113/pingcheck-mcp As a local MCP server: npm package
claude mcp add --transport stdio pingcheck-mcp -- npx -y pingcheck-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only LastPing 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: LastPing · What it can do: io.github.Churman1113/pingcheck-mcp · 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.