EQVPS — MCP Server

API-native, pay-per-use, no-KYC VPS hosting that AI agents can rent and run by themselves. EQVPS exposes a Model Context Protocol server so an autonomous agent can discover plans, create an account, pay with crypto, order a VPS, and fully operate it — no human in the loop, agents provision programmatically.

• 🌐 Website: https://eqvps.com

• 📚 Docs (REST + MCP): https://eqvps.com/docs

• 🔌 MCP endpoint: https://mcp.eqvps.com/mcp (transport: streamable-http)

• 💸 Payment: crypto only — USDC and USDT on Base and Ethereum, via a self-hosted non-custodial gateway (PayRam). No KYC.

• 📝 Blog (guides): https://eqvps.com/blog

This is a hosted, commercial remote MCP server. Most tools require a Bearer token tied to a customer account with a prepaid crypto balance. Provisioning a VPS spends prepaid balance funded with topup_balance. Catalog tools (list_plans) are public.

What this server does

An AI agent can complete the entire VPS lifecycle on its own — no dashboard, no card, no identity check:

1. Discover — list_plans (public) returns plans, specs, prices, OS images.

2. Sign up — register_account gives the agent a Bearer token instantly (no email, no OTP, no human step).

3. Fund — topup_balance returns a crypto checkout URL; pay in USDC/USDT to load a prepaid balance.

4. Provision — order_vps creates a VPS from the balance; get_vps_status returns live state and SSH access.

5. Operate — power, hostname, root-password reset, reinstall, metrics, cancel — all over MCP.

Related MCP server: agentmetal/mcp

Authentication (two paths — do not mix)

• AI agents (this MCP): call register_account — the agent supplies its own credentials and receives a Bearer token immediately. No email, no OTP, no human step. Send it as Authorization: Bearer <token>.

• Humans (website only): passwordless email OTP — for people in a browser. Agents cannot use this (they cannot read email).

An MCP agent must use register_account, never the email-OTP human flow. If a model suggests "wait for a code from your email", that is wrong for agents — the agent already holds its token from register_account.

Quickstart

Claude Code — one command:

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

Generic MCP client — JSON config:

{
  "mcpServers": {
    "eqvps": {
      "url": "https://mcp.eqvps.com/mcp",
      "transport": "streamable-http"
    }
  }
}

Remote server — no install, no Docker. Point any MCP client at the endpoint above. Machine-readable manifest: /.well-known/mcp.json (live at https://eqvps.com/.well-known/mcp.json).

Then, in plain language:

Register an EQVPS account, show me plans, create a crypto top-up invoice for $20; once I confirm payment, order an Ubuntu 24.04 VPS and give me its SSH access.

• The agent does everything via tools except funding: a human sends crypto to the top-up invoice once. After the balance is funded, repeat orders are fully hands-off.

Tools (21)

Typical agent flow

list_plans → register_account → topup_balance (pay crypto) → order_vps → get_vps_status (SSH access) → operate (power_vps, set_hostname, reinstall_vps, get_vps_metrics, cancel_service).

Example client

This repository documents the hosted EQVPS MCP server (mcp.eqvps.com) and ships a minimal example client — you do not run a server yourself. To try the connection and list plans:

npm install
node examples/connect.mjs      # connects to mcp.eqvps.com, prints tools + list_plans

Point EQVPS_MCP_URL at a different endpoint if needed. The example uses only the public list_plans tool; authenticated tools need a Bearer token from register_account.

About

EQVPS is API-native, pay-per-use VPS hosting for humans and AI agents. NVMe storage, full root, instant deploy, EU nodes. Crypto payment (USDC/USDT on Base and Ethereum), no KYC. Registered in the Official MCP Registry as io.github.Poiuyhje/eqvps.

License

MIT.