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.

omp-worker-mcp

NPM · OMP-WORKER-MCP · SCANNED SEP 24

Delegate complete coding tasks to the local OMP default model and inspect the result.

Available components

+4 this week 82 Trust /100
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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1241 tokens (~137/item across 9 items; 9 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 Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 61% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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
Install

How do I install the omp-worker-mcp server?

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

npm · omp-worker-mcp

# add to Claude Code
claude mcp add divenire990-omp-worker-mcp -- npx -y omp-worker-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "divenire990-omp-worker-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "omp-worker-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "divenire990-omp-worker-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "omp-worker-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add divenire990-omp-worker-mcp -- npx -y omp-worker-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "divenire990-omp-worker-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "omp-worker-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add divenire990-omp-worker-mcp --command npx --arg -y --arg omp-worker-mcp
# ~/.hermes/config.yaml
mcp_servers:
  divenire990-omp-worker-mcp:
    command: "npx"
    args: ["-y", "omp-worker-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "divenire990-omp-worker-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "omp-worker-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add divenire990-omp-worker-mcp -t stdio -c npx -a -y omp-worker-mcp
// mcp.json
{
  "mcpServers": {
    "divenire990-omp-worker-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "omp-worker-mcp"
      ]
    }
  }
}
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.

  • 24 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

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 24 Sept 2026 · Analysed npm/omp-worker-mcp@0.1.1

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 →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~1,084 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
omp_cancel ~72

Request immediate cancellation of one exact delegated OMP job. The detached runner owns the OMP child PID and terminates that process tree safely. Call this immediately when the user asks to stop; do not inspect PIDs or manually kill processes first.

NameTypeReqDescription
job_idstringyes
reasonstring
NameTypeReqDescription
artifactsarrayyes
attemptintegeryes
details_pathstring
errorstring
job_idstringyes
max_attemptsintegeryes
remainingarrayyes
session_idstring
statusstringyes
summarystring
verificationarrayyes

No examples provided.

omp_cancel_group ~75

Request immediate cancellation of a running batch task group and its child tasks. Writes a cancellation request that the detached group coordinator handles safely. Call this immediately when the user asks to stop a batch.

NameTypeReqDescription
group_idstringyesThe group_id of the batch task group to cancel
reasonstringReason for cancellation
NameTypeReqDescription
blocked_tasksintegeryes
cancelled_tasksintegeryes
completed_tasksintegeryes
failed_tasksintegeryes
group_idstringyes
max_parallelintegeryes
statusstringyes
summarystringyes
tasksarray
total_tasksintegeryes

No examples provided.

omp_continue ~75

Resume the same OMP session with targeted supervisory feedback to correct specific acceptance defects without starting a fresh task from scratch. Bounded to remaining attempts within max_attempts.

NameTypeReqDescription
feedbackstringyesSpecific defect, evidence, intended correction, and success check
job_idstringyes
timeout_minutesinteger
NameTypeReqDescription
artifactsarrayyes
attemptintegeryes
details_pathstring
errorstring
job_idstringyes
max_attemptsintegeryes
remainingarrayyes
session_idstring
statusstringyes
summarystring
verificationarrayyes

No examples provided.

omp_delegate ~125

Low-level background delegation entrypoint. Transfers ownership of an execution task to OMP and returns immediately with job_id. Prefer omp_run_compact for standard workflows to avoid separate delegate/wait round trips.

NameTypeReqDescription
acceptancearray
cwdstringyesAbsolute working directory OMP may inspect and modify
goalstringyesComplete natural-language outcome OMP must deliver
max_attemptsinteger
supervisor_briefstringDecision-ready read-only findings, hypotheses, constraints, and recommended direction
timeout_minutesinteger
NameTypeReqDescription
artifactsarrayyes
attemptintegeryes
details_pathstring
errorstring
job_idstringyes
max_attemptsintegeryes
remainingarrayyes
session_idstring
statusstringyes
summarystring
verificationarrayyes

No examples provided.

omp_result ~66

Retrieve full details of a terminal OMP job, including finalResponse and attempt logs. Call this only when minimal acceptance check fails, high-risk operations occurred, or the user explicitly asks for full inspection; do not call this after every successful compact run.

NameTypeReqDescription
job_idstringyes
NameTypeReqDescription
artifactsarrayyes
attemptintegeryes
attemptsarrayyes
cwdstringyes
details_pathstringyes
errorstring
final_responsestring
goalstringyes
job_idstringyes
max_attemptsintegeryes
remainingarrayyes
session_idstring
statusstringyes
summarystring
verificationarrayyes

No examples provided.

