Open Computer Use
Capped at 70: core tools not tested: blocked in sandbox; the tests add up to 95. Why scores are capped
Test points add up to 95; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology
Test points before the cap (95/100)
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs10/15
- License10/10
Tested npm open-computer-use 1.1.4 (MIT; repo iFurySt/open-computer-use). Installed pinned with scripts off (npm --ignore-scripts) and launched with `mcp`: initialize and tools/list over stdio succeeded with no credentials and listed 9 tools (9 annotated by the server: 2 read-only, 0 destructive). Real calls: 0 of 1 real function calls passed. No passing real call: the Linux runtime needs the AT-SPI accessibility stack and a desktop session. Core tools not tested: 70 cap.
Tool-call test (2026-11-13 UTC, direct MCP stdio client, no LLM): fail. 0 of 1 real function calls passed. No passing real call: the Linux runtime needs the AT-SPI accessibility stack and a desktop session. Evidence: local test run, Nov 13, 2026 UTC.
Transport (tested 2026-11-13 UTC): stdio
Token cost (estimate): approx. 1309 tokens, cl100k estimate (9 tools, measured 2026-11-13 UTC, version 1.1.4). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 3 read, 1 write (state-changing), 5 unclassified · Auth: local · Rate limit: unknown · Pricing unit: unknown
Auth: local. Rate limit: unknown. Pricing unit: unknown.
click— unclassifieddrag— unclassifiedget_app_state— readlist_apps— readperform_secondary_action— unclassifiedpress_key— unclassifiedscroll— unclassifiedset_value— write (state-changing)type_text— read
local stdio server with no recorded cloud credential
Score 70/100 · Tools 9 · Token cost approx. 1,309 tokens · Compare · Last tested 2026-11-13 UTC · Version tested 1.1.4 · Package open-computer-use · Repo iFurySt/open-computer-use
Summary: Open Computer Use completed an MCP handshake without credentials and exposed 9 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 9
- Context cost
- approx. 1309 tokens, cl100k estimate (9 tools, measured 2026-11-13 UTC, version 1.1.4; an estimate) ranking · add up your servers' context cost
- API key
- No key to connect (handshake passed)
- Tested
- 2026-11-13 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install open-computer-use (Node 20, Linux) succeeded in 1s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 9 tools listed in 6.8s. |
| maintenance | pass | 25 | Repo pushed 0 days before test; 2,948 GitHub stars. |
| docs | partial | 10 | install instructions present; mcpServers config example present. Check of the package's own README (README shipped in npm package). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 1309 tokens, cl100k estimate for 9 tools · about 16% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-13 UTC
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 9 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-13 UTC test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
429dc007a6e7: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "open-computer-use",
"version": "1.1.4",
"registry": "npm",
"status": "working",
"tested": "2026-11-13",
"tools_count": 9,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install open-computer-use` (Node 20, Linux) succeeded in 1s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 9 tools listed in 6.8s."
],
"maintenance": [
"pass",
25,
"Repo pushed 0 days before test; 2,948 GitHub stars."
],
"docs": [
"partial",
10,
"install instructions present; `mcpServers` config example present. Check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
}
}Install
npx -y open-computer-use mcp
Pin the version we tested
npx -y open-computer-use@1.1.4 mcp
tested 2026-11-13 UTC. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"open-computer-use": {
"command": "npx",
"args": [
"-y",
"open-computer-use@1.1.4",
"mcp"
]
}
}
}Tools listed
click, drag, get_app_state, list_apps, perform_secondary_action, press_key, scroll, set_value, type_text
Quick config
{
"mcpServers": {
"open-computer-use": {
"command": "npx",
"args": [
"-y",
"open-computer-use",
"mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install open-computer-use(Node 20). This is the exact command we ran on 2026-11-13 UTC. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (9 in our test).
{
"mcpServers": {
"open-computer-use": {
"command": "npx",
"args": [
"-y",
"open-computer-use",
"mcp"
]
}
}
}Test history
- 2026-11-13 UTC: New
Related: Best workflow and automation MCP servers · Troubleshooting: Protocol version mismatch (HTTP 400)
FAQ
Is Open Computer Use deprecated?
No. open-computer-use was not deprecated or archived when we last tested it on 2026-11-13 UTC.
What replaces Open Computer Use?
Nothing; Open Computer Use is not deprecated as of 2026-11-13 UTC.
Does Open Computer Use need an API key?
No. It completed an MCP handshake with no credentials and listed 9 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.