octomux (ShreyPaharia/octomux) is an MCP server listed on the M8ven Trust Index. It scores 52 out of 100, grade D. It declares 11 tools. No publisher has claimed this listing.

Caution

52/100

octomux

Item: octomux
Rating: 52
Author: M8ven

Local dashboard to run parallel Claude Code & Cursor agents — kanban fleet view, one permission inbox, in-app diff review. macOS, MIT.

→ ShreyPaharia/octomux · listed on github_code

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every push why connect →

Who stands behind it

ShreyPaharia

Source: github_code

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings

🚨

Secret credentials may flow to a network call

1 flow detected: OCTOMUX_ACTION_TOKEN. We can’t prove the destination matches the brand the credential belongs to.

⚠️

Known vulnerabilities in dependencies: 13 high

Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.

🔐

You'll be asked for 4 credentials: ANTHROPIC_API_KEY, OCTOMUX_ACTION_TOKEN, OCTOMUX_REMOTE_TOKEN, OCTOMUX_SECRET_KEY

These are read from process.env at runtime. Make sure you trust where they’ll be sent.

// tools this server exposes11 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

monitor_status

get_task_output

get_agent_output

pull_linear_issue

recent_repos

default_branch

search_learnings

list_schedules

list_schedule_kinds

get_settings

report_complete

// known CVEs in dependencies13 high24 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

highjs-yaml@4.2.0GHSA-52cp-r559-cp3m

js-yaml: YAML merge-key chains can force quadratic CPU consumption

highjs-yaml@4.2.0GHSA-5p4m-2wfm-xmqj

JS-YAML: Quadratic CPU consumption in !!omap resolution (3.x and 4.x) — CVE-2026-59870 fix not backported

highnanoid@5.0.9GHSA-28wg-ghj8-5hjv

nanoid: non-secure generators can loop indefinitely with negative size

highnanoid@5.0.9GHSA-2v37-7h3g-55p8

nanoid: custom generators can loop indefinitely when size is zero

highnanoid@5.0.9GHSA-xwg4-73v4-xw9w

nanoid: Integer Overflow or Wraparound

Depend on this server? Get alerted when its CVEs change.Watch this server free →

// environment variables

To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.

🔐 secretANTHROPIC_API_KEY

configJIRA_EMAIL_TEST

configOCTOMUX_ACTION_BASE_URL

🔐 secretOCTOMUX_ACTION_TOKEN

configOCTOMUX_ALLOWED_HOSTS

configOCTOMUX_APPROVAL_TIMEOUT_MS

configOCTOMUX_BIND

configOCTOMUX_CAPABILITY_GATE_ENABLED

configOCTOMUX_CLAUDE_FLAGS

configOCTOMUX_CONVERSATION_ID

configOCTOMUX_DATA_DIR

configOCTOMUX_DB_PATH

configOCTOMUX_GH_STUB_RESPONSE

configOCTOMUX_GITHUB_LOGIN

configOCTOMUX_HOOK_LOG_RETAIN

configOCTOMUX_HOOK_TIMEOUT_MS

configOCTOMUX_PORT

🔐 secretOCTOMUX_REMOTE_TOKEN~/.octomux/data/remote-token; override with ). Open

configOCTOMUX_SAFE_MODE

🔐 secretOCTOMUX_SECRET_KEY

configOCTOMUX_SUBMIT_RESULT_PATH

configOCTOMUX_SUBMIT_RESULT_SCHEMA

configOCTOMUX_SUBMIT_RESULT_SCHEMA_PATH

configOCTOMUX_TASK_ID

configOCTOMUX_TMUX_BIN

Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.

deployPORT

// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

11/11 tools missing one or more hints — monitor_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_task_output (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_agent_output (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +8 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

No arbitrary install scripts

Has postinstall/preinstall script — runs arbitrary code on npm install

Remove postinstall/preinstall hooks unless they’re essential.

Production dependencies are patched

0 critical, 6 high severity in production deps — js-yaml@4.2.0 (high), js-yaml@4.2.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

7 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Dependency freshness

2/42 production deps stale: @dnd-kit/utilities@2023-11-06 (2.8y), rehype-sanitize@2023-11-20 (2.8y)

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail

The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.

// improvement guidance — verified publishers only

We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.

// embed badge in your README

[![M8ven Verified](https://m8ven.ai/badge/mcp/shreypaharia/octomux?variant=verified)](https://m8ven.ai/mcp/shreypaharia/octomux)

Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.

commit: b7cfad9356f5031323d6476ccf313bc7994cb123

code hash: b3e0270851a471dc8f1672b66970a0714a404b0fde29c855da954376fda26c42

view raw JSON →

Check MCPs from inside your assistant

Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check

check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern

How to add it →Free · no account needed · works in any MCP client