eqvps

No-KYC crypto VPS an AI agent buys and controls entirely over MCP — register, pay in USDC/USDT, provision, get root.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • List Plans: List all available VPS plans (catalog) with pricing, specs and the OS images each plan can boot. No authentication needed. Use this first to pick a `product` slug and an `os_id` for `order
  • Register Account: Create a new EQVPS customer account with first_name, last_name, email. Returns a bearer `token` — STORE IT SAFELY: it is your only credential. Send it as `Authorization: Bearer <toke
  • Login: Log in with email + password. Returns a bearer `token`. NOTE: accounts created via register_account have NO password by default — reuse the token from register instead. If you have no password,

What data it sees

Do you need an account

No: the server works without sign-in

No-KYC crypto VPS an AI agent buys and controls entirely over MCP — register, pay in USDC/USDT, provision, get root. 27 tools. EU servers from $3/mo.

How to connect

How to connect eqvps to Claude

The server address to paste into Claude settings:

https://eqvps-7560.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect eqvps to ChatGPT

The server address to paste into ChatGPT settings:

https://eqvps-7560.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect eqvps to Cursor

The server address to paste into Cursor settings:

https://eqvps-7560.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (27)

Raw names from tools/list. Only developers need these.

list_plansList all available VPS plans (catalog) with pricing, specs and the OS images each plan can boot. No authentication needed. Use this first to pick a `product` slug and an `os_id` for `order_vps`.
register_accountCreate a new EQVPS customer account with first_name, last_name, email. Returns a bearer `token` — STORE IT SAFELY: it is your only credential. Send it as `Authorization: Bearer <token>` on every following request. No password or human step is needed. If you may lose the token, call `set_password` once (while authenticated) to also enable email+password `login` as a backup.
loginLog in with email + password. Returns a bearer `token`. NOTE: accounts created via register_account have NO password by default — reuse the token from register instead. If you have no password, first call `set_password` (while still authenticated with your register token), or use the human email-OTP flow in a browser.
set_passwordSet a password for THIS account (the one your bearer token belongs to). Accounts from register_account have no password by default — the bearer token is the credential. Call this ONCE to enable email+password `login` as a recovery method in case the token is lost. Needs only the new password (min 8 chars, letters+numbers) — no current password the first time. If a password was already set, this returns 409 (use change-password instead).
whoamiReturn the authenticated account profile (id, name, email). Use to verify the bearer token is valid.
get_balanceReturn the account's prepaid credit balance and currency. `order_vps` spends from this balance automatically when it is sufficient.
topup_balanceCreate a top-up invoice and return a `checkout_url` (PayRam crypto checkout). The balance is credited automatically once the on-chain payment confirms. `amount` is in account currency (USD); minimum and maximum are enforced server-side. Only one unpaid top-up may exist at a time.
order_vpsOrder a VPS. `product` = plan slug from list_plans; `os_id` = an OS id from that plan's images. Optional `hostname` and `ssh_key` (public key — strongly recommended so you get key-based root login). Branching on the response: • `paid_from_balance: true` → the prepaid balance covered it; the server is provisioning. Poll `get_vps_status` until status is `active` and the VM is reachable. • `paid_from_balance: false` → balance was insufficient; an unpaid `invoice` is returned. Call `pay_invoice` with `invoice.id` to get a crypto `checkout_url`, OR `topup_balance` then re-order.
pay_invoiceInitiate payment for an owned, unpaid invoice. Returns a PayRam `checkout_url`; the invoice settles (and the VPS provisions) automatically once the on-chain payment confirms.
list_vpsList the account's ACTIVE VPS services — active, provisioning, and suspended servers (deleted/cancelled are excluded). Use the `id` as `service_id` for the management tools. If a server is missing from this list it has been deleted — do not query its status or try to manage it.
get_vps_statusGet full detail for one VPS: status, specs, live VM state/uptime, and SSH access info (host, port, ready-to-paste `command`). ROOT PASSWORD (keyless VPS): call with `reveal: true` to retrieve it. It is shown ONCE, and only after the VM has finished booting — at that moment the password is applied to the live VM, so it is guaranteed to work. While the VM is still booting the response carries `password_pending: true` and NO password; just call again with `reveal: true` in ~30-60s (the one-time reveal is NOT spent until a password is actually returned — no reset or reboot needed). Without `reveal`, `password_available: true` means a password is waiting to be revealed. If you supplied an SSH key at order time, log in with that key (no password); `ssh_ready: false` means the VM is still booting — retry shortly. Use `reset_password` ONLY if the password is lost. Poll this (without `reveal`) after `order_vps` to watch provisioning reach `active`. NAT plans (no dedicated IP): the SSH `port` shown is an EXTERNAL DNAT port forwarded to the VM internal port 22 (`internal_port` in the response). If you configure a host firewall, allow the INTERNAL port — `ufw allow OpenSSH` — NOT the external port, or `ufw enable` will lock SSH out. See `firewall_note` in the response.
power_vpsPower-control a VPS: `start`, `stop` or `reboot`.
set_hostnameSet the VPS hostname (valid DNS label; applied on next reboot/rebuild).
reset_passwordRotate the root password. The new password is applied to the LIVE VM immediately via the guest-agent (no reboot) and works within ~10-30s; the OLD password stops working. REQUIRES confirm = exact hostname (from get_vps_status) or 'DELETE'. Agent must confirm with the human before calling. Use this ONLY if the password was lost — NOT because SSH was not instant on a fresh order (a new VM needs ~60s to boot; poll get_vps_status with reveal:true instead). New password is NOT in this response — read it ONCE via get_vps_status (reveal:true); also emailed.
reinstall_vpsDESTRUCTIVE — all data is lost. REQUIRES confirm = exact hostname (from get_vps_status) or 'DELETE'. Agent must explicitly confirm with the human before calling. Wipes and reinstalls the VPS with the given OS image (`os_id` from list_plans). Provisioning runs asynchronously; poll `get_vps_status`.
get_vps_metricsTime-series resource metrics (CPU %, memory, network, disk) for a VPS. `timeframe` ∈ hour|day|week|month (default hour).
cancel_serviceCancel a VPS. DEFAULT `end_of_period`: the server stays active until the end of the already-paid period, then is simply not renewed — NO data loss now, safe. `immediate` DESTROYS the VM and ALL data right away, permanently and irreversibly, and REQUIRES `confirm` set to the exact server hostname (see get_vps_status). Use end_of_period unless you explicitly intend to wipe the server now. On `immediate`, the unused portion of the already-paid period is refunded to your account balance (see `refund_amount` in the response).
delegate_serviceGrant OPERATOR access to one of YOUR VPS to another person by email (they can power/reinstall/console/hostname/rdns, but NOT renew, cancel or change billing). Sends them an invitation with an accept link. Optional `expires_days` for time-limited access. Owner-only.
accept_delegationAccept a delegation invitation using the `token` from the invite link. Creates/links your account and grants operator access. Returns a bearer token for the delegated account.
list_delegationsList outgoing delegations you (the owner) have granted on your services — who has operator access to what, and its status.
list_delegated_to_meList services other owners have delegated operator access to you — the VPS you can operate but don't own.
revoke_delegationRevoke a delegation by its id (owner revokes access, or a delegate declines their own). The other side is notified. Use list_delegations / list_delegated_to_me to find the id.
create_ticketOpen a support ticket with EQVPS. `subject` and `message` are required; optional `service_id` ties it to one of your VPS. The response includes the ticket `code` — use that with get_ticket / reply_ticket / close_ticket.
list_ticketsList your support tickets with status and last-message info. `last_message_author: "staff"` means support has replied since you last looked.
get_ticketRead one ticket and its full message thread. Each message has an `author`: `you` or `staff` — a `staff` message is a reply from support. Poll this to see new answers. The ticket code comes from create_ticket / list_tickets.
reply_ticketPost a reply on one of your tickets. Use the ticket code from create_ticket / list_tickets.
close_ticketClose one of your tickets. `rating` (1-5) and `comment` are OPTIONAL — you can close without rating. Use the ticket code from create_ticket / list_tickets.