Pingvera MCP vs Upcheck
A side-by-side look at the Pingvera MCP and Upcheck MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
P
Pingvera MCPMonitoringClient-website monitoring for agencies: uptime, incidents, SSL/domain expiry, server metrics.38FairAuth: not declaredU
UpcheckMonitoring · Remote HTTP/SSEMonitor website uptime, SSL certificates, DNS, domain expiry and page changes, and manage alerts.42FairAuth: not declaredVerdict: choose Pingvera MCP for monitoring work; choose Upcheck for monitoring over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
PChoose Pingvera MCP when
- You need dedicated capabilities in the Monitoring domain.
UChoose Upcheck when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | P Pingvera MCP | U Upcheck |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 38/100 · Fair | 42/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | — |
| Directory activity | 7 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Pingvera MCP | View Upcheck |
Tools & capabilities
Pingvera MCP tools
No tool names declared yet. Check the project README from the listing page.
Upcheck tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Pingvera MCP
No confirmed install command for Pingvera MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Upcheck
{
"mcpServers": {
"upcheck": {
"url": "https://upcheck.so/mcp"
}
}
}
Frequently asked questions
Pingvera MCP is categorized under Monitoring and uses an install path we have not confirmed yet. Upcheck belongs to Monitoring and uses a remote HTTP/SSE transport. Pick Pingvera MCP for monitoring work and Upcheck for monitoring.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Pingvera MCP has no confirmed install command yet — follow its own setup instructions.
Pingvera MCP has no declared pricing — check the project's own site. Upcheck has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add monitoring-2 and upcheck as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Pingvera MCP has a quality signal of 38/100 (Fair) with 7 views, 0 installs and 0 GitHub stars. Upcheck has 42/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.