# SupaForge (npm · @akal/supaforge)

Find and fix drift between Supabase environments: schema, RLS, roles, auth, storage and more.

- Trust score: 83/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-16

## Components

- npm · `@akal/supaforge`: 83/100 (this document), [markdown](https://verifymcp.io/servers/akalsoftware-supaforge/akal-supaforge.md), [page](https://verifymcp.io/servers/akalsoftware-supaforge/akal-supaforge)

## Channel facts

- Registry: `npm`
- Package: `@akal/supaforge`
- Version: `0.0.35`
- 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-16.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 41 of 164 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to akalsoftware/supaforge).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 658 tokens (~82/item across 8 items; 5 tools + 3 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the SupaForge MCP server?

SupaForge runs locally as an npm package, launched with npx -y @akal/supaforge. 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 akalsoftware-supaforge -- npx -y @akal/supaforge
```

### Cursor

```json
{
  "mcpServers": {
    "akalsoftware-supaforge": {
      "command": "npx",
      "args": [
        "-y",
        "@akal/supaforge"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "akalsoftware-supaforge": {
      "command": "npx",
      "args": [
        "-y",
        "@akal/supaforge"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add akalsoftware-supaforge -- npx -y @akal/supaforge
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "akalsoftware-supaforge": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@akal/supaforge"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add akalsoftware-supaforge --command npx --arg -y --arg @akal/supaforge
```

### Hermes

```yaml
mcp_servers:
  akalsoftware-supaforge:
    command: "npx"
    args: ["-y", "@akal/supaforge"]
```

### Netclaw

```json
{
  "McpServers": {
    "akalsoftware-supaforge": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@akal/supaforge"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add akalsoftware-supaforge -t stdio -c npx -a -y @akal/supaforge
```

### Other

```json
{
  "mcpServers": {
    "akalsoftware-supaforge": {
      "command": "npx",
      "args": [
        "-y",
        "@akal/supaforge"
      ]
    }
  }
}
```

## 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-16 (score 83, 0)

- [functional] Package version: 0.0.34 → 0.0.35

### 2026-10-15 (score 83, +33)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.03
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

### 2026-10-14 (score 50, 0)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100
- [functional] Package version: 0.0.33 → 0.0.34

### 2026-10-13 (score 50)

First indexed and scored.

## MCP tools (5)

### `scan_drift` (~180 tokens)

Scan for drift between Supabase environments and return a structured report. Results include per-check status, issues with SQL fixes, and a health score.

Input parameters:

- `checks` (array): Limit scan to specific checks (e.g. ["rls", "rls-coverage"]).
- `configPath` (string): Absolute path to supaforge.config.json. Rejected unless the server was started with --allow-config-path; otherwise the config in the server's own working directory is used.
- `skip` (array): Skip specific checks, the equivalent of the CLI --skip flag. Unioned with checks.exclude from the config file. Use this to avoid a slow or failing layer without editing the project config.
- `source` (string): Source environment name (overrides config default).
- `target` (string): Target environment name (overrides config default).

### `apply_fixes` (~161 tokens)

Apply SQL fixes to resolve drift detected by scan_drift. Previews by default — pass dryRun=false to actually write to the target database.

Input parameters:

- `checks` (array): Apply fixes only for specific checks.
- `configPath` (string): Absolute path to supaforge.config.json. Rejected unless the server was started with --allow-config-path; otherwise the config in the server's own working directory is used.
- `dryRun` (boolean): Preview SQL without executing it. Defaults to true: writing is opt-in here as it is everywhere else in supaforge, where it needs --apply. Pass dryRun=false to actually apply the fixes.
- `source` (string): Source environment name.
- `target` (string): Target environment name.

### `take_snapshot` (~98 tokens)

Capture a point-in-time snapshot of a Supabase environment. Snapshots are stored under .supaforge/snapshots/ and can be used to restore state.

Input parameters:

- `configPath` (string): Absolute path to supaforge.config.json. Rejected unless the server was started with --allow-config-path; otherwise the config in the server's own working directory is used.
- `environment` (string): Environment to snapshot (defaults to config source).

### `create_migration` (~118 tokens)

Capture a snapshot and generate a migration file containing the diff against the previous snapshot. Migration files are stored under .supaforge/migrations/.

Input parameters:

- `configPath` (string): Absolute path to supaforge.config.json. Rejected unless the server was started with --allow-config-path; otherwise the config in the server's own working directory is used.
- `description` (string): Human-readable description for the migration (e.g. "add-rls-to-orders").
- `environment` (string): Environment to snapshot (defaults to config source).

### `get_check_result` (~58 tokens)

Retrieve the result for a specific check from the most recent scan_drift call. Returns issues, status, and duration for the named check.

Input parameters:

- `check` (string, required): The check name to retrieve (e.g. "rls-coverage").

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/akalsoftware-supaforge/akal-supaforge#diagnostics

## Score history

- 2026-10-16: 83
- 2026-10-15: 83
- 2026-10-14: 50
- 2026-10-13: 50

## Common questions

### What is the SupaForge MCP server?

SupaForge is an MCP server listed in the public MCP registry as io.github.akalsoftware/supaforge. Find and fix drift between Supabase environments: schema, RLS, roles, auth, storage and more. This page covers its npm package (@akal/supaforge).

### Is the SupaForge MCP server safe to use?

SupaForge scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. 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 SupaForge MCP server expose?

SupaForge exposes 5 tools: scan_drift, apply_fixes, take_snapshot, create_migration, get_check_result. Their descriptions and schemas cost roughly 615 tokens of context every time the server is loaded.

### Is the SupaForge MCP server still maintained?

SupaForge is still listed as active in the MCP registry. We last reached this channel on 16 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 SupaForge MCP server under?

SupaForge 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

- npm package: https://www.npmjs.com/package/@akal/supaforge
- Socket report: https://socket.dev/npm/package/@akal/supaforge
- Repository: https://github.com/akalsoftware/supaforge
- Website: https://supaforge.dev/
- Changelog RSS feed: https://verifymcp.io/servers/akalsoftware-supaforge/akal-supaforge.xml
- Changelog JSON feed: https://verifymcp.io/servers/akalsoftware-supaforge/akal-supaforge.json
- HTML version of this page: https://verifymcp.io/servers/akalsoftware-supaforge/akal-supaforge