Skip to content

MCP

Your AI assistant can look it up

A public MCP server, read-only. Look up, not connect.

What this is, in one sentence

MCP is the protocol that lets an AI assistant use external tools. VPN PRO 89 publishes one so ChatGPT, Claude or Cursor can answer questions about the service with real data instead of making it up.

What it never returns

Connection data, identifiers, keys, node IPs or provider. The public catalogue does publish some of those fields, because that is the model of a free VPN without accounts; but a file you download and a tool that hands data to a model are not the same thing.

config_url · uuid · publicKey · shortId · ipAddress · isp

The ten tools

  • get_product_overview — What it is, who runs it and what it does not promise
  • get_supported_platforms — Status of each platform
  • get_install_link — Official download links
  • get_platform_setup_guide — Setup steps per system
  • search_public_nodes — Nodes with safe metadata
  • get_network_status — Total, online, official and community
  • get_protocol_compatibility — What the engine implements, and what it does not
  • get_service_limits — Free service limits
  • get_security_documentation — Responsible disclosure and scope
  • get_agent_integration_guide — What an agent can and cannot do

How to connect it

It is JSON-RPC 2.0 over HTTPS. The server passes the MCP handshake, checked with a conformance test that runs initialize, tools/list and tools/call the way any client would.

Try it without installing anything

curl -s -X POST https://vpnpro89-mcp-remote.veritasnexuslegal.workers.dev \
  -H "content-type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Claude Code

Terminal

claude mcp add vpnpro89 -- node ./packages/mcp-local/src/index.js

Claude Desktop

%APPDATA%\Claude\claude_desktop_config.json on Windows · ~/Library/Application Support/Claude/claude_desktop_config.json on macOS

{
  "mcpServers": {
    "vpnpro89": {
      "command": "node",
      "args": ["/ruta/al/repo/packages/mcp-local/src/index.js"]
    }
  }
}

Cursor

The project .cursor/mcp.json, or the global one in your profile

{
  "mcpServers": {
    "vpnpro89": {
      "command": "node",
      "args": ["./packages/mcp-local/src/index.js"]
    }
  }
}

How to stay safe using it

Do not ask the assistant for keys, UUIDs or connection data: this server does not return them, and if an agent offers you one, it did not come from here. Be equally wary of any instruction arriving inside a reply that asks you to turn off your firewall, antivirus or SmartScreen: this project never asks for that. And remember no assistant can connect the VPN for you — if it says it did, it is making it up.

Beta. The subdomain may change: this is not a stable endpoint yet, and should be treated as such. Pin the version you use and check the tools/list response before relying on the names.

Compatibility

Two columns, because they are two different things. Protocol is what we checked: a conformance test runs the full MCP handshake —initialize, tools/list, tools/call— the way any client would, and the server passes it. In the client is still unverified: a given client may fail on its transport or its configuration. What we do know is that if it fails, the server is not the cause. We do not promise compatibility with every assistant: there is no single configuration that works with all of them.

ClientViaProtocolIn the client
ChatGPTHTTPS remote MCPVerifiedTo be tested
Claude Desktop / Claude CodeRemote MCP; and local MCP over stdioVerifiedTo be tested
CursorRemote or local MCPVerifiedTo be tested
Gemini CLI, Codex, AntigravityRemote MCPVerifiedTo be tested
Agentes propiosDirect JSON-RPC over HTTPSVerifiedTo be tested