API Shakedown
OCI · GHCR.IO/ANZAR-AHSAN-COMMITS/API-SHAKEDOWN · 2 COMPONENTS
Turn an OpenAPI spec into WireMock stubs, contract tests and chaos scenarios, on local LLMs.
Available components
Last scanned (7 hours ago)
Scores higher than 52% of OCI servers
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 393 tokens (~65/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 0
- Package version: 0.1.1 → 0.1.3 functional
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 15 Oct 26 36
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Oct 2026 · Analysed oci/ghcr.io/anzar-ahsan-commits/api-shakedown@0.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
activate_chaos ~52
Turn one chaos scenario on in the harness's running WireMock (others go off).
| Name | Type | Req | Description |
|---|---|---|---|
| harness_dir | string | yes | – |
| scenario_id | string | yes | – |
| wiremock_url | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| active | – | yes | – |
| mappings_added | integer | – | – |
| wiremock_url | string | yes | – |
No examples provided.
deactivate_chaos ~32
Turn all chaos scenarios off: the stubs behave normally again.
| Name | Type | Req | Description |
|---|---|---|---|
| wiremock_url | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| active | – | yes | – |
| mappings_added | integer | – | – |
| wiremock_url | string | yes | – |
No examples provided.
doctor ~22
Check that the configured LLM provider is reachable and the model is available.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | yes | – |
| model | string | yes | – |
| ok | boolean | yes | – |
| provider | string | yes | – |
No examples provided.
generate_harness ~123
Generate a ready-to-run chaos test harness for an OpenAPI spec into out_dir. offline=true skips the LLM (deterministic, seconds); otherwise this takes minutes on a local model, and review=false roughly halves that. Refuses a non-empty out_dir unless force=true (which overwrites only the harness's own files).
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | – |
| max_revisions | integer | – | – |
| offline | boolean | – | – |
| out_dir | string | yes | – |
| review | boolean | – | – |
| spec | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | – |
| next_steps | array | yes | – |
| notes | array | yes | – |
| out_dir | string | yes | – |
| reviews | array | yes | – |
| summary | object | yes | – |
| unresolved | array | yes | – |
No examples provided.
inspect_spec ~36
Load and validate an OpenAPI spec (file path or http(s) URL) and list its operations.
| Name | Type | Req | Description |
|---|---|---|---|
| spec | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| openapi_version | string | yes | – |
| operations | array | yes | – |
| title | string | yes | – |
| version | string | yes | – |
| warnings | array | yes | – |
No examples provided.
list_chaos_scenarios ~30
List the chaos scenarios of a generated harness.
| Name | Type | Req | Description |
|---|---|---|---|
| harness_dir | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | array | yes | – |
No examples provided.
How do I install the API Shakedown MCP server?
API Shakedown runs locally as a container image, launched with docker run --rm -i ghcr.io/anzar-ahsan-commits/api-shakedown:0.1.3. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/anzar-ahsan-commits/api-shakedown
claude mcp add anzar-ahsan-commits-api-shakedown -- docker run --rm -i ghcr.io/anzar-ahsan-commits/api-shakedown:0.1.3
What is the API Shakedown MCP server?
API Shakedown is an MCP server listed in the public MCP registry as io.github.anzar-ahsan-commits/api-shakedown. Turn an OpenAPI spec into WireMock stubs, contract tests and chaos scenarios, on local LLMs. This page covers its container image (ghcr.io/anzar-ahsan-commits/api-shakedown).
Is the API Shakedown MCP server safe to use?
API Shakedown scores 41 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the API Shakedown MCP server expose?
API Shakedown exposes 6 tools: doctor, inspect_spec, generate_harness, list_chaos_scenarios, activate_chaos, deactivate_chaos. Their descriptions and schemas cost roughly 295 tokens of context every time the server is loaded.
Is the API Shakedown MCP server still maintained?
API Shakedown is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the API Shakedown MCP server under?
API Shakedown declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.