SupaForge
NPM · @AKAL/SUPAFORGE
Find and fix drift between Supabase environments: schema, RLS, roles, auth, storage and more.
Available components
Last scanned (1 day ago)
Scores higher than 79% of npm servers
Category Databases
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 Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 41 of 164 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to akalsoftware/supaforge). View diagnostics → Pass
- 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 Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 658 tokens (~82/item across 8 items; 5 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 16 Oct 26 0
- Package version: 0.0.34 → 0.0.35 functional
- 15 Oct 26 +33
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 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 functional
- 14 Oct 26 0
- 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). security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 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 functional
- 13 Oct 26 50
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 16 Oct 2026 · Analysed npm/@akal/supaforge@0.0.35
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | akalsoftware/supaforge |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/akalsoftware/supaforge/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 3270540355 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:94d0fa533933fc48fff2b2b1d0727a2747d2b0e668b93e09fe1b0ecf8683997a1c9342a7309da3ec06c723f10966022f2764498dec6f7789f590b0054 |
Background: How many MCP packages publish verified provenance →
Dependencies 164 packages
| Packages resolved | 164 |
|---|---|
| Stale | 41 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
apply_fixes ~161
Apply SQL fixes to resolve drift detected by scan_drift. Previews by default — pass dryRun=false to actually write to the target database.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
create_migration ~118
Capture a snapshot and generate a migration file containing the diff against the previous snapshot. Migration files are stored under .supaforge/migrations/.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
get_check_result ~58
Retrieve the result for a specific check from the most recent scan_drift call. Returns issues, status, and duration for the named check.
| Name | Type | Req | Description |
|---|---|---|---|
| check | string | yes | The check name to retrieve (e.g. "rls-coverage"). |
No output schema declared.
No examples provided.
scan_drift ~180
Scan for drift between Supabase environments and return a structured report. Results include per-check status, issues with SQL fixes, and a health score.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
take_snapshot ~98
Capture a point-in-time snapshot of a Supabase environment. Snapshots are stored under .supaforge/snapshots/ and can be used to restore state.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
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.
npm · @akal/supaforge
claude mcp add akalsoftware-supaforge -- npx -y @akal/supaforge
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.