Forge Engine
REMOTE · MMVDABZADCLEBFXYZUDG.SUPABASE.CO · SCANNED AUG 3
Design spec + milestones AI coding agents read before building; drift flagged, changes reviewed.
Available components
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 →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 5539 tokens (~102/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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mmvdabzadclebfxyzudg.supabase.co
claude mcp add --transport http app-forgeengine-forge https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp
[mcp_servers.app-forgeengine-forge] url = "https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-forgeengine-forge": {
"type": "remote",
"url": "https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp",
"enabled": true
}
}
} openclaw mcp add app-forgeengine-forge --url https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp --transport streamable-http
mcp_servers:
app-forgeengine-forge:
url: "https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp" {
"mcpServers": {
"app-forgeengine-forge": {
"type": "http",
"url": "https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +5
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 26 Jul 26 71
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 3 Aug 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 | 28 Jun 2026 | 26 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | 1d2d53f65d874dfb0eead7aab0301afd |
| 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 |
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 Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Protected resource metadata
| Document | https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp |
| Authorisation server | https://mmvdabzadclebfxyzudg.supabase.co/auth/v1 |
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.
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.