TunnelHQ

com.tunnelhqPublished by tunnelhq.comOfficial publisherv1.0.0Updated Nov 11, 2026

VPN server monitoring: test VPN configs, see failures and manage incidents from your AI assistant.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server that lets an assistant test VPN configurations, review failures and manage incidents for VPN servers.

What you can do
  • Test VPN configurations and check whether they work
  • Review VPN connection failures and their details
  • Manage incidents related to VPN servers
  • No individual tools are listed in the registry entry, so exact actions are unconfirmed
When to use it
Useful if you run VPN servers and want to check configuration health, look into failures or handle incidents from within an AI assistant instead of a separate dashboard.
Requirements
A remote MCP endpoint at mcp.tunnelhq.com over streamable HTTP; OAuth sign-in is required. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to a TunnelHQ account, so the assistant can act on your VPN monitoring data. Incident management may change or close records; confirm before letting it modify anything.

Installation

In SourceWeft

  1. Open TunnelHQ in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.tunnelhq%2Ftunnelhq/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "tunnelhq": {
      "type": "http",
      "url": "https://mcp.tunnelhq.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 11, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.