StatOSS vs Fettle
A side-by-side look at the StatOSS and Fettle MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
StatOSSMonitoringStatus pages and uptime monitoring: read status, monitors and incidents; open incidents.37FairAuth: not declaredF
FettleMonitoring · Remote HTTP/SSEUptime monitoring for developers — monitors, incidents, heartbeats, maintenance, status pages37FairAuth: not declaredVerdict: choose StatOSS for monitoring work; choose Fettle for monitoring over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
FChoose Fettle 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 StatOSS | F Fettle |
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 37/100 · Fair | 37/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 | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View StatOSS | View Fettle |
Tools & capabilities
StatOSS tools
No tool names declared yet. Check the project README from the listing page.
Fettle 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.
StatOSS
No confirmed install command for StatOSS yet — follow the setup steps linked from its listing page rather than a guessed package name.
Fettle
{
"mcpServers": {
"fettle-2": {
"url": "https://fettle.sh/docs/mcp"
}
}
}
Frequently asked questions
StatOSS is categorized under Monitoring and uses an install path we have not confirmed yet. Fettle belongs to Monitoring and uses a remote HTTP/SSE transport. Pick StatOSS for monitoring work and Fettle 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. StatOSS has no confirmed install command yet — follow its own setup instructions.
StatOSS has no declared pricing — check the project's own site. Fettle 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 statoss and fettle-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, StatOSS has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Fettle has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
