Forge Engine
REMOTE · MMVDABZADCLEBFXYZUDG.SUPABASE.CO
Design spec + milestones AI coding agents read before building; drift flagged, changes reviewed.
Available components
Last scanned (4 hours ago)
Scores higher than 98% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Project Management
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 5630 tokens (~104/item across 54 items; 54 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 69% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 55 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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 6 Aug 26 0
- Authorization: pass → fail ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: good → fair functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 5 Nov 2026 · Probed https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=supabase.co | CN=WE1,O=Google Trust Services,C=US | 24 Oct 2026 | 22 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d2b50611cd88e9c50e4e2231f4d3f059 |
| SANs: supabase.co, *.supabase.co | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mmvdabzadclebfxyzudg.supabase.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| supabase.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp | Verified | 200 | |
| http (plaintext) | http://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp | HTTPS enforced | 301 | https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp |
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 →
update_milestone ~93
Edit milestone goal/weeks/difficulty/name — DIRECT. new_name renames (never delete+recreate).
| Name | Type | Req | Description |
|---|---|---|---|
| difficulty | string | – | "" clears |
| goal | string | – | – |
| id | string | – | Preferred |
| name | string | – | Current name (if no id) |
| new_name | string | – | Rename |
| project_id | string | – | – |
| weeks | number | – | – |
No output schema declared.
No examples provided.
update_system ~204
Propose a system UPDATE → Inbox diff. get_system first; send the FULL revised spec. new_title renames; context_title+context bundles the Idea update. Set resync:true ONLY when you rewrote this spec FROM its upstream Idea (see resync_from_idea) — it re-stamps the staleness signal on adopt.
| Name | Type | Req | Description |
|---|---|---|---|
| acknowledge_rejection | boolean | – | Only after a DECLINED bounce AND asking the user |
| context | string | – | Full revised Idea text |
| context_title | string | – | Idea section to also update |
| id | string | – | Preferred |
| name | string | – | If no id |
| new_title | string | – | Rename in the same card |
| project_id | string | – | – |
| resync | boolean | – | This spec was re-derived from its upstream Idea — re-stamps sourceSig on adopt. Never set it on an ordinary edit. |
| spec | string | yes | Full revised spec markdown |
No output schema declared.
No examples provided.
update_task ~156
Edit a task or CLAIM it — DIRECT. assignee:"me"+status:"in-progress" claims (errors if held; force:true for stale); done:true or assignee:"" releases.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string | – | "me" claims; "" releases |
| done | boolean | – | true releases the claim |
| effort | string | – | "" clears |
| force | boolean | – | Take over a STALE claim only |
| human | boolean | – | true = human-only (next_task/get_briefing skip it); false clears |
| name | string | – | – |
| project_id | string | – | – |
| status | string | – | "" clears |
| task_id | string | yes | From get_milestone |
No output schema declared.
No examples provided.
withdraw_proposal ~47
Remove YOUR OWN still-pending Inbox item (id from the propose response / get_inbox).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The pending item's id |
| project_id | string | – | – |
No output schema declared.
No examples provided.
How do I install the Forge Engine MCP server?
Forge Engine is a hosted endpoint at https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mmvdabzadclebfxyzudg.supabase.co
claude mcp add --transport http app-forgeengine-forge 'https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp'
What is the Forge Engine MCP server?
Forge Engine is an MCP server listed in the public MCP registry as app.forgeengine/forge. Design spec + milestones AI coding agents read before building; drift flagged, changes reviewed. This page covers its hosted endpoint (https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp).
Is the Forge Engine MCP server safe to use?
Forge Engine scores 91 out of 100 on VerifyMCP. 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 Forge Engine MCP server expose?
Forge Engine exposes 54 tools: get_help, get_workflow, import_from_code, design_ui_from_systems, post_log, and 49 more. Their descriptions and schemas cost roughly 5,159 tokens of context every time the server is loaded.
Does the Forge Engine MCP server require authentication?
Yes. Forge Engine asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Forge Engine MCP server still maintained?
Forge Engine is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.