Stackwitness MCP vs RealUptime
A side-by-side look at the Stackwitness MCP and RealUptime MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
Stackwitness MCPMonitoring · Remote HTTP/SSEIndependent monitoring: status, monitors, and incidents from your StackWitness workspace.42FairAuth: not declaredR
RealUptimeMonitoringRealUptime monitors, incidents, status pages, Errors issues, and free third-party outage checks.37FairAuth: not declaredVerdict: choose Stackwitness MCP for monitoring work over a hosted endpoint; choose RealUptime for monitoring. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
SChoose Stackwitness MCP 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 | S Stackwitness MCP | R RealUptime |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 42/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| 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 | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Stackwitness MCP | View RealUptime |
Tools & capabilities
Stackwitness MCP tools
No tool names declared yet. Check the project README from the listing page.
RealUptime 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.
Stackwitness MCP
{
"mcpServers": {
"mcp-145": {
"url": "https://stackwitness.com/integrations/mcp"
}
}
}
RealUptime
No confirmed install command for RealUptime yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Stackwitness MCP is categorized under Monitoring and uses a remote HTTP/SSE transport. RealUptime belongs to Monitoring and uses an install path we have not confirmed yet. Pick Stackwitness MCP for monitoring work and RealUptime 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. RealUptime has no confirmed install command yet — follow its own setup instructions.
Stackwitness MCP has no declared pricing — check the project's own site. RealUptime 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 mcp-145 and realuptime as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Stackwitness MCP has a quality signal of 42/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. RealUptime has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
