_ registry / mcp streamable-http · checked 57m ago

forge

https://mmvdabzadclebfxyzudg.supabase.co

Registry code: 9b9028b094b0113a

api record

Forge is the live design source-of-truth (vision, Systems[Goal/Boundary/Acceptance], screens, milestones, Inbox) a coding agent builds from. You READ the design and PROPOSE changes — proposals + deletes go to the owner's Inbox to ADOPT in the web app at https://forgeengine.app (you can't adopt or hard-delete). Connect with a forge_sk_ key (Bearer token) — generate one in the web app under "Connect a coding agent"; if the user isn't connected, tell them they can either add the key to their MCP config themselves or paste it to you in chat.

Start with get_project_meta; pass project_id (from…

endpoint
https://mmvdabzadclebfxyzudg.supabase.co/functions/v1/forge-mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is forge live?
Yes — it answered the hub's last check (checked 57m ago). It answered 100% of checks over the last 30 days.
Is forge free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does forge have?
54 tools: get_system, list_systems, report_drift, update_milestone, get_balance, get_inbox, search, propose_dna, ….
Is forge safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
245ms

last good check

priced tools
0

of 54 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 54 tools
54 auth-required 54 of 54 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_system auth-required never probed

    ONE system's full spec (Goal/Boundary/Acceptance, markdown, sources, status) + pending Inbox changes touching it.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Preferred"
    },
    "name": {
      "type": "string",
      "description": "If no id"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 16 lines
  • list_systems auth-required never probed

    All systems, compact: id, name, status, 1-line goal.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 8 lines
  • report_drift auth-required never probed

    Flag CODE DRIFT — mapped files no longer match the repo. Advisory; a fresh report_build_status clears it.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Preferred"
    },
    "name": {
      "type": "string",
      "description": "If no id"
    },
    "note": {
      "type": "string",
      "description": "Optional — what drifted"
    },
    "project_id": {
      "type": "string"
    },
    "missing_files": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Paths that no longer exist"
    }
  }
}
    arguments 27 lines
  • update_milestone auth-required never probed

    Edit milestone goal/weeks/difficulty/name — DIRECT. new_name renames (never delete+recreate).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Preferred"
    },
    "goal": {
      "type": "string"
    },
    "name": {
      "type": "string",
      "description": "Current name (if no id)"
    },
    "weeks": {
      "type": "number"
    },
    "new_name": {
      "type": "string",
      "description": "Rename"
    },
    "difficulty": {
      "enum": [
        "easy",
        "medium",
        "hard",
        ""
      ],
      "type": "string",
      "description": "\"\" clears"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 36 lines
  • get_balance auth-required 57m ago

    Read Balance Lab: stat tables, boards with EVALUATED values, scenarios.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "board": {
      "type": "string",
      "description": "One board (omit = all)"
    },
    "project_id": {
      "type": "string"
    },
    "include_rows": {
      "type": "boolean",
      "description": "false = schema only"
    }
  }
}
    arguments 16 lines
  • get_inbox auth-required never probed

    PENDING Inbox (the owner's triage queue). Check BEFORE proposing — avoid duplicates. Read-only.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 8 lines
  • search auth-required never probed

    Keyword search — compact hits {kind, id, name} + snippet.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "kinds": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional: system | context | milestone | task | screen | proposal"
    },
    "query": {
      "type": "string",
      "description": "Text to search for"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 22 lines
  • propose_dna auth-required never probed

    Propose Project DNA and/or Tech Notes → Inbox (at least one).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "dna": {
      "type": "string",
      "description": "Omit to leave unchanged"
    },
    "batch": {
      "type": "string",
      "description": "import_from_code batch id"
    },
    "project_id": {
      "type": "string"
    },
    "tech_notes": {
      "type": "string",
      "description": "Omit to leave unchanged"
    }
  }
}
    arguments 20 lines
  • report_milestone_progress auth-required never probed

    Mark existing-milestone tasks done → Inbox progress card (owner adopts the ticks).

    mcp-tool

    {
  "type": "object",
  "required": [
    "done_tasks"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Preferred"
    },
    "milestone": {
      "type": "string",
      "description": "Milestone name (if no id)"
    },
    "done_tasks": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Task names that are done"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 26 lines
  • get_briefing auth-required 57m ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "task": {
      "type": "string",
      "description": "A task id or name — briefs its milestone's systems instead"
    },
    "files": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Repo-relative paths you're about to touch — mapped to their systems"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 19 lines
  • get_build_region auth-required 57m ago

    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`.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "page": {
      "type": "number",
      "description": "Which page of the map (default 1); the body tells you how many there are"
    },
    "system": {
      "type": "string",
      "description": "One system by name or id — returns its acceptance-criteria detail too"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 16 lines
  • get_help auth-required never probed

    Forge how-to on demand (no project needed): propose→adopt, what a System is, Balance Lab formats, sign-in. Call when unsure.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_workflow auth-required never probed

    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).

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • import_from_code auth-required never probed

    One-command codebase import: recipe + batch id — propose one Context overview + one System per real module; the owner adopts all at once.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 8 lines
  • design_ui_from_systems auth-required never probed

    Recipe to design the UI from Systems (user request only): steps + batch id — confirm canvas aspect, then screens + PLACED elements + edges in one batch.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 8 lines
  • post_log auth-required never probed

    Append a build-log entry to Activity — what you built/decided (commit-note style).

    mcp-tool

    {
  "type": "object",
  "required": [
    "text"
  ],
  "properties": {
    "text": {
      "type": "string",
      "description": "What you did / decided (1–2 sentences)"
    },
    "entity": {
      "type": "string",
      "description": "System/screen/milestone it's about"
    },
    "version": {
      "type": "string",
      "description": "e.g. \"0.379.0\""
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 23 lines
  • get_project_context auth-required never probed

    FULL design dump — LARGE, last resort; prefer get_project_meta + list_*/get_*/search.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 8 lines
  • list_projects auth-required never probed

    Projects your key reaches (id, name, role); pass an id as project_id to switch.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_project_meta auth-required never probed

    START HERE. Tiny overview: counts, members, task claims + working_now (avoid collisions), forge_workflow_version.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 8 lines
  • trace_ui_from_image auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "screen"
  ],
  "properties": {
    "screen": {
      "type": "string",
      "description": "The screen whose reference image to trace (name or id)"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 15 lines
  • get_stale auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 8 lines
  • resync_from_idea auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "note"
  ],
  "properties": {
    "note": {
      "type": "string",
      "description": "The Idea note's title or id (from get_stale)"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 15 lines
  • get_design_document auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "page": {
      "type": "number",
      "description": "Which part of the full document to return (default 1). The header tells you how many parts there are."
    },
    "project_id": {
      "type": "string"
    },
    "for_summary": {
      "type": "boolean",
      "description": "Return the condensed summarization source (all system goals + boundaries, no tables) instead of the full document"
    }
  }
}
    arguments 16 lines
  • set_design_overview auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "summary"
  ],
  "properties": {
    "summary": {
      "type": "string",
      "description": "The Overview in markdown, starting at `### What this is`"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 15 lines
  • get_history auth-required never probed

    DESIGN MEMORY: recorded decisions/logs/rejections with who/when. Read BEFORE changing a system's direction; empty = no recorded WHY — don't invent one.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "number",
      "description": "Default 30, max 100"
    },
    "query": {
      "type": "string",
      "description": "Keyword filter"
    },
    "system": {
      "type": "string",
      "description": "System id or exact name"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 20 lines
  • get_impact auth-required never probed

    BLAST RADIUS of a system (deterministic): upstream context, siblings, dependent screens/milestones, files, code-coupled systems, pending Inbox, recent activity. Run BEFORE changing it.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Preferred"
    },
    "name": {
      "type": "string",
      "description": "If no id"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 16 lines
  • get_rejections auth-required never probed

    Owner's DECLINED list — check at session start; follow each entry's guidance, then resolve_rejection(title).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 8 lines
  • resolve_rejection auth-required never probed

    Report you REVERTED a declined change (unlocks the owner's Clear). Call after realigning the build.

    mcp-tool

    {
  "type": "object",
  "required": [
    "title"
  ],
  "properties": {
    "title": {
      "type": "string",
      "description": "Exactly as get_rejections returned it"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 15 lines
  • list_screens auth-required never probed

    All screens, compact: id, name, purpose, status.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 8 lines
  • get_screen auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Preferred"
    },
    "name": {
      "type": "string",
      "description": "If no id"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 16 lines
  • get_screen_image auth-required never probed

    A screen's reference image (HUD background) as an actual IMAGE you can see — reads the stored file inline (signed-URL fallback past 4MB).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Preferred"
    },
    "name": {
      "type": "string",
      "description": "If no id"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 16 lines
  • update_element auth-required never probed

    Move/resize/relabel an element — DIRECT, live. element_id (preferred) or screen+label; x+y also places an unplaced one.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "h": {
      "type": "number"
    },
    "w": {
      "type": "number"
    },
    "x": {
      "type": "number",
      "description": "px on the screen's canvas"
    },
    "y": {
      "type": "number"
    },
    "note": {
      "type": "string",
      "description": "\"\" clears"
    },
    "type": {
      "type": "string",
      "description": "e.g. button/bar/panel (optional)"
    },
    "label": {
      "type": "string",
      "description": "Current label"
    },
    "screen": {
      "type": "string",
      "description": "With label, if no element_id"
    },
    "system": {
      "type": "string",
      "description": "System it serves"
    },
    "new_label": {
      "type": "string",
      "description": "Rename (optional)"
    },
    "element_id": {
      "type": "string",
      "description": "From get_screen (preferred)"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 49 lines
  • withdraw_proposal auth-required never probed

    Remove YOUR OWN still-pending Inbox item (id from the propose response / get_inbox).

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "The pending item's id"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 15 lines
  • delete_entity auth-required never probed

    PROPOSE a delete → Inbox (owner adopts; nothing deleted now). id preferred or exact name; flow_edge may use from+to.

    mcp-tool

    {
  "type": "object",
  "required": [
    "kind"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Entity/task/element/edge id"
    },
    "to": {
      "type": "string",
      "description": "flow_edge: destination screen"
    },
    "from": {
      "type": "string",
      "description": "flow_edge: source screen"
    },
    "kind": {
      "enum": [
        "system",
        "context",
        "screen",
        "milestone",
        "task",
        "element",
        "flow_edge"
      ],
      "type": "string",
      "description": "What to delete"
    },
    "name": {
      "type": "string",
      "description": "Exact name/title (if no id)"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 40 lines
  • dedupe auth-required never probed

    Remove duplicate-named entries (keep first) — DIRECT, destructive.

    mcp-tool

    {
  "type": "object",
  "required": [
    "kind"
  ],
  "properties": {
    "kind": {
      "enum": [
        "milestones",
        "elements"
      ],
      "type": "string",
      "description": "What to dedupe"
    },
    "screen": {
      "type": "string",
      "description": "For kind=elements"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 23 lines
  • reorder auth-required never probed

    Reorder milestones / tasks / elements — DIRECT. order = ids in new order; omitted keep relative order.

    mcp-tool

    {
  "type": "object",
  "required": [
    "kind",
    "order"
  ],
  "properties": {
    "kind": {
      "enum": [
        "milestones",
        "tasks",
        "elements"
      ],
      "type": "string",
      "description": "What to reorder"
    },
    "order": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Ids in the new order"
    },
    "screen": {
      "type": "string",
      "description": "For kind=elements"
    },
    "milestone": {
      "type": "string",
      "description": "For kind=tasks (name)"
    },
    "project_id": {
      "type": "string"
    },
    "milestone_id": {
      "type": "string",
      "description": "For kind=tasks"
    }
  }
}
    arguments 40 lines
  • list_milestones auth-required never probed

    All milestones, compact: id, name, weeks, order, done/total.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 8 lines
  • get_milestone auth-required never probed

    ONE milestone: goal, weeks, difficulty, systems, every task (id/name/done/status/effort).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Preferred"
    },
    "name": {
      "type": "string",
      "description": "If no id"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 16 lines
  • list_activity auth-required never probed

    Change history {who, change, entity, kind, when}, newest first; filter kind/who/query.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "who": {
      "type": "string",
      "description": "Author email substring (optional)"
    },
    "kind": {
      "type": "string",
      "description": "system | context | milestone | screen (optional)"
    },
    "limit": {
      "type": "number",
      "description": "Default 30, max 200"
    },
    "query": {
      "type": "string",
      "description": "Keyword filter (optional)"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 24 lines
  • propose_system auth-required never probed

    Propose a NEW system → Inbox. spec = ## Goal / ## Boundary (Owns · Doesn't own) / ## Acceptance. Exists? use update_system. (Alias: create_proposal.)

    mcp-tool

    {
  "type": "object",
  "required": [
    "title",
    "spec"
  ],
  "properties": {
    "spec": {
      "type": "string",
      "description": "Markdown: ## Goal / ## Boundary / ## Acceptance"
    },
    "batch": {
      "type": "string",
      "description": "import_from_code batch id"
    },
    "files": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Implementing paths, ONE file per entry"
    },
    "title": {
      "type": "string",
      "description": "System name (Title Case, English)"
    },
    "project_id": {
      "type": "string"
    },
    "derives_from": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Context note title(s) this system derives from → wires provenance (upstream + siblings)"
    },
    "acknowledge_rejection": {
      "type": "boolean",
      "description": "Only after a DECLINED bounce AND asking the user"
    }
  }
}
    arguments 42 lines
  • propose_context auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "title",
    "content"
  ],
  "properties": {
    "batch": {
      "type": "string",
      "description": "import_from_code batch id"
    },
    "title": {
      "type": "string",
      "description": "Match existing to update, or new to add"
    },
    "resync": {
      "type": "boolean",
      "description": "This note was re-derived from the current systems — re-stamps both staleness signals on adopt"
    },
    "content": {
      "type": "string",
      "description": "Complete text, not a delta"
    },
    "project_id": {
      "type": "string"
    },
    "acknowledge_rejection": {
      "type": "boolean",
      "description": "Only after a DECLINED bounce AND asking the user"
    }
  }
}
    arguments 32 lines
  • update_system auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "spec"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Preferred"
    },
    "name": {
      "type": "string",
      "description": "If no id"
    },
    "spec": {
      "type": "string",
      "description": "Full revised spec markdown"
    },
    "resync": {
      "type": "boolean",
      "description": "This spec was re-derived from its upstream Idea — re-stamps sourceSig on adopt. Never set it on an ordinary edit."
    },
    "context": {
      "type": "string",
      "description": "Full revised Idea text"
    },
    "new_title": {
      "type": "string",
      "description": "Rename in the same card"
    },
    "project_id": {
      "type": "string"
    },
    "context_title": {
      "type": "string",
      "description": "Idea section to also update"
    },
    "acknowledge_rejection": {
      "type": "boolean",
      "description": "Only after a DECLINED bounce AND asking the user"
    }
  }
}
    arguments 43 lines
  • propose_balance_table auth-required never probed

    Propose a stat-doc TABLE → Inbox. csv (header; `key%` = percent; first column = name) OR schema+rows. Adopting REPLACES same-named.

    mcp-tool

    {
  "type": "object",
  "required": [
    "title"
  ],
  "properties": {
    "csv": {
      "type": "string",
      "description": "Header + rows; non-numeric = info"
    },
    "rows": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "description": "[{name, atk: 350, …}]"
    },
    "title": {
      "type": "string",
      "description": "Table name"
    },
    "schema": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "description": "[{key, mode: flat|pct|text, base, min, max, desc}]"
    },
    "registry": {
      "type": "boolean",
      "description": "true = the shared Stats registry"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 37 lines
  • propose_balance_board auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name",
    "nodes"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Board name"
    },
    "nodes": {
      "type": "array",
      "items": {
        "type": "object"
      },
      "description": "e.g. {kind:\"formula\",name:\"dmg\",formula:\"atk - mdef\"}"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 23 lines
  • propose_milestone auth-required never probed

    Propose a NEW milestone (+ optional tasks) → Inbox.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "goal": {
      "type": "string",
      "description": "One-line goal (optional)"
    },
    "name": {
      "type": "string",
      "description": "Milestone name"
    },
    "tasks": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Task names (optional)"
    },
    "project_id": {
      "type": "string"
    },
    "acknowledge_rejection": {
      "type": "boolean",
      "description": "Only after a DECLINED bounce AND asking the user"
    }
  }
}
    arguments 30 lines
  • report_build_status auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "status"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Preferred"
    },
    "name": {
      "type": "string",
      "description": "If no id"
    },
    "files": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "ONE file per entry (optional ' — function'); prose → decisions"
    },
    "status": {
      "type": "string",
      "description": "todo | in-progress | implemented"
    },
    "version": {
      "type": "string",
      "description": "e.g. \"0.379.0\""
    },
    "evidence": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "at": {
            "type": "string",
            "description": "ISO time of the pass (defaults to now); green expires after 21d"
          },
          "proof": {
            "type": "string"
          },
          "passed": {
            "type": "boolean",
            "description": "true = you RAN this test and it passed → counts toward TEST-GREEN"
          },
          "criterion": {
            "type": "string"
          }
        }
      },
      "description": "Map ## Acceptance bullets to a test/file: [{criterion, proof, passed?, at?}]. Re-send full set (replaces). proof-only = backed (claimed); passed:true = test-green (guarantee)."
    },
    "decisions": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Decisions/divergences (prose)"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 64 lines
  • propose_flow_edge auth-required never probed

    SECONDARY (user-driven UI): propose a link between two existing screens → Inbox.

    mcp-tool

    {
  "type": "object",
  "required": [
    "from",
    "to"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "Destination screen name"
    },
    "from": {
      "type": "string",
      "description": "Source screen name"
    },
    "label": {
      "type": "string",
      "description": "Transition label (optional)"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 24 lines
  • propose_element auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "screen",
    "label"
  ],
  "properties": {
    "h": {
      "type": "number",
      "description": "Default 40"
    },
    "w": {
      "type": "number",
      "description": "Default 120"
    },
    "x": {
      "type": "number",
      "description": "Left px"
    },
    "y": {
      "type": "number",
      "description": "Top px"
    },
    "note": {
      "type": "string"
    },
    "type": {
      "type": "string",
      "description": "button/bar/panel/text (default box)"
    },
    "label": {
      "type": "string",
      "description": "Element label, e.g. 'HP bar'"
    },
    "screen": {
      "type": "string",
      "description": "Existing screen name"
    },
    "system": {
      "type": "string",
      "description": "System it serves"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 47 lines
  • propose_screen auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Screen name (Title Case, English)"
    },
    "parent": {
      "type": "string",
      "description": "Make it a POPUP over this screen"
    },
    "purpose": {
      "type": "string",
      "description": "What this screen is for"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 23 lines
  • report_screen_status auth-required never probed

    Report a SCREEN's status (todo|in-progress|implemented) → Inbox.

    mcp-tool

    {
  "type": "object",
  "required": [
    "screen",
    "status"
  ],
  "properties": {
    "screen": {
      "type": "string",
      "description": "Screen name"
    },
    "status": {
      "type": "string",
      "description": "todo | in-progress | implemented"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 20 lines
  • rename_screen auth-required never probed

    Rename a screen IN PLACE — DIRECT; links/elements follow (id-referenced).

    mcp-tool

    {
  "type": "object",
  "required": [
    "name",
    "new_name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Exact CURRENT name"
    },
    "new_name": {
      "type": "string",
      "description": "New name (must not collide)"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 20 lines
  • add_task auth-required never probed

    Add a task to a milestone — DIRECT. assignee:"me" claims on creation.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "done": {
      "type": "boolean"
    },
    "name": {
      "type": "string",
      "description": "Task name"
    },
    "human": {
      "type": "boolean",
      "description": "Human-only (GTM/validation/people work) — next_task & get_briefing skip it"
    },
    "effort": {
      "enum": [
        "S",
        "M",
        "L"
      ],
      "type": "string"
    },
    "status": {
      "enum": [
        "in-progress",
        "blocked"
      ],
      "type": "string"
    },
    "assignee": {
      "type": "string",
      "description": "\"me\" claims it"
    },
    "milestone": {
      "type": "string",
      "description": "If no id"
    },
    "project_id": {
      "type": "string"
    },
    "milestone_id": {
      "type": "string",
      "description": "Preferred"
    }
  }
}
    arguments 49 lines
  • next_task auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "dry_run": {
      "type": "boolean",
      "description": "Peek without claiming"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 12 lines
  • update_task auth-required never probed

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "task_id"
  ],
  "properties": {
    "done": {
      "type": "boolean",
      "description": "true releases the claim"
    },
    "name": {
      "type": "string"
    },
    "force": {
      "type": "boolean",
      "description": "Take over a STALE claim only"
    },
    "human": {
      "type": "boolean",
      "description": "true = human-only (next_task/get_briefing skip it); false clears"
    },
    "effort": {
      "enum": [
        "S",
        "M",
        "L",
        ""
      ],
      "type": "string",
      "description": "\"\" clears"
    },
    "status": {
      "enum": [
        "in-progress",
        "blocked",
        ""
      ],
      "type": "string",
      "description": "\"\" clears"
    },
    "task_id": {
      "type": "string",
      "description": "From get_milestone"
    },
    "assignee": {
      "type": "string",
      "description": "\"me\" claims; \"\" releases"
    },
    "project_id": {
      "type": "string"
    }
  }
}
    arguments 53 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 9b9028b094b0113a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/9b9028b094b0113a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/9b9028b094b0113a/badge.svg)](https://brick.blue/agent/9b9028b094b0113a?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on supabase.co 88 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

80 more sit on this domain. All of them.