orca-mcp (BuildContext/orca-mcp) 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.

C
Emerging
74/100
12 days ago

orca-mcp

External MCP server for controlling Orca worktrees, agent sessions, and multi-agent orchestration from any MCP client via stdio or Streamable HTTP.

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

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 pushwhy connect →

Who stands behind it

BuildContext

Source: Glama

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 →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: ORCA_BRIDGE_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.
configHINDSIGHT_URLno Not used on the stdio path today (HTTP proxy only)
configORCA_BRIDGE_AUDIT_DIRAppend-only audit log (redacted NDJSON under or ~/.orca-bridge) records tool calls for forensics — it is not an access-control layer.
configORCA_BRIDGE_DEBUGno 0 mutes access log (stderr in stdio mode)
configORCA_BRIDGE_DEFAULT_AGENTno Default agent (default omp)
configORCA_BRIDGE_DEFAULT_REPOno Default --repo for dispatch
configORCA_BRIDGE_FROMORCA_BRIDGE_SENDER_TERMINAL / no Pin orchestration sender handle
configORCA_BRIDGE_INJECT_RECOVERY
configORCA_BRIDGE_INJECT_SETTLE_MS
configORCA_BRIDGE_PUBLIC_ORIGINe =https://your-host.example.ts.net \
configORCA_BRIDGE_REDIRECT_ALLOWexport ="https://your-client.example/,https://hyperagent.com/"
configORCA_BRIDGE_SENDER_SHAREDno 1 = single-tenant sender pin
configORCA_BRIDGE_SENDER_TERMINAL/ ORCA_BRIDGE_FROM no Pin orchestration sender handle
configORCA_BRIDGE_SENDER_TITLEno Title for auto-created coordinator tabs
🔐 secretORCA_BRIDGE_TOKEN"": "<openssl rand -hex 32>",
configORCA_CLI_COMMAND"": "orca"
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 — orca (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.

Tests exist

No test files found

Add tests that exercise each declared tool.

Shell command execution

1 child_process/subprocess call in production code — runs shell commands (server.mjs:421)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

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 4 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/buildcontext-orca-mcp-17b75d)](https://m8ven.ai/mcp/buildcontext-orca-mcp-17b75d)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 5243aea96b1aef49c93563bc811facd5de39f9ba
code hash: f9a6691b5158c6176e366f25dc0b18f21762d037ee367de119316daecadfa95b
verified: 8/11/2026, 7:31:02 AM
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