A
anzar-ahsan-commits/api-shakedown
Give it an OpenAPI spec.
★ 2·updated 2026-11-01
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 2 ★ · anzar-ahsan-commits/api-shakedown · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 2 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
anzar-ahsan-commits/api-shakedown;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# API Shakedown
Excerpted from the repository README (abridged)
Give it an OpenAPI spec. Get back a ready-to-run test harness: WireMock stubs, contract
tests, robustness probes, and chaos scenarios, written by a team of LLM agents that
review each other's work.
Runs locally on Ollama by default: no API key, no data leaves
your machine. Cloud models (OpenAI, Anthropic) are bring-your-own-key. Available as a
CLI, a Docker image, and an MCP server so an AI assistant can drive it.
> Status: alpha (0.1.3). Works end to end on the example spec with a local 8B model.
A real run on the bundled example with qwen3:8b on a laptop, sped up: generation
took about 9 minutes. Recording: docs/demo.cast.
## Contents
Why
Where it helps
Quick start
What you get
How it works
Install
Usage
Configuration
MCP server
Docker
Architecture
Limitations
Roadmap
Development
Contributing
License
## Why
Teams that consume an API need three things that are tedious to write by hand and go
stale quickly:
1. A realistic mock of the API to develop and test against.
2. Contract tests that tell you when the real API stops matching its spec.
3. Failure drills: what does your client do when the API is slow, flaky, rate
limited, returns garbage, or goes down?
API Shakedown generates all three from the spec you already have, and keeps them honest:
the LLMs never write code that runs. They propose data (response bodies, test
cases, failure scenarios, test records), and code validates every item against the
spec, feeds problems back to the model, and falls back to deterministic output when a
model cannot get it right. Without any model at all (--offline), every part still works.
## Where it helps
| Situation | Typical teams | What API Shakedown gives you |
| Building before the backend exists | Frontend, mobile, partner integrators | A virtual service generated from the agreed spec, so work starts on day one instead of after the backend ships or after hand-written mocks. |
| Depending on APIs you don't control (payments, shipping, identity checks, credit bureaus) | Fintech, e-commerce, logistics, insurance | Vendor sandboxes are often rate-limited, flaky or billed per call. Test locally what your app does when the provider times out, rate-limits you, or returns 503 twice before recovering. |
| Proving clients survive failure | Microservice teams, SRE game days | Switch timeouts, rate limits, flaky calls and partial outages on and off while your client runs, and confirm retries, backoff and fallbacks really work. |
| Catching spec drift before release | API owners, platform and public-API teams | Contract tests run against a real deployment in CI and fail when the implementation stops matching its spec. |
| Hardening input validation | Any API team | Robustness probes check that malformed requests get a 4xx, never a 500. A complement to a security review, not a replacement. |
| Regulated or offline environments | Banking, healthcare, government | Everything runs on a local model: the spec never leaves the machine, where many AI tools cannot be used at all. |
| Migrating or rewriting a service | Legacy modernisation | Generate contract tests from the existing spec and run them against the new implementation to confirm it behaves the same. |
tests, robustness probes, and chaos scenarios, written by a team of LLM agents that
review each other's work.
Runs locally on Ollama by default: no API key, no data leaves
your machine. Cloud models (OpenAI, Anthropic) are bring-your-own-key. Available as a
CLI, a Docker image, and an MCP server so an AI assistant can drive it.
> Status: alpha (0.1.3). Works end to end on the example spec with a local 8B model.
A real run on the bundled example with qwen3:8b on a laptop, sped up: generation
took about 9 minutes. Recording: docs/demo.cast.
## Contents
Why
Where it helps
Quick start
What you get
How it works
Install
Usage
Configuration
MCP server
Docker
Architecture
Limitations
Roadmap
Development
Contributing
License
## Why
Teams that consume an API need three things that are tedious to write by hand and go
stale quickly:
1. A realistic mock of the API to develop and test against.
2. Contract tests that tell you when the real API stops matching its spec.
3. Failure drills: what does your client do when the API is slow, flaky, rate
limited, returns garbage, or goes down?
API Shakedown generates all three from the spec you already have, and keeps them honest:
the LLMs never write code that runs. They propose data (response bodies, test
cases, failure scenarios, test records), and code validates every item against the
spec, feeds problems back to the model, and falls back to deterministic output when a
model cannot get it right. Without any model at all (--offline), every part still works.
## Where it helps
| Situation | Typical teams | What API Shakedown gives you |
| Building before the backend exists | Frontend, mobile, partner integrators | A virtual service generated from the agreed spec, so work starts on day one instead of after the backend ships or after hand-written mocks. |
| Depending on APIs you don't control (payments, shipping, identity checks, credit bureaus) | Fintech, e-commerce, logistics, insurance | Vendor sandboxes are often rate-limited, flaky or billed per call. Test locally what your app does when the provider times out, rate-limits you, or returns 503 twice before recovering. |
| Proving clients survive failure | Microservice teams, SRE game days | Switch timeouts, rate limits, flaky calls and partial outages on and off while your client runs, and confirm retries, backoff and fallbacks really work. |
| Catching spec drift before release | API owners, platform and public-API teams | Contract tests run against a real deployment in CI and fail when the implementation stops matching its spec. |
| Hardening input validation | Any API team | Robustness probes check that malformed requests get a 4xx, never a 500. A complement to a security review, not a replacement. |
| Regulated or offline environments | Banking, healthcare, government | Everything runs on a local model: the spec never leaves the machine, where many AI tools cannot be used at all. |
| Migrating or rewriting a service | Legacy modernisation | Generate contract tests from the existing spec and run them against the new implementation to confirm it behaves the same. |
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/anzar-ahsan-commits-api-shakedown/)
- Source
- awesome · https://github.com/anzar-ahsan-commits/api-shakedown
- Browse by field
- MCP servers
- Traction
- 2 ★
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.