Stream Vessel vs Fettle
Stream Vessel is an MCP server published by streamvessel. Marketplaces we read that list it: 1 (Official MCP Registry). Fettle is an MCP server published by fettle.sh. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). 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 |  Stream Vessel |   Fettle |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.6.1 Downloads/month (npm): 508 Downloads/week (npm): 229 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.6.1 Downloads/month (npm): 508 Downloads/week (npm): 229 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 | Stream Vessel | Fettle |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-20 |
| Where it runs (differs) | Remote server (mcp.streamvessel.com) | Remote server or your machine |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/streamvessel/ai-integrations | github.com/fettlesh/monitoring-mcp |
| Changes in the last 7 days (differs) | 2 | 10 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | Responded 26 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
Stream Vessel
Browse, upload, download, copy, move and share files in your own S3-compatible buckets.
Fettle
Uptime monitoring for developers — monitors, incidents, heartbeats, maintenance, status pages
How to run each
Stream Vessel As a remote MCP server
claude mcp add --transport http streamvessel https://mcp.streamvessel.comFettle As a remote MCP server
claude mcp add --transport http fettle https://api.fettle.sh/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: FETTLE_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Fettle 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
The marketplaces of Stream Vessel publish no settings it asks for, so we do not compare settings.
What it can do: Stream Vessel · What it can do: Fettle · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.