# API Shakedown (pypi · api-shakedown)

Turn an OpenAPI spec into WireMock stubs, contract tests and chaos scenarios, on local LLMs.

- Trust score: 81/100 (high trust)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- oci · `ghcr.io/anzar-ahsan-commits/api-shakedown`: 41/100, [markdown](https://verifymcp.io/servers/anzar-ahsan-commits-api-shakedown/ghcr-io-anzar-ahsan-commits-api-shakedown.md), [page](https://verifymcp.io/servers/anzar-ahsan-commits-api-shakedown/ghcr-io-anzar-ahsan-commits-api-shakedown)
- pypi · `api-shakedown`: 81/100 (this document), [markdown](https://verifymcp.io/servers/anzar-ahsan-commits-api-shakedown/api-shakedown.md), [page](https://verifymcp.io/servers/anzar-ahsan-commits-api-shakedown/api-shakedown)

## Channel facts

- Registry: `pypi`
- Package: `api-shakedown`
- Version: `0.1.3`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-25.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 8 of 75 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to anzar-ahsan-commits/api-shakedown).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 393 tokens (~65/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the API Shakedown MCP server?

API Shakedown runs locally as a PyPI package, launched with uvx api-shakedown. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add anzar-ahsan-commits-api-shakedown -- uvx api-shakedown
```

### Cursor

```json
{
  "mcpServers": {
    "anzar-ahsan-commits-api-shakedown": {
      "command": "uvx",
      "args": [
        "api-shakedown"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "anzar-ahsan-commits-api-shakedown": {
      "command": "uvx",
      "args": [
        "api-shakedown"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add anzar-ahsan-commits-api-shakedown -- uvx api-shakedown
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "anzar-ahsan-commits-api-shakedown": {
      "type": "local",
      "command": [
        "uvx",
        "api-shakedown"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add anzar-ahsan-commits-api-shakedown --command uvx --arg api-shakedown
```

### Hermes

```yaml
mcp_servers:
  anzar-ahsan-commits-api-shakedown:
    command: "uvx"
    args: ["api-shakedown"]
```

### Netclaw

```json
{
  "McpServers": {
    "anzar-ahsan-commits-api-shakedown": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "api-shakedown"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add anzar-ahsan-commits-api-shakedown -t stdio -c uvx -a api-shakedown
```

### Other

```json
{
  "mcpServers": {
    "anzar-ahsan-commits-api-shakedown": {
      "command": "uvx",
      "args": [
        "api-shakedown"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-25 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-24 (score 66, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.1.1 → 0.1.3

### 2026-10-23 (score 80, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-10-15 (score 76)

First indexed and scored.

## MCP tools (6)

### `doctor` (~22 tokens)

Check that the configured LLM provider is reachable and the model is available.

Output parameters:

- `detail` (string)
- `model` (string)
- `ok` (boolean)
- `provider` (string)

### `inspect_spec` (~36 tokens)

Load and validate an OpenAPI spec (file path or http(s) URL) and list its operations.

Input parameters:

- `spec` (string, required)

Output parameters:

- `openapi_version` (string)
- `operations` (array)
- `title` (string)
- `version` (string)
- `warnings` (array)

### `generate_harness` (~123 tokens)

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).

Input parameters:

- `force` (boolean)
- `max_revisions` (integer)
- `offline` (boolean)
- `out_dir` (string, required)
- `review` (boolean)
- `spec` (string, required)

Output parameters:

- `files` (array)
- `next_steps` (array)
- `notes` (array)
- `out_dir` (string)
- `reviews` (array)
- `summary` (object)
- `unresolved` (array)

### `list_chaos_scenarios` (~30 tokens)

List the chaos scenarios of a generated harness.

Input parameters:

- `harness_dir` (string, required)

Output parameters:

- `result` (array)

### `activate_chaos` (~52 tokens)

Turn one chaos scenario on in the harness's running WireMock (others go off).

Input parameters:

- `harness_dir` (string, required)
- `scenario_id` (string, required)
- `wiremock_url` (string)

Output parameters:

- `active`
- `mappings_added` (integer)
- `wiremock_url` (string)

### `deactivate_chaos` (~32 tokens)

Turn all chaos scenarios off: the stubs behave normally again.

Input parameters:

- `wiremock_url` (string)

Output parameters:

- `active`
- `mappings_added` (integer)
- `wiremock_url` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/anzar-ahsan-commits-api-shakedown/api-shakedown#diagnostics

## Score history

- 2026-10-25: 81
- 2026-10-24: 66
- 2026-10-23: 80
- 2026-10-22: 76
- 2026-10-21: 76
- 2026-10-20: 76
- 2026-10-19: 76
- 2026-10-18: 76
- 2026-10-17: 76
- 2026-10-16: 76
- 2026-10-15: 76

## Common questions

### 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 PyPI package (api-shakedown).

### Is the API Shakedown MCP server safe to use?

API Shakedown scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 October 2026. Its build provenance is signed and verified. 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.

## Links

- PyPI project: https://pypi.org/project/api-shakedown/
- Socket report: https://socket.dev/pypi/package/api-shakedown
- Repository: https://github.com/anzar-ahsan-commits/api-shakedown
- Changelog RSS feed: https://verifymcp.io/servers/anzar-ahsan-commits-api-shakedown/api-shakedown.xml
- Changelog JSON feed: https://verifymcp.io/servers/anzar-ahsan-commits-api-shakedown/api-shakedown.json
- HTML version of this page: https://verifymcp.io/servers/anzar-ahsan-commits-api-shakedown/api-shakedown