Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.Agent360dk/computer-mcp

NPM · @AGENT360/COMPUTER-MCP

macOS computer use with the guardrails on: passwords blacked out, writes need consent, all logged.

+5 this week 80 Trust /100

Last scanned (19 hours ago)

Scores higher than 65% of npm servers

Category Browser Automation

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security92
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 27 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 545 tokens (~45/item across 12 items; 12 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 45% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1
    • Security disclosure: unverified → pass ▲ functional
  • 11 Oct 26 +2
    • Security disclosure: pass → unverified ▼ functional
  • 4 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 16 Oct 2026 · Analysed npm/@agent360/computer-mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
postinstall unreviewed node bin/postinstall.js || true

Background: Why install scripts are a supply-chain risk →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~545 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
computer_activate ~27

Bring an application to the front by bundle ID or name.

NameTypeReqDescription
appstringyes–

No output schema declared.

No examples provided.

computer_apps ~25

List running applications with their bundle IDs. Use the bundle ID to target other tools.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

computer_audit ~37

Show what this server has done: the last N entries of the append-only audit log.

NameTypeReqDescription
limitnumber–Default 40.

No output schema declared.

No examples provided.

computer_click ~58

Click at screen coordinates. Get coordinates from computer_inspect frames, not from guessing.

NameTypeReqDescription
buttonstring––
countnumber–2 for double-click.
xnumberyes–
ynumberyes–

No output schema declared.

No examples provided.

computer_inspect ~70

Read the accessibility tree: roles, titles, values and frames. Prefer this over guessing pixel coordinates from a screenshot. Values of secure fields are never returned.

NameTypeReqDescription
appstring––
depthnumber–Default 12.
limitnumber–Max nodes, default 400.

No output schema declared.

No examples provided.

computer_key ~37

Press a key combination, e.g. "cmd+s", "escape", "cmd+shift+4".

NameTypeReqDescription
combostringyes–

No output schema declared.

No examples provided.

computer_move ~34

Move the mouse pointer without clicking (to trigger hover states).

NameTypeReqDescription
xnumberyes–
ynumberyes–

No output schema declared.

No examples provided.

computer_permissions ~28

Check which macOS permissions are granted (Accessibility, Screen Recording). Call this first if anything fails.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

computer_screenshot ~105

Screenshot the screen or one app. Password fields and password-manager windows are blacked out BEFORE the image is written, so they never reach the model. Set redact=false only if you know the screen holds no secrets.

NameTypeReqDescription
appstring–Bundle ID or app name. Omit for the whole screen.
maxWidthnumber–Scale down to this width in pixels. Default 1400.
redactboolean–Default true. Blacks out secure fields.

No output schema declared.

No examples provided.

computer_scroll ~33

Scroll by pixel deltas at the current pointer position.

NameTypeReqDescription
dxnumber––
dynumber––

No output schema declared.

No examples provided.

computer_type ~59

Type text into the focused field as Unicode, so it works on any keyboard layout. The text is never written to the audit log in clear text.

NameTypeReqDescription
cpsnumber–Characters per second, default 240.
textstringyes–

No output schema declared.

No examples provided.

computer_windows ~32

List open windows with titles and screen frames.

NameTypeReqDescription
appstring–Limit to one bundle ID or app name.

No output schema declared.

No examples provided.

Install

How do I install the io.github.Agent360dk/computer-mcp server?

io.github.Agent360dk/computer-mcp runs locally as an npm package, launched with npx -y @agent360/computer-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @agent360/computer-mcp

# add to Claude Code
claude mcp add agent360dk-computer-mcp -- npx -y @agent360/computer-mcp
Common questions

What is the io.github.Agent360dk/computer-mcp server?

io.github.Agent360dk/computer-mcp is listed in the public MCP registry as io.github.Agent360dk/computer-mcp. macOS computer use with the guardrails on: passwords blacked out, writes need consent, all logged. This page covers its npm package (@agent360/computer-mcp).

Is the io.github.Agent360dk/computer-mcp server safe to use?

io.github.Agent360dk/computer-mcp scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.Agent360dk/computer-mcp server expose?

io.github.Agent360dk/computer-mcp exposes 12 tools: computer_permissions, computer_apps, computer_windows, computer_screenshot, computer_inspect, and 7 more. Their descriptions and schemas cost roughly 545 tokens of context every time the server is loaded.

Is the io.github.Agent360dk/computer-mcp server still maintained?

io.github.Agent360dk/computer-mcp is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.Agent360dk/computer-mcp server under?

io.github.Agent360dk/computer-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.