Forge Engine MCP server
app.forgeengine/forgeforgeengine.appstreamable-httpv0.2.0Scanned
Design spec + milestones AI coding agents read before building; drift flagged, changes reviewed.
54 tools: 3 can delete or cancel things, 1 do something that can't be undone, 26 change things and 24 only read.
- Reads private data · 11
- Reads text others write · 6
- Can send data out · 2
- 4 findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here can delete or cancel things and 1 does something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Forge Engine MCP server can do
The Forge Engine MCP server is published by forgeengine.app, a domain the MCP Registry verified. It has 54 tools. It can delete or cancel things (3 tools: withdraw_proposal, delete_entity and dedupe), do things that cannot be undone, such as sending, paying or publishing (propose_flow_edge) and create or change data (26 tools: get_workflow, import_from_code, design_ui_from_systems, post_log and 22 more). 24 tools only read.
11 tools read private data (get_workflow, get_design_document, get_briefing and 8 more); 6 tools bring in text other people can write (get_briefing, get_system, get_impact and 3 more); 2 tools can send data out of your system (post_log and propose_flow_edge). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 4 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 0.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
54 tools
Deletes or cancels 3Claude Code: deny
dedupeRemove duplicate-named entries (keep first) — DIRECT, destructive.No findings
Why it is in this group
- The description's first verb is "remove": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Remove duplicate-named entries (keep first) — DIRECT, destructive.
Annotations the server declares
- destructiveHint: true
- forgeTier: direct-destructive
delete_entityPROPOSE a delete → Inbox (owner adopts; nothing deleted now).No findings
Why it is in this group
- The name "delete_entity" says "delete": a word for removing or ending something.
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it PROPOSE a delete → Inbox (owner adopts; nothing deleted now). id preferred or exact name; flow_edge may use from+to.
Annotations the server declares
- destructiveHint: true
- forgeTier: direct-destructive
withdraw_proposalRemove YOUR OWN still-pending Inbox item (id from the propose response / get_inbox).1 finding
Why it is in this group
- The name "withdraw_proposal" says "withdraw": a word that usually means money moves, which cannot be taken back.
- The description's first verb is "remove": a word for removing or ending something.
- The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.
Findings
- Warn
The server marks "withdraw_proposal" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"destructiveHint":false}; The name "withdraw_proposal" says "withdraw": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it Remove YOUR OWN still-pending Inbox item (id from the propose response / get_inbox).
Annotations the server declares
- destructiveHint: false
- forgeTier: direct-edit
Can't be undone 1Claude Code: ask
propose_flow_edgeSECONDARY (user-driven UI): propose a link between two existing screens → Inbox.Can send data outNo findings
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it SECONDARY (user-driven UI): propose a link between two existing screens → Inbox.
Annotations the server declares
- destructiveHint: false
- forgeTier: propose-inbox
Changes things 26Claude Code: ask
add_taskAdd a task to a milestone — DIRECT.No findings
Why it is in this group
- The name "add_task" says "add": a word for a change.
Description, as the server wrote it Add a task to a milestone — DIRECT. assignee:"me" claims on creation.
Annotations the server declares
- destructiveHint: false
- forgeTier: direct-edit
design_ui_from_systemsRecipe to design the UI from Systems (user request only): steps + batch id — confirm canvas aspect, then screens + PLACED elements + edges in one batch.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Recipe to design the UI from Systems (user request only): steps + batch id — confirm canvas aspect, then screens + PLACED elements + edges in one batch.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
get_project_metaSTART HERE.1 finding
Why it is in this group
- The name "get_project_meta" says "get": a word for reading.
- The description's first verb is "start": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "get_project_meta" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "get_project_meta" says "get": a word for reading.
Description, as the server wrote it START HERE. Tiny overview: counts, members, task claims + working_now (avoid collisions), forge_workflow_version.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
get_workflowRun FIRST in a new repo (no project): first-connect routine + the working-agreement block to ADD to AGENTS.md/CLAUDE.md now (tell the user in one line; remove if they object).Reads private data1 finding
Why it is in this group
- The name "get_workflow" says "get": a word for reading.
- The description's first verb is "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- private-dataThe description's first sentence says "repo": it reads repositories.
Findings
- Warn
The server marks "get_workflow" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "get_workflow" says "get": a word for reading.
Description, as the server wrote it Run FIRST in a new repo (no project): first-connect routine + the working-agreement block to ADD to AGENTS.md/CLAUDE.md now (tell the user in one line; remove if they object).
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
import_from_codeOne-command codebase import: recipe + batch id — propose one Context overview + one System per real module; the owner adopts all at once.1 finding
Why it is in this group
- The name "import_from_code" says "import": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "import_from_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "import_from_code" says "import": a word for a change.
Description, as the server wrote it One-command codebase import: recipe + batch id — propose one Context overview + one System per real module; the owner adopts all at once.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
next_taskDISPATCHER (multi-agent): atomically pick + claim the next task to build — walks milestones in order, skips human-only tasks and any task whose systems share code files with a task…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it DISPATCHER (multi-agent): atomically pick + claim the next task to build — walks milestones in order, skips human-only tasks and any task whose systems share code files with a task another agent already holds or is actively touching, so parallel agents spread out instead of colliding. Returns the claimed task + systems, or why none is free. dry_run:true peeks without claiming.
Annotations the server declares
- destructiveHint: false
- forgeTier: direct-edit
post_logAppend a build-log entry to Activity — what you built/decided (commit-note style).Can send data outNo findings
Why it is in this group
- The name "post_log" says "post": a word for a change.
What it can reach
- outboundThe name "post_log" says "post": it sends or publishes something to other people.
Description, as the server wrote it Append a build-log entry to Activity — what you built/decided (commit-note style).
Annotations the server declares
- destructiveHint: false
- forgeTier: direct-edit
propose_balance_boardPropose a node board → Inbox.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Propose a node board → Inbox. Kinds const|formula|item|sheet|loadout|picker|pool|process|note|frame; formulas reference blocks by NAME; omit x/y = auto-layout. Adopting REPLACES same-named.
Annotations the server declares
- destructiveHint: false
- forgeTier: propose-inbox
propose_balance_tablePropose a stat-doc TABLE → Inbox.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Propose a stat-doc TABLE → Inbox. csv (header; `key%` = percent; first column = name) OR schema+rows. Adopting REPLACES same-named.
Annotations the server declares
- destructiveHint: false
- forgeTier: propose-inbox
propose_contextPropose a new/updated Idea note → Inbox.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Propose a new/updated Idea note → Inbox. Title-match to update; send the COMPLETE revised text. Set resync:true ONLY when you rewrote the note FROM the current systems (get_stale lists notes the systems have moved past) — it stops the adopted note from immediately nagging to re-generate the systems it was just written from.
Annotations the server declares
- destructiveHint: false
- forgeTier: propose-inbox
propose_dnaPropose Project DNA and/or Tech Notes → Inbox (at least one).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Propose Project DNA and/or Tech Notes → Inbox (at least one).
Annotations the server declares
- destructiveHint: false
- forgeTier: propose-inbox
propose_elementSECONDARY (user-driven UI): propose an element onto a screen → Inbox.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it SECONDARY (user-driven UI): propose an element onto a screen → Inbox. ALWAYS pass x/y/w/h (px on the screen's `resolution` from get_screen); no coords = unplaced pile.
Annotations the server declares
- destructiveHint: false
- forgeTier: propose-inbox
propose_milestonePropose a NEW milestone (+ optional tasks) → Inbox.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Propose a NEW milestone (+ optional tasks) → Inbox.
Annotations the server declares
- destructiveHint: false
- forgeTier: propose-inbox
propose_screenSECONDARY (user-driven UI): propose a NEW screen → Inbox.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it SECONDARY (user-driven UI): propose a NEW screen → Inbox. parent = popup over that screen; purpose grounds AI suggestions. Whole UI? design_ui_from_systems first.
Annotations the server declares
- destructiveHint: false
- forgeTier: propose-inbox
propose_systemPropose a NEW system → Inbox.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Propose a NEW system → Inbox. spec = ## Goal / ## Boundary (Owns · Doesn't own) / ## Acceptance. Exists? use update_system. (Alias: create_proposal.)
Annotations the server declares
- destructiveHint: false
- forgeTier: propose-inbox
rename_screenRename a screen IN PLACE — DIRECT; links/elements follow (id-referenced).No findings
Why it is in this group
- The name "rename_screen" says "rename": a word for a change.
Description, as the server wrote it Rename a screen IN PLACE — DIRECT; links/elements follow (id-referenced).
Annotations the server declares
- destructiveHint: false
- forgeTier: direct-edit
reorderReorder milestones / tasks / elements — DIRECT.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Reorder milestones / tasks / elements — DIRECT. order = ids in new order; omitted keep relative order.
Annotations the server declares
- destructiveHint: false
- forgeTier: direct-edit
report_driftFlag CODE DRIFT — mapped files no longer match the repo.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Flag CODE DRIFT — mapped files no longer match the repo. Advisory; a fresh report_build_status clears it.
Annotations the server declares
- destructiveHint: false
- forgeTier: direct-edit
report_milestone_progressMark existing-milestone tasks done → Inbox progress card (owner adopts the ticks).No findings
Why it is in this group
- The description's first verb is "mark": a word for a change.
Description, as the server wrote it Mark existing-milestone tasks done → Inbox progress card (owner adopts the ticks).
Annotations the server declares
- destructiveHint: false
- forgeTier: propose-inbox
resync_from_ideaThe recipe for re-syncing ONE changed Idea note into the specs that depend on it — the same scoped job the app's "Re-sync N systems" button does, minus the button.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it The recipe for re-syncing ONE changed Idea note into the specs that depend on it — the same scoped job the app's "Re-sync N systems" button does, minus the button. Returns the note, the affected specs in full, and exactly how to send the result back. You do the writing; it lands in the owner's Inbox to ADOPT. CRUCIAL: send updates with `resync:true`, or the owner adopts your fix and the design still reports it as stale.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
set_design_overviewWrite the Design Document's Overview — the human-readable page a new team member reads first.No findings
Why it is in this group
- The name "set_design_overview" says "set": a word for a change.
Description, as the server wrote it Write the Design Document's Overview — the human-readable page a new team member reads first. WRITES DIRECTLY (no Inbox): it is a derived, clearly-labelled AI summary, not design truth, and the owner can clear or rewrite it in one click. HARD RULES, same as the in-app button: use ONLY facts stated in the design (call get_design_document with for_summary:true first); invent no mechanics, numbers or names; describe, never evaluate; write in the design's dominant language. Structure: `### What this is` · `### The core loop` · `### How the systems fit` (which system feeds which — the part a raw spec list cannot give) · `### Edges` (ONLY if the design states scope limits / open questions). 250-400 words, no top-level heading. Forge stamps the project version it was compiled from, so the owner is told when the design has moved past it.
Annotations the server declares
- destructiveHint: false
- forgeTier: direct-edit
trace_ui_from_imageSECONDARY (user-driven UI): turn a screen's REFERENCE IMAGE into placed elements.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it SECONDARY (user-driven UI): turn a screen's REFERENCE IMAGE into placed elements. Returns the image itself plus the recipe — the canvas resolution, the fraction→pixel conversion that stops coordinates landing wrong, and what is already on the screen so a second pass updates instead of duplicating. You look at the picture and send back propose_element / update_element with x/y/w/h; it all lands in the owner's Inbox. Use when the user wants the wireframe to match a screenshot or mockup they uploaded.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
update_elementMove/resize/relabel an element — DIRECT, live.No findings
Why it is in this group
- The name "update_element" says "update": a word for a change.
Description, as the server wrote it Move/resize/relabel an element — DIRECT, live. element_id (preferred) or screen+label; x+y also places an unplaced one.
Annotations the server declares
- destructiveHint: false
- forgeTier: direct-edit
update_milestoneEdit milestone goal/weeks/difficulty/name — DIRECT.No findings
Why it is in this group
- The name "update_milestone" says "update": a word for a change.
Description, as the server wrote it Edit milestone goal/weeks/difficulty/name — DIRECT. new_name renames (never delete+recreate).
Annotations the server declares
- destructiveHint: false
- forgeTier: direct-edit
update_systemPropose a system UPDATE → Inbox diff.No findings
Why it is in this group
- The name "update_system" says "update": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- forgeTier: propose-inbox
update_taskEdit a task or CLAIM it — DIRECT.No findings
Why it is in this group
- The name "update_task" says "update": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- destructiveHint: false
- forgeTier: direct-edit
Only reads 24Show 24 read-only tools
get_balanceRead Balance Lab: stat tables, boards with EVALUATED values, scenarios.Reads private dataNo findings
Why it is in this group
- The name "get_balance" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "table": it reads databases.
Description, as the server wrote it Read Balance Lab: stat tables, boards with EVALUATED values, scenarios.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
get_briefingONE-CALL orientation before you build: pass `files` you're about to edit (or a `task`) → the systems that own them, each with Goal + Acceptance + build status/files/last_commit/dri…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_briefing" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
- private-dataThe input names a file (input.files), and the tool reads: it reads files.
- untrusted-inputThe description's first sentence says "inbox": it reads inbound email, which other people can write.
Description, as the server wrote it ONE-CALL orientation before you build: pass `files` you're about to edit (or a `task`) → the systems that own them, each with Goal + Acceptance + build status/files/last_commit/drift + coupled_systems (code neighbors an edit may break) + pending Inbox changes + recent decisions, plus open-rejection count, who's active, `recent_changes` (what happened since you were last here — a session handoff), and a task to claim. Replaces the get_project_meta→get_system→get_build_region dance.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
get_build_regionSystem→code map per built system: implementing files, status, drift flag, last_commit, and acceptance-evidence COUNTS.Reads private dataNo findings
Why it is in this group
- The name "get_build_region" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
Description, as the server wrote it System→code map per built system: implementing files, status, drift flag, last_commit, and acceptance-evidence COUNTS. Mapped files gone from the repo? report_drift. Pass `system:"<name|id>"` for ONE system plus the full text of its acceptance criteria (omitted from the map — it is the bulk of the payload). Big projects come back paged: the body says 'page N of M', call again with `page: N+1`.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
get_design_documentThe WHOLE design as one readable document — Vision (+ Project DNA) → every System spec → reference notes, compiled deterministically from the current design.Reads private dataNo findings
Why it is in this group
- The name "get_design_document" says "get": a word for reading.
What it can reach
- private-dataThe name "get_design_document" says "get" and "document": it reads documents.
- private-dataThe description's first sentence says "document": it reads documents.
Description, as the server wrote it The WHOLE design as one readable document — Vision (+ Project DNA) → every System spec → reference notes, compiled deterministically from the current design. Read this to understand a project end-to-end instead of walking list_systems → get_system N times. Returns markdown plus the project `version` it was compiled from. Long designs come back PAGED — the header says 'part N of M', call again with `page: N+1` for the rest. Pass `for_summary: true` to get the condensed projection instead (every system's Goal + Boundary, tables stripped, one page) — that is what you should summarize from.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
get_helpForge how-to on demand (no project needed): propose→adopt, what a System is, Balance Lab formats, sign-in.No findings
Why it is in this group
- The name "get_help" says "get": a word for reading.
Description, as the server wrote it Forge how-to on demand (no project needed): propose→adopt, what a System is, Balance Lab formats, sign-in. Call when unsure.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
get_historyDESIGN MEMORY: recorded decisions/logs/rejections with who/when.No findings
Why it is in this group
- The name "get_history" says "get": a word for reading.
Description, as the server wrote it DESIGN MEMORY: recorded decisions/logs/rejections with who/when. Read BEFORE changing a system's direction; empty = no recorded WHY — don't invent one.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
get_impactBLAST RADIUS of a system (deterministic): upstream context, siblings, dependent screens/milestones, files, code-coupled systems, pending Inbox, recent activity.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_impact" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
- untrusted-inputThe description's first sentence says "inbox": it reads inbound email, which other people can write.
Description, as the server wrote it BLAST RADIUS of a system (deterministic): upstream context, siblings, dependent screens/milestones, files, code-coupled systems, pending Inbox, recent activity. Run BEFORE changing it.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
get_inboxPENDING Inbox (the owner's triage queue).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_inbox" says "get": a word for reading.
What it can reach
- private-dataThe name "get_inbox" says "get" and "inbox": it reads mail.
- private-dataThe description's first sentence says "inbox": it reads mail.
- untrusted-inputThe name "get_inbox" says "get" and "inbox": it reads inbound email, which other people can write.
- untrusted-inputThe description's first sentence says "inbox": it reads inbound email, which other people can write.
Description, as the server wrote it PENDING Inbox (the owner's triage queue). Check BEFORE proposing — avoid duplicates. Read-only.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
get_milestoneONE milestone: goal, weeks, difficulty, systems, every task (id/name/done/status/effort).No findings
Why it is in this group
- The name "get_milestone" says "get": a word for reading.
Description, as the server wrote it ONE milestone: goal, weeks, difficulty, systems, every task (id/name/done/status/effort).
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
get_project_contextFULL design dump — LARGE, last resort; prefer get_project_meta + list_*/get_*/search.No findings
Why it is in this group
- The name "get_project_context" says "get": a word for reading.
Description, as the server wrote it FULL design dump — LARGE, last resort; prefer get_project_meta + list_*/get_*/search.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
get_rejectionsOwner's DECLINED list — check at session start; follow each entry's guidance, then resolve_rejection(title).No findings
Why it is in this group
- The name "get_rejections" says "get": a word for reading.
Description, as the server wrote it Owner's DECLINED list — check at session start; follow each entry's guidance, then resolve_rejection(title).
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
get_screenONE screen's layout: canvas `resolution` (use THESE px), elements x/y/w/h, links, popups.No findings
Why it is in this group
- The name "get_screen" says "get": a word for reading.
Description, as the server wrote it ONE screen's layout: canvas `resolution` (use THESE px), elements x/y/w/h, links, popups. Read before editing a screen. has_reference_image:true → get_screen_image shows you the actual image.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
get_screen_imageA screen's reference image (HUD background) as an actual IMAGE you can see — reads the stored file inline (signed-URL fallback past 4MB).Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_screen_image" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it A screen's reference image (HUD background) as an actual IMAGE you can see — reads the stored file inline (signed-URL fallback past 4MB).
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
get_staleWhat has drifted between the Idea lane and the System Specs — the design's own out-of-sync list, computed deterministically (no AI, no tokens).No findings
Why it is in this group
- The name "get_stale" says "get": a word for reading.
Description, as the server wrote it What has drifted between the Idea lane and the System Specs — the design's own out-of-sync list, computed deterministically (no AI, no tokens). Three kinds: Idea notes edited since the systems were generated from them (with the systems each one touches), Idea notes whose prose the systems have moved past, and specs whose stamped source fingerprint no longer matches. Read this before assuming the design is coherent; fix the first kind with resync_from_idea.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
get_systemONE system's full spec (Goal/Boundary/Acceptance, markdown, sources, status) + pending Inbox changes touching it.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_system" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "inbox": it reads mail.
- untrusted-inputThe description's first sentence says "inbox": it reads inbound email, which other people can write.
Description, as the server wrote it ONE system's full spec (Goal/Boundary/Acceptance, markdown, sources, status) + pending Inbox changes touching it.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
list_activityChange history {who, change, entity, kind, when}, newest first; filter kind/who/query.No findings
Why it is in this group
- The name "list_activity" says "list": a word for reading.
Description, as the server wrote it Change history {who, change, entity, kind, when}, newest first; filter kind/who/query.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
list_milestonesAll milestones, compact: id, name, weeks, order, done/total.No findings
Why it is in this group
- The name "list_milestones" says "list": a word for reading.
Description, as the server wrote it All milestones, compact: id, name, weeks, order, done/total.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
list_projectsProjects your key reaches (id, name, role); pass an id as project_id to switch.No findings
Why it is in this group
- The name "list_projects" says "list": a word for reading.
Description, as the server wrote it Projects your key reaches (id, name, role); pass an id as project_id to switch.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
list_screensAll screens, compact: id, name, purpose, status.No findings
Why it is in this group
- The name "list_screens" says "list": a word for reading.
Description, as the server wrote it All screens, compact: id, name, purpose, status.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
list_systemsAll systems, compact: id, name, status, 1-line goal.No findings
Why it is in this group
- The name "list_systems" says "list": a word for reading.
Description, as the server wrote it All systems, compact: id, name, status, 1-line goal.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
report_build_statusReport a SYSTEM's status (todo|in-progress|implemented) — DIRECT, live.Reads private dataNo findings
Why it is in this group
- The name "report_build_status" says "status": a word for reading.
What it can reach
- private-dataThe input names a file (input.files), and the tool reads: it reads files.
Description, as the server wrote it Report a SYSTEM's status (todo|in-progress|implemented) — DIRECT, live. ALWAYS pass files (full list — it REPLACES); non-todo with no files shows done-but-EMPTY. 'implemented' counts as VERIFIED only when every UNIT-TESTABLE ## Acceptance bullet is backed via evidence[{criterion,proof}]; a bullet tagged [manual]/[e2e]/[ui]/[wip] is EXEMPT (verified by manual/e2e). Otherwise it's a CLAIM (verified:false) and the response names the unbacked criteria. TWO tiers: VERIFIED = a test is NAMED; GREEN (guarantee) = you RAN the test and reported `passed:true` on the evidence — green goes stale after 21 days, so re-run to keep it.
Annotations the server declares
- destructiveHint: false
- forgeTier: direct-edit
report_screen_statusReport a SCREEN's status (todo|in-progress|implemented) → Inbox.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "report_screen_status" says "status": a word for reading.
What it can reach
- private-dataThe description's first sentence says "inbox": it reads mail.
- untrusted-inputThe description's first sentence says "inbox": it reads inbound email, which other people can write.
Description, as the server wrote it Report a SCREEN's status (todo|in-progress|implemented) → Inbox.
Annotations the server declares
- destructiveHint: false
- forgeTier: propose-inbox
resolve_rejectionReport you REVERTED a declined change (unlocks the owner's Clear).No findings
Why it is in this group
- The name "resolve_rejection" says "resolve": a word for reading.
Description, as the server wrote it Report you REVERTED a declined change (unlocks the owner's Clear). Call after realigning the build.
Annotations the server declares
- destructiveHint: false
- forgeTier: direct-edit
searchKeyword search — compact hits {kind, id, name} + snippet.No findings
Why it is in this group
- The name "search" says "search": a word for reading.
Description, as the server wrote it Keyword search — compact hits {kind, id, name} + snippet.
Annotations the server declares
- readOnlyHint: true
- forgeTier: read
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
132 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 2 outbound tools breaks every one.
- Reads private data11
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write6
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__forge__post_log",
"mcp__forge__propose_flow_edge"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:29 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 30
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 30 tools that change things (3 destructive, 1 irreversible, 26 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp: tools/list returned 54 tools to an anonymous client, including withdraw_proposal (destructive), delete_entity (destructive), dedupe (destructive), propose_flow_edge (irreversible), get_workflow (write) and 25 more
Findings
Matches of fixed checks, with the text they matched.
- Warnget_workflow
The server marks "get_workflow" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "get_workflow" says "get": a word for reading.
- Warnimport_from_code
The server marks "import_from_code" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "import_from_code" says "import": a word for a change.
- Warnget_project_meta
The server marks "get_project_meta" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true}; The name "get_project_meta" says "get": a word for reading.
The server marks "withdraw_proposal" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"destructiveHint":false}; The name "withdraw_proposal" says "withdraw": a word that usually means money moves, which cannot be taken back.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http forge https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcpclaude mcp add --transport http forge https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__forge__get_help",
"mcp__forge__get_project_context",
"mcp__forge__list_projects",
"mcp__forge__get_stale",
"mcp__forge__get_design_document",
"mcp__forge__get_briefing",
"mcp__forge__get_system",
"mcp__forge__list_systems",
"mcp__forge__get_build_region",
"mcp__forge__get_history",
"mcp__forge__get_impact",
"mcp__forge__get_rejections",
"mcp__forge__resolve_rejection",
"mcp__forge__list_screens",
"mcp__forge__get_screen",
"mcp__forge__get_screen_image",
"mcp__forge__list_milestones",
"mcp__forge__get_milestone",
"mcp__forge__list_activity",
"mcp__forge__get_inbox",
"mcp__forge__search",
"mcp__forge__get_balance",
"mcp__forge__report_build_status",
"mcp__forge__report_screen_status"
],
"ask": [
"mcp__forge__get_workflow",
"mcp__forge__import_from_code",
"mcp__forge__design_ui_from_systems",
"mcp__forge__post_log",
"mcp__forge__get_project_meta",
"mcp__forge__trace_ui_from_image",
"mcp__forge__resync_from_idea",
"mcp__forge__set_design_overview",
"mcp__forge__report_drift",
"mcp__forge__update_element",
"mcp__forge__reorder",
"mcp__forge__propose_system",
"mcp__forge__propose_context",
"mcp__forge__propose_dna",
"mcp__forge__update_system",
"mcp__forge__propose_balance_table",
"mcp__forge__propose_balance_board",
"mcp__forge__propose_milestone",
"mcp__forge__report_milestone_progress",
"mcp__forge__propose_flow_edge",
"mcp__forge__propose_element",
"mcp__forge__propose_screen",
"mcp__forge__rename_screen",
"mcp__forge__update_milestone",
"mcp__forge__add_task",
"mcp__forge__next_task",
"mcp__forge__update_task"
],
"deny": [
"mcp__forge__withdraw_proposal",
"mcp__forge__delete_entity",
"mcp__forge__dedupe"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as forge. Review it before you use it.
Capability tags behind 13 rules
- mcp__forge__get_workflow private-data
- mcp__forge__post_log outbound
- mcp__forge__get_design_document private-data
- mcp__forge__get_briefing private-data, untrusted-input
- mcp__forge__get_system private-data, untrusted-input
- mcp__forge__get_build_region private-data
- mcp__forge__get_impact private-data, untrusted-input
- mcp__forge__get_screen_image private-data, untrusted-input
- mcp__forge__get_inbox private-data, untrusted-input
- mcp__forge__get_balance private-data
- mcp__forge__report_build_status private-data
- mcp__forge__propose_flow_edge outbound
- mcp__forge__report_screen_status private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/app.forgeengine/forge/verify?hash=5b6a338b7583c56b08a3c36dad4c8d7dc4a42f37531cf751e463798dd537ce70" | jq -e '.changed == false'Pinned hash 5b6a338b7583, from Nov 10, 2026, 05:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/app.forgeengine/forge/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/app.forgeengine/forge)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:44 UTC.
Forge Engine MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Forge Engine MCP server safe?
- No scan can promise that. What its definitions show: 54 tools, 30 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Forge Engine MCP server delete data?
- Yes. 3 tools can delete, cancel or revoke something: withdraw_proposal, delete_entity and dedupe.
Can the Forge Engine MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: propose_flow_edge.
What tools does the Forge Engine MCP server have?
- 54 tools: 3 destructive, 1 irreversible, 26 write, 24 read. withdraw_proposal, delete_entity, dedupe, propose_flow_edge, get_workflow, import_from_code, design_ui_from_systems, post_log and 46 more.
Does the Forge Engine MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Forge Engine MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): post_log and propose_flow_edge.
Has the Forge Engine MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.