Skip to main content
Glama
anzar-ahsan-commits

api-shakedown

by anzar-ahsan-commits
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to api-shakedown

No user-submitted related servers found.

    Related Servers

    • Dev MCP Server

      powerducklab
      A
      license
      Not graded
      quality
      B
      maintenance
      Gives AI coding agents dereferenced OpenAPI facts about the backend being implemented, and verifies that implementation against a local server via ping probes, single requests, contract tests, and ordered multi-step scenarios with extraction and assertions. It also spins up loopback mocks for missing dependencies and derives a relational data model from the spec, reconciling it with optional live database evidence and emitting additive SQL that is never executed.
      1,065 npm
      MIT

    • FuzzSpec

      hanifalkauni
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding assistants to inspect OpenAPI specs, fuzz live REST endpoints with boundary and adversarial vectors, replay failing anomalies deterministically without AI tokens, and scaffold OpenAPI specs from source routes.
      Apache 2.0
    • fetchsandbox-mcp by fetchsandbox

      fetchsandbox-mcpofficial

      fetchsandbox
      A
      license
      A
      quality
      A
      maintenance
      A deterministic eval engine for coding agents. Your agent claims it fixed the bug—this checks it. The same scenario runs twice against a sandbox of the services your code calls, with failures injected on purpose. It must fail on the old code and pass on the new. The verdict is an exit code, not a model's opinion. Every run leaves a receipt.
      16
      2,309 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a clearly distinct step: provider health check (doctor), spec loading/validation (inspect_spec), harness generation (generate_harness), and scenario listing/toggling (list/activate/deactivate_chaos). There is no meaningful overlap between any pair.

    Naming Consistency4/5

    Five of six tools follow a clean snake_case verb_noun pattern (inspect_spec, generate_harness, list_chaos_scenarios, activate_chaos, deactivate_chaos). The lone outlier 'doctor' is a bare noun, a minor but visible deviation from the otherwise consistent convention.

    Tool Count5/5

    Six tools is well-scoped for a focused chaos-testing pipeline, with each tool mapping to a necessary step from provider check to scenario toggling. Nothing feels padded or missing at the count level.

    Completeness4/5

    The surface covers the core lifecycle: verify provider, inspect spec, generate harness, and toggle scenarios. Minor gaps exist around harness execution/teardown (no explicit start/stop/reset of WireMock, and deactivate is all-or-nothing), but these are workable around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources