API Shakedown vs Fettle
API Shakedown is an MCP server published by anzar-ahsan-commits. 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-11-10. 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 |  API Shakedown |   Fettle |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.3 Downloads/month (PyPI): 0 Downloads/week (PyPI): 46 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 1.5.0 Downloads/month (npm): 1 920 Downloads/week (npm): 979 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.5.0 Downloads/month (npm): 1 920 Downloads/week (npm): 979 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 | API Shakedown | Fettle |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 2 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-24 (worse) | 2026-11-10 (better) |
| Where it runs (differs) | On your machine (api-shakedown) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 2 | 3, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/anzar-ahsan-commits/api-shakedown | github.com/fettlesh/monitoring-mcp |
| Changes in the last 7 days (differs) | 0 | 9 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | 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
API Shakedown
Turn an OpenAPI spec into WireMock stubs, contract tests and chaos scenarios, on local LLMs.
Fettle
Uptime monitoring — monitors, incidents, heartbeats, maintenance windows, status page incidents
How to run each
API Shakedown As a local MCP server: PyPI package
claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --transport stdio api-shakedown -- uvx api-shakedown mcpRequires: ANTHROPIC_API_KEY (secret), OPENAI_API_KEY (secret)
Fettle 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
Only API Shakedown asks for
ANTHROPIC_API_KEY (secret)OPENAI_API_KEY (secret)SHAKEDOWN_MODELSHAKEDOWN_OLLAMA_URLSHAKEDOWN_PROVIDER
Only Fettle asks for
FETTLE_API_KEY (secret)FETTLE_API_URLFETTLE_TIMEOUT_MS
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: API Shakedown · 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.