orca (alex2481kobe/orca) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 1 tool. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100

orca

A local harness for the coding agents you already run: let Claude Code or Codex spawn and depend on subagents over MCP, with governed lanes, git-worktree isolation, an audit gate, and a private phone dashboard over Tailscale.

→ alex2481kobe/orca· listed on github_repo_search

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

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

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

alex2481kobe

Source: github_repo_search

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
4 flows detected: ORCA_API_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 3 credentials: ORCA_API_TOKEN, ORCA_REFRESH_TOKEN, ORCA_TOOL_LEASE_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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.
configCLAUDE_CONFIG_DIR
configCODEX_HOME
configORCA_AGENT_TOOLS_BASE_URL
configORCA_ALLOWED_HOSTS
🔐 secretORCA_API_TOKENNo means every process on this machine is Orca admin, and role
configORCA_AUTO_AUDIT
configORCA_AUTO_COMPLETE_MS
configORCA_AUTO_RECLAIM_WORKTREE
configORCA_BROWSER_SESSION_TTL_MS
configORCA_CLI_BINARY
configORCA_CLI_HEARTBEAT_TIMEOUT_MS
configORCA_ENABLE_CUSTOM_CLI
configORCA_HEARTBEAT_MS
configORCA_HOST
configORCA_LANE_CONCURRENCY
configORCA_LANE_ID
configORCA_LANE_IDLE_TIMEOUT_MS
configORCA_LANE_JOURNAL_HOT_SEGMENTS
configORCA_LANE_JOURNAL_SEGMENT_BYTES
configORCA_MAX_JSON_BYTES
configORCA_MAX_TERMINAL_LANES_PER_SESSION
configORCA_ORCHESTRATOR_ID
configORCA_PAIRING_CODE_TTL_MS
configORCA_PROJECT_ID
configORCA_RATE_LIMIT_DISABLED
🔐 secretORCA_REFRESH_TOKEN
configORCA_ROLE
configORCA_SEED
configORCA_SESSION_ID
configORCA_STOP_ESCALATE_MS
configORCA_STREAM_HEARTBEAT_MS
🔐 secretORCA_TOOL_LEASE_TOKEN
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

1/1 tools missing one or more hints — permission_prompt (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). 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.

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 2 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 Score](https://m8ven.ai/badge/mcp/alex2481kobe/orca)](https://m8ven.ai/mcp/alex2481kobe/orca)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: bb416e61447ee235f4a9cf84904f0b773a4404d8
code hash: 7162a18a5c46e658655e25e82046f2c18df16aa9d8e00ccdfdf4fb8be0833626
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