vpn-mcp
Related Servers
Alternatives to vpn-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables web-based ChatGPT and other MCP-capable AI clients to read, edit, search, and run code in projects open in local VS Code through a one-click public HTTPS tunnel. Provides 33 tools spanning file operations, code intelligence, terminals, and Git, with multi-window routing that follows or locks onto the active project.3MIT
- AlicenseNot gradedqualityBmaintenanceThis MCP server enables web AI assistants such as ChatGPT, Claude Web, and Gemini Web to securely connect to local IDEs and workspaces for file edits, terminal and Git commands, and multi-project navigation through an outbound bridge with zero inbound ports.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables Gemini CLI and ChatGPT to inspect, modify, and run commands in local code projects through MCP, including Git operations and multi-project session binding with secure remote access.160 npmMIT
- AlicenseAqualityBmaintenanceEnables ChatGPT web to use local tools like file reading, command execution, and patch application through an MCP server over OpenAI Secure MCP Tunnel.62MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to reach tools running on any machine or existing MCP server, even behind NAT, using only outbound connections with no open ports, tunnels, or third-party services, while keeping oversized responses out of the model's context and enforcing per-token access policies.9 npmAGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables ChatGPT and Claude to securely connect to existing Codex sessions across local and remote development hosts via a self-hosted MCP gateway.Apache 2.0
TDQS
Scored across 8 tools
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.
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.
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.
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.