com.uptimemonitoring/mcp vs AgentResolver — Agent Commerce Health Monitoring
com.uptimemonitoring/mcp is an MCP server published by uptimemonitoring.com. Marketplaces we read that list it: 1 (Official MCP Registry). AgentResolver — Agent Commerce Health Monitoring is an MCP server published by waxsway. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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.uptimemonitoring/mcp |  AgentResolver — Agent Commerce Health Monitoring |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.2.4 Forks (GitHub): 0 Stars (GitHub): 0 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.uptimemonitoring/mcp | AgentResolver — Agent Commerce Health Monitoring |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.uptimemonitoring.com/mcp) | Remote server (agentresolver.vercel.app/mcp) |
| 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/uptimemonitoring/examples | github.com/waxsway/agentresolver |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 5 days ago, requires a key | Responded 23 h ago |
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.uptimemonitoring/mcp
Agent-native uptime monitoring. Create, inspect, and assert monitor health. Free 50-monitor tier.
AgentResolver — Agent Commerce Health Monitoring
Free API/MCP/x402 health checks plus $19 hourly managed monitoring for agent services.
How to run each
com.uptimemonitoring/mcp As a remote MCP server
claude mcp add --transport http com-uptimemonitoring-mcp https://api.uptimemonitoring.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
AgentResolver — Agent Commerce Health Monitoring As a remote MCP server
claude mcp add --transport http agentresolver https://agentresolver.vercel.app/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints 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.uptimemonitoring/mcp · What it can do: AgentResolver — Agent Commerce Health Monitoring · 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.