SPARDA logo

SPARDA

Compiles backend behavior into a deterministic graph to detect unsafe AI edits and optionally expose a running app through MCP.

Install SPARDA

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "sparda": {
      "command": "npx",
      "args": [
        "-y",
        "sparda-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y sparda-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 8d ago.

Overview

SPARDA MCP server connects AI clients to a running application through a generated MCP bridge, while its CLI compiles backend routes, queries, mutations, guards, and side effects into a Unified Behavior Graph. Commands such as `prove`, `apocalypse`, and `gate` check coverage, invariants, guard changes, and deployment risks locally without an API key. Use it when AI-generated backend edits need deterministic safety checks or when an agent needs access to a live application through MCP. The MCP runtime is optional; the prover and graph compiler can be used independently.

Use cases

  • Detect guard-removing AI edits before they land
  • Gate backend deployments on verified behavior
  • Compile supported applications into a behavior graph
  • Expose a running application to Claude through MCP

Key features

  • Deterministic offline behavior analysis
  • Unified Behavior Graph compilation
  • Baseline-to-edit regression checks
  • Deployment and CI gating
  • Optional live MCP bridge
  • Replay and proof artifacts

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · sparda-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars8Stargazers on the source repository.
npm downloads795Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How SPARDA works

What SPARDA MCP server does

SPARDA MCP server is the optional runtime layer of SPARDA's backend analysis system. SPARDA first compiles an application into a Unified Behavior Graph (UBG), stored as .sparda/ubg.json under the SBIR specification. The graph represents routes, database queries, state changes, guards, and side effects in a language-agnostic form.

The wider CLI can then inspect that graph before deployment. prove produces a combined proof and coverage verdict, apocalypse acts as a deployment gate, and gate compares the graph before and after an edit. A removed guard can therefore be detected as a behavior regression rather than only as a text diff. heal can accept a fix only when replay, verification, and safety checks continue to pass.

The optional MCP mode exposes a running application to AI clients through a generated bridge. It is separate from the core proving workflow: the graph compiler and verification commands do not require an MCP client.

How it works

Run init from the application directory to scan routes, generate a marked /mcp router, inject it into the application, create sparda.json, and save a backup. The generated changes are reversible. After the application is running, dev starts the bridge and serves the graph as MCP tools for a connected client.

For safety checks, SPARDA parses supported backend structures and compiles them into the UBG. Native compilation is documented for Express, FastAPI, Flask, Next.js, NestJS, and Medusa; OpenAPI can be used for other stacks. Each command operates on the compiled graph rather than relying only on source-text patterns.

gate --arm records a baseline, while gate --hook checks a later edit and returns exit code 2 when the hook detects a regression. Results can also be emitted as JSON, Markdown, SARIF, an HTML dossier, or an SVG badge, depending on the command.

Setup and configuration

The primary commands run through npx sparda-mcp, including prove, apocalypse, gate, init, and dev. The repository requires Node.js 18 or newer. The documented workflow does not require an API key, cloud account, or external service.

For the MCP runtime, run npx sparda-mcp init in the app directory, start the application, then run npx sparda-mcp dev. init prints a client configuration block using the application path as the working directory. The README specifically documents configuration for Claude Desktop and says Claude Code connects to the same bridge.

Tools and capabilities

  • Compile supported backends into a UBG.
  • Prove coverage, premises, guards, invariants, transactions, and aggregate boundaries.
  • Compare baseline and edited behavior graphs with gate.
  • Replay recorded production requests with timeless and export bugs as tests.
  • Serve the compiled graph over HTTP with mirror.
  • Generate badges, reports, JSON, Markdown, and SARIF output.

Limitations and notes

SPARDA reports PROVEN (PARTIAL) when it can inspect only part of an application, and reports PREMISE NOT VERIFIED when it cannot establish that the whole application was examined.

The MCP bridge is optional and requires a running application after initialization. The system is local and deterministic, but its conclusions depend on the code and application behavior available to the compiler and graph.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about SPARDA

SPARDA is an MCP server that connects AI clients to a running application through a generated bridge, while its broader CLI compiles backend behavior into a graph. Its main commands include prove, apocalypse, gate, heal, badge, dossier, ubg, timeless, mirror, init, and dev.

Run `npx sparda-mcp init` in the application directory, then start the application and run `npx sparda-mcp dev`. The repository documents Node.js 18 or newer and says the initialization step generates the MCP router, writes `sparda.json`, creates a backup, and prints client configuration.

Yes, Claude Code can connect to the same bridge started by `sparda-mcp dev`. The repository also documents a Claude Code plugin that runs `npx -y sparda-mcp gate --hook` after edit and write operations, allowing guard-removing edits to be blocked with the documented hook exit code.

Use `sparda gate` with a baseline: arm the guarded version with `sparda gate --arm`, then run the hook workflow on the edited version. SPARDA compares behavior graphs and can report a removed guard, with `--hook` returning exit code 2 for the documented Claude Code edit loop.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSPARDA AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/sparda?style=directory)](https://allmcps.com/mcp/sparda)
HTML Embed
<a href="https://allmcps.com/mcp/sparda"><img src="https://allmcps.com/api/badge/sparda?style=directory" alt="SPARDA on AllMCPs" /></a>