Orgo Ai MCP Server

@orgo-ai/mcp npm v3.0.0

Published by @orgo-ai — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Orgo virtual computer control — works with Claude Code, Claude Desktop, and any MCP client

Trust grade
B
89/100
Last scanned get badge →
Trust
B · 89/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Critical
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
B Why this grade threat 100 − adoption risk = 89/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 11 = 89. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−10 capability blast radius (critical) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 6

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: orgo_download_file → orgo_list_files → orgo_bash. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow orgo_download_file → orgo_list_files → orgo_bash

high Tool "orgo_bash" exposes command/code executionMTC-CAP-001

Tool "orgo_bash" appears to run shell commands or evaluate code (keyword "bash" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool orgo_bash

high Tool "orgo_exec" exposes command/code executionMTC-CAP-001

Tool "orgo_exec" appears to run shell commands or evaluate code (keyword "exec" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool orgo_exec

high Shell/command execution in server code (dist/server.js)MTC-SRC-002

In the server's implementation (`dist/server.js:43`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: et terminal preferred), exec (Python) - **Files**: list, upload, export, download - **AI Agent**: completions (autonomou

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/server.js

low Mutating tool "orgo_bash" declares no destructiveHintMTC-CAP-005

Tool "orgo_bash" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool orgo_bash

low Mutating tool "orgo_exec" declares no destructiveHintMTC-CAP-005

Tool "orgo_exec" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool orgo_exec

Tools 40

Each tool and what it can reach — statically extracted from the published source.

  • orgo_bashruns code / shell
  • orgo_download_fileingests untrusted input
  • orgo_execruns code / shell
  • orgo_list_filesreads sensitive data
  • orgo_upload_filenetwork egress
  • orgo_clickno sensitive capability
  • orgo_clone_computerno sensitive capability
  • orgo_completionsno sensitive capability
  • orgo_create_computerno sensitive capability
  • orgo_create_workspaceno sensitive capability
Show 30 more tools ↓
  • orgo_delete_computerno sensitive capability
  • orgo_delete_threadno sensitive capability
  • orgo_dragno sensitive capability
  • orgo_ensure_runningno sensitive capability
  • orgo_export_fileno sensitive capability
  • orgo_get_computerno sensitive capability
  • orgo_get_creditsno sensitive capability
  • orgo_get_profileno sensitive capability
  • orgo_get_threadno sensitive capability
  • orgo_get_transactionsno sensitive capability
  • orgo_get_workspaceno sensitive capability
  • orgo_keyno sensitive capability
  • orgo_list_computersno sensitive capability
  • orgo_list_templatesno sensitive capability
  • orgo_list_threadsno sensitive capability
  • orgo_list_workspacesno sensitive capability
  • orgo_resize_computerno sensitive capability
  • orgo_restart_computerno sensitive capability
  • orgo_screenshotno sensitive capability
  • orgo_scrollno sensitive capability
  • orgo_star_templateno sensitive capability
  • orgo_starred_templatesno sensitive capability
  • orgo_start_computerno sensitive capability
  • orgo_start_streamno sensitive capability
  • orgo_stop_computerno sensitive capability
  • orgo_stop_streamno sensitive capability
  • orgo_stream_statusno sensitive capability
  • orgo_typeno sensitive capability
  • orgo_vnc_passwordno sensitive capability
  • orgo_workspace_by_nameno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v3.0.0 latest B 89/100 6 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: B · 89/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/orgo-ai-mcp/badge.svg)](https://mcptrustchecker.com/registry/orgo-ai-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/orgo-ai-mcp"><img src="https://mcptrustchecker.com/registry/orgo-ai-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/orgo-ai-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @orgo-ai/mcp --online

Use the free API → How scoring works

More in Developer Tools