A
licenseA
qualityB
maintenanceMCP server for Remnawave panel API. Manage VPN users, nodes, hosts, and system stats from Claude Code or any MCP-compatible client.
34
MIT
registry
Server Details
Cloud-hosted MCP server for URnetwork VPN and Proxy
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A3.6/5.0
Tool DescriptionsB
Average 3.1/5 across 1 of 1 tools scored.
Server CoherenceA
Disambiguation5/5
Only one tool exists, so there is no possibility of confusing it with another tool. The purpose is clearly described.
Naming Consistency5/5
The single tool name 'providerLocations' follows a clear camelCase convention, and with only one tool, the naming is inherently consistent.
Tool Count4/5
A single tool is appropriate for the narrow purpose of fetching provider locations, though the server feels minimal. It does not exceed or fall short of its stated scope.
Completeness5/5
The tool fully covers its domain: retrieving available provider locations. There are no missing CRUD operations because the domain is a simple read-only query.
Available Tools
1 toolproviderLocationsBInspect
Get available URnetwork VPN provider locations
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Location name to search for (e.g. 'New York', 'Tokyo', 'US East'). Supports fuzzy matching. An empty query returns a list of available countries. |
Tool Definition Quality
B3.1/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations present, the description must bear the full burden of behavioral disclosure. It only says 'Get available ... locations' with no details about return structure, potential errors, rate limits, or whether the operation is read-only. The query behavior (fuzzy matching, empty query semantics) is only in the schema, not the description.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence that communicates the essential purpose without wasted words. It is appropriately sized for a simple lookup tool.
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?
For a simple read-only lookup with one parameter and a fully documented schema, this is minimally complete. However, with no output schema and no mention of response format or pagination, an agent might not know exactly what to expect beyond 'locations'. It is adequate but leaves some gaps.
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?
The schema provides 100% coverage of the parameter 'query', including examples and behavior like fuzzy matching and empty query semantics. The description adds no parameter-level detail, so the schema carries the load. Baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action and resource: 'Get available URnetwork VPN provider locations'. It uses a specific verb ('Get') and names the resource, but does not differentiate from sibling tools because none are provided. The purpose is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives, as there are no sibling tools listed. The description does not explain what kinds of queries are appropriate or when to use an empty query. The only usage context comes from the parameter schema, not the description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
erebrus-mcpofficial
AlicenseBqualityBmaintenanceMCP server for deploying and managing Erebrus decentralized VPN nodes, API keys, and file uploads.40GPL 3.0- AlicenseAqualityBmaintenanceThe first MCP Server dedicated to Bitcoin ecosystem236MIT
- Alicense-qualityAmaintenanceOpen-source, engine-agnostic MCP server shared by Unity-MCP, Godot-MCP, and Unreal-MCP.9Apache 2.0