omp_run_batch_compact ~291

Submits a decomposed group of OMP tasks to execute concurrently in the server-side bounded rolling pool (max_parallel 1-10) using a detached group runner. Enforces dependency DAG and write-ownership safety, waits up to wait_seconds (0-240, default 60s) for batch completion, and returns stable compact aggregated results. If still running when deadline elapses, returns group_id and minimal progress counts for subsequent omp_wait_group.

NameTypeReqDescription
cwdstringyesAbsolute working directory OMP may inspect and modify
default_max_attemptsintegerDefault per-task attempt limit if not specified in task (1-5, default 3)
default_timeout_minutesintegerDefault per-task timeout in minutes if not specified in task (1-120, default 30)
group_timeout_minutesintegerHard overall group deadline in minutes (1-120, default 60)
max_parallelintegerMaximum concurrent active OMP runners (1-10, default 4)
supervisor_briefstringShared decision-ready read-only findings, hypotheses, and constraints for the task group
tasksarrayyesArray of decomposed tasks to execute concurrently according to dependency DAG and ownership safety
wait_secondsintegerMaximum seconds to wait for batch completion inside this call (0-240, default 60)
NameTypeReqDescription
blocked_tasksintegeryes
cancelled_tasksintegeryes
completed_tasksintegeryes
failed_tasksintegeryes
group_idstringyes
max_parallelintegeryes
statusstringyes
summarystringyes
tasksarray
total_tasksintegeryes

No examples provided.

omp_run_compact ~194

Preferred entrypoint for single substantive execution tasks. Creates a delegated OMP task, launches the detached runner, and waits up to wait_seconds (default 60s) for completion in a single MCP call. If finished, returns a compact summary, artifacts, verification, and details_path without dumping the full final response. If still running at the deadline, returns job_id and status running for subsequent omp_wait.

NameTypeReqDescription
acceptancearray
cwdstringyesAbsolute working directory OMP may inspect and modify
goalstringyesComplete natural-language outcome OMP must deliver
max_attemptsinteger
supervisor_briefstringDecision-ready read-only findings, hypotheses, constraints, and recommended direction
timeout_minutesinteger
wait_secondsintegerMaximum seconds to wait for terminal status inside this call (0-60, default 60)
NameTypeReqDescription
artifactsarrayyes
attemptintegeryes
details_pathstring
errorstring
job_idstringyes
max_attemptsintegeryes
remainingarrayyes
session_idstring
statusstringyes
summarystring
verificationarrayyes

No examples provided.

omp_wait ~76

Wait for an existing OMP job to reach a terminal status, polling up to wait_seconds (default 30s, max 60s). Returns the current status and summary once terminal or when the wait deadline elapses. Avoid polling in a tight loop.

NameTypeReqDescription
job_idstringyes
wait_secondsinteger
NameTypeReqDescription
artifactsarrayyes
attemptintegeryes
details_pathstring
errorstring
job_idstringyes
max_attemptsintegeryes
remainingarrayyes
session_idstring
statusstringyes
summarystring
verificationarrayyes

No examples provided.

omp_wait_group ~110

Wait for an existing OMP task group to reach a terminal status, polling up to wait_seconds (0-240, default 60s). If completed, returns full aggregated compact results in original input order. If still running when deadline elapses, returns minimal progress counts without leaking task summaries.

NameTypeReqDescription
group_idstringyesThe unique group_id returned by omp_run_batch_compact
wait_secondsintegerMaximum seconds to wait inside this call (0-240, default 60)
NameTypeReqDescription
blocked_tasksintegeryes
cancelled_tasksintegeryes
completed_tasksintegeryes
failed_tasksintegeryes
group_idstringyes
max_parallelintegeryes
statusstringyes
summarystringyes
tasksarray
total_tasksintegeryes

No examples provided.

Common questions

What is the omp-worker-mcp server?

omp-worker-mcp is listed in the public MCP registry as io.github.divenire990/omp-worker-mcp. Delegate complete coding tasks to the local OMP default model and inspect the result. This page covers its npm package (omp-worker-mcp).

Is the omp-worker-mcp server safe to use?

omp-worker-mcp scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 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 omp-worker-mcp server expose?

omp-worker-mcp exposes 9 tools: omp_run_batch_compact, omp_wait_group, omp_cancel_group, omp_run_compact, omp_delegate, and 4 more. Their descriptions and schemas cost roughly 1,084 tokens of context every time the server is loaded.

Is the omp-worker-mcp server still maintained?

omp-worker-mcp is still listed as active in the MCP registry. We last reached this channel on 24 September 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 omp-worker-mcp server under?

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