Home / MCP registry index / app.forgeengine/forge

Forge Engine

app.forgeengine/forge in the official MCP registry. Endpoint https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp. Source: github.com/alongkornonline2019/forge-mcp.

The registry describes it as: Design spec + milestones AI coding agents read before building; drift flagged, changes reviewed.

We read its 54 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

get_help get_workflow import_from_code design_ui_from_systems post_log get_project_context list_projects get_project_meta trace_ui_from_image get_stale resync_from_idea get_design_document set_design_overview get_briefing get_system list_systems get_build_region report_drift get_history get_impact get_rejections resolve_rejection list_screens get_screen get_screen_image update_element withdraw_proposal delete_entity dedupe reorder list_milestones get_milestone list_activity get_inbox search propose_system propose_context propose_dna update_system get_balance propose_balance_table propose_balance_board propose_milestone report_milestone_progress report_build_status propose_flow_edge propose_element propose_screen report_screen_status rename_screen update_milestone add_task next_task update_task

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/app-forgeengine-forge/badge.svg)](https://lazaretto.dev/mcp-registry/app-forgeengine-forge)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.