Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

forge-delegate

NPM · FORGE-DELEGATE

Delegate coding tasks from Claude Code, Codex or opencode to any model opencode can run.

Available components

+4 this week 67 Trust /100

Last scanned (21 hours ago)

Scores higher than 34% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability64
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1638 tokens (~273/item across 6 items; 6 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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.

  • 4 Nov 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.

  • 2 Nov 26 +3
    • Stability: unverified → 0.20 ▲ functional
  • 28 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 27 Oct 26 48

    First indexed and scored.

Diagnostics

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 4 Nov 2026 · Analysed npm/forge-delegate@1.2.4

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~1,259 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
ask_model ~201

Get a second opinion from a different model — on a design, an approach, or a tricky snippet — or ask one when the user requests it. Sends a one-shot prompt over a direct API call and returns the raw response. The model has no file access and cannot take actions; for anything touching files use delegate. Don't use it for syntax or API details you already know: a cheap model is usually less reliable than you on those. Omit model to use the configured default.

NameTypeReqDescription
modelstring–provider/model or ollama:<name>, e.g. deepseek/deepseek-v4-flash, ollama:llama3. Omit to use the configured default; don't pick a premium tier
promptstringyesThe full question. The model has seen none of this conversation, so include the code and context it needs
systemstring–Optional system prompt, e.g. a role or an answer format

No output schema declared.

No examples provided.

check_delegation ~98

Check a delegation started with background:true. Returns RUNNING, DONE or TIMED OUT, the elapsed time, the session id, and the last 8,000 characters of the agent's output. Each poll costs context, so wait between polls instead of checking in a tight loop. Call with no id to list all jobs.

NameTypeReqDescription
idstring–Job id returned by delegate with background:true. Omit to list all jobs

No output schema declared.

No examples provided.

delegate ~541

Hand a coding task to another AI model running as a full agent via local opencode: it reads the project, explores, and writes the code in its own tool loop, none of which enters your context. Use it instead of writing the code yourself for: tests for code that already exists; a mechanical refactor (rename, signature change, import rewrite, API migration); lint/type/build errors (paste the error output); boilerplate or scaffolding (CRUD endpoints, config, schemas, adapters, fixtures); a port between languages or frameworks; the same edit repeated across 3 or more files; reading a large file or directory to answer one narrow question; the survey half of an audit. Runs inline by default and returns when done; Claude Code backgrounds calls past 2 minutes, other hosts wait. Pass background:true to get a job id at once, then poll check_delegation. Pass continue_session (returned by a previous delegation) to keep the same agent session instead of re-exploring. Name file paths in task; never paste their contents. model/directory/agent/autoApprove default from config — omit them. Review what comes back before reporting it done.

NameTypeReqDescription
agentstring–opencode agent to use (defaults to config defaultAgent)
autoApproveboolean–Let the agent edit files and run commands without asking (defaults to config autoApprove, true). When false nobody is there to approve, so actions that need approval can stall or be refused
backgroundboolean–Run detached and return a job id immediately; poll check_delegation (default false)
continue_sessionstring–Session id from a previous delegation's result, to continue in that agent session
directorystring–Absolute path of the project to work in (defaults to config defaultDirectory, else the server's working directory)
filesarray–Paths to attach to the agent's prompt (inline only; ignored with background:true). Rarely needed: the agent reads paths named in task itself
modelstring–provider/model, e.g. opencode/deepseek-v4.1-flash-free. Omit to use the configured default; don't raise it to a premium tier — split the task instead
profilestring–Named preset from config profiles (see get_delegate_config) that sets model, agent, variant, directory and autoApprove together
taskstringyesSelf-contained instructions: the goal, the file paths to read or change, constraints, and how to check the result (e.g. which tests to run). The agent has not seen this conversation

No output schema declared.

No examples provided.

get_delegate_config ~75

Read the current forge-delegate configuration: defaultModel, defaultAgent, defaultVariant, autoApprove, timeoutMs, defaultDirectory, and named profiles — plus the installed version and whether it updates automatically. Call this to see what will be used when a model/directory is omitted, or when the user asks which version is running.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_models ~69

List the models available for delegation: local/keyless ones, direct-API models from opencode logins, and agentic models from the local opencode installation. Call it when the user asks what's available or wants to change the default model, not before an ordinary delegation — those use the configured default.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_delegate_config ~275

Change forge-delegate configuration at runtime — no reinstall. Only change settings when the user asks; never raise defaultModel to a premium tier on your own. Pass any subset of {defaultModel, defaultAgent, defaultVariant, autoApprove, timeoutMs, defaultDirectory, profiles}. Set a field to null to clear it. To edit a profile, pass the whole profiles object (e.g. profiles: {tests: {model: "..."}}); set a profile to null to delete it. Only provided keys change; others are preserved.

NameTypeReqDescription
autoApproveboolean–Let delegated agents edit files and run commands without asking
defaultAgentstring|null–opencode agent used when a call omits agent
defaultDirectorystring|null–Absolute project path used when a call omits directory
defaultModelstring|null–provider/model used when a call omits model
defaultVariantstring|null–Reasoning-effort variant, sent to opencode as provider/model#variant
profilesobject–The whole profiles object: { name: { model, agent, variant, autoApprove, directory } }. A profile set to null is deleted
timeoutMsnumber–Per-delegation timeout in milliseconds (default 900000, 15 minutes)

No output schema declared.

No examples provided.

Install

How do I install the forge-delegate MCP server?

forge-delegate runs locally as an npm package, launched with npx -y forge-delegate. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · forge-delegate

# add to Claude Code
claude mcp add muhamadbarzani-forge-delegate -- npx -y forge-delegate
Common questions

What is the forge-delegate MCP server?

forge-delegate is an MCP server listed in the public MCP registry as io.github.MuhamadBarzani/forge-delegate. Delegate coding tasks from Claude Code, Codex or opencode to any model opencode can run. This page covers its npm package (forge-delegate).

Is the forge-delegate MCP server safe to use?

forge-delegate scores 67 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the forge-delegate MCP server expose?

forge-delegate exposes 6 tools: list_models, ask_model, delegate, check_delegation, get_delegate_config, set_delegate_config. Their descriptions and schemas cost roughly 1,259 tokens of context every time the server is loaded.

Is the forge-delegate MCP server still maintained?

forge-delegate is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the forge-delegate MCP server under?

forge-delegate declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.