Skip to main content
Glama
cheeeee

vpn-mcp

by cheeeee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to vpn-mcp

No user-submitted related servers found.

    Related Servers

    • nodemaven-mcp

      Artirain
      A
      license
      A
      quality
      B
      maintenance
      MCP server that lets AI agents route web requests through NodeMaven residential and mobile proxies, with tools for geo-targeted fetching, proxy checking, and location/usage queries.
      5
      MIT
    • StealthSurf MCP Server by StealthSurf-VPN

      StealthSurf MCP Serverofficial

      StealthSurf-VPN
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI agents to manage VPN configurations, cloud servers, and account settings through the StealthSurf API. It supports natural language commands for tasks such as creating VPN configs, managing cloud server orders, and performing device security audits.
      3
      MIT
    • aethyn-browser-mcp by aethynio

      aethyn-browser-mcpofficial

      aethynio
      A
      license
      A
      quality
      C
      maintenance
      An MCP server enabling AI agents to drive a real browser through residential proxies with per-task geo (country/city) and sticky identity, all chosen at call time.
      10
      24 npm
      3
      MIT

    • MCP Browser

      wgarrido
      A
      license
      A
      quality
      C
      maintenance
      MCP server that lets AI assistants browse the web through your real Chrome with your cookies, sessions, and fingerprint, avoiding bot detection and CAPTCHAs. Enables web browsing, content extraction, and multi-step workflows via persistent tabs.
      15
      5 npm
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a distinct and clear purpose within the VPN lifecycle: activation, connection, disconnection, fetching through VPN, node listing, setup, status checking, and node switching. There is no overlap or ambiguity; an agent can easily select the right tool for each step.

    Naming Consistency5/5

    All tool names follow a consistent 'vpn_' prefix with descriptive action suffixes (e.g., activate, connect, fetch). The naming pattern is uniform and predictable, making it easy for an agent to understand and navigate the toolset.

    Tool Count5/5

    With 8 tools, the server is well-scoped for managing a VPN service. Each tool serves a specific function in the activation, setup, connection, usage, and management workflow, with no redundant or missing operations for the domain.

    Completeness5/5

    The toolset provides complete coverage for the VPN domain: account activation, setup, connection, disconnection, fetching through the VPN, node listing, status monitoring, and node switching. There are no obvious gaps, enabling agents to handle the full lifecycle without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources