Skip to main content
Glama
Sign In
Kali Linux MCP Server

Kali Linux MCP Server

by AlessandroAnnini
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

vpn_connect

Connect to Mullvad VPN to anonymize security testing. Choose WireGuard or OpenVPN protocol and server location.

Instructions

Connect to Mullvad VPN for anonymous security testing

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vpn_connect"
  }
}

Input Schema

NameRequiredDescriptionDefault
serverNoServer location (e.g., 'se', 'nl ams') - defaults from .env
protocolNoVPN protocol (default: wireguard)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must disclose behavioral traits. It only states 'connect' without details on authentication, side effects, or whether a previous connection must be disconnected first.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence with no waste, but it lacks structure such as separate sections for purpose and usage.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With two parameters, no output schema, and no annotations, the description covers the basic purpose but misses contextual details like connection time, prerequisites, or what happens on failure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for both parameters. The description adds no additional meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the action (connect), the specific service (Mullvad VPN), and the context (anonymous security testing). It distinguishes well from sibling tools like vpn_disconnect and vpn_status.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'for anonymous security testing' implies a use context, but there is no explicit guidance on when to use this tool versus alternatives like vpn_disconnect, nor any mention of prerequisites or conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools