Home / MCP registry index / computer.cool/mcp

Cool Computers

computer.cool/mcp in the official MCP registry. Endpoint https://api.cool.computer/mcp. Source: github.com/The-Money-Company-Limited/cool-computers.

The registry describes it as: Put what you make online, get comments on it, and give it a cloud computer when it needs one.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http cool https://api.cool.computer/mcp

{
  "mcpServers": {
    "cool": {
      "url": "https://api.cool.computer/mcp"
    }
  }
}

code --add-mcp '{"name":"cool","type":"http","url":"https://api.cool.computer/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

cool_browse cool_clear_service cool_connect_integration cool_create_computer cool_delete_comment cool_delete_computer cool_delete_file cool_delete_secrets cool_disconnect_integration cool_exec cool_expose_port cool_get_computer cool_get_computer_network cool_get_default_network cool_get_domain cool_get_email_address cool_get_exposure cool_get_integration_connect cool_get_logs cool_get_secret_metadata cool_get_service cool_get_service_logs cool_get_usage cool_give_vm cool_leave_comment cool_list_computers cool_list_emails cool_list_files cool_list_integrations cool_list_network_denials cool_list_releases cool_list_secret_audit cool_list_secrets cool_list_shares cool_mkdir cool_plan_switch_workspace cool_promote_release cool_publish cool_pull_comments cool_query_database cool_read_email cool_read_file cool_remove_domain cool_reopen_comment cool_reply_comment cool_reply_email cool_resolve_comment cool_restart_service cool_run_service cool_send_email cool_set_computer_network cool_set_computer_visibility cool_set_default_network cool_set_domain cool_set_secrets cool_share cool_stat_file cool_stop_service cool_switch_workspace cool_unexpose_port and 3 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-04): 31a09beb2917ecfa. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/computer-cool-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/computer-cool-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. How tool poisoning works. What we found across the registry. Check another server.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.