Home / MCP registry index / io.github.Poiuyhje/eqvps

EQVPS — VPS and code sandboxes for AI agents

io.github.Poiuyhje/eqvps in the official MCP registry. Endpoint https://mcp.eqvps.com/mcp. Source: github.com/Poiuyhje/eqvps-mcp.

The registry describes it as: No-KYC VPS + per-second code sandboxes AI agents run over MCP — 75 tools, SDK, pay BTC/XMR/USDC/USDT

We read its 47 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

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

Claude Code

claude mcp add --transport http eqvps https://mcp.eqvps.com/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "eqvps": {
      "url": "https://mcp.eqvps.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"eqvps","type":"http","url":"https://mcp.eqvps.com/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. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

list_plans register_account login refresh_token set_password whoami get_balance topup_balance order_vps get_order_limits pay_invoice list_vps get_vps_status reveal_password power_vps set_hostname reset_password reinstall_vps get_vps_metrics cancel_service undo_cancel get_upgrade_options change_plan delegate_service accept_delegation list_delegations list_delegated_to_me revoke_delegation create_ticket list_tickets get_ticket reply_ticket close_ticket sandbox_pricing create_sandbox run_code exec_command get_task kill_task upload_file download_file get_download_url get_upload_url list_sandboxes get_sandbox kill_sandbox get_started

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-poiuyhje-eqvps/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-poiuyhje-eqvps)

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. What we found across the registry.

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