Remnawave Tools MCP
Related Servers
Alternatives to Remnawave Tools MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceTurns OpenAPI specs into MCP tools with secure defaults, risk inspection, confirmation gates, response limits, audit logging, and secret redaction.-
- AlicenseBqualityCmaintenanceSecurity gateway that wraps any MCP server with per-tool policies, approval gates, and optional Ed25519-signed decision receipts. Shadow mode logs every tool call without blocking; enforce mode applies block, rate-limit, and minimum-tier rules. Receipts are independently verifiable offline with no accounts needed.51,279 npm10MIT
- AlicenseNot gradedqualityAmaintenanceOperates Rancher-managed Kubernetes through any MCP client with capability detection, generic resource access, and curated workflows, wrapped in an audit-logged, rate-limited, confirmation-guarded safety model.1MIT
- FlicenseNot gradedqualityBmaintenanceProvides a secure MCP boundary for AI agents, intercepting and validating tool calls, redacting secrets, and requiring human approval for sensitive actions with a tamper-evident audit trail.-
- FlicenseNot gradedqualityCmaintenanceWraps your existing MCP servers and checks each tool call against policy and live state before it runs. Allow, block, or require a refresh, with a reason the agent can act on.5-
- AlicenseNot gradedqualityBmaintenanceMCP proxy that journals mutating tool calls and enables undo via compensation. It adds checkpoint, list_changes, undo_to, and explain_blast_radius meta-tools while forwarding all original downstream tools unchanged.MIT
TDQS
Scored across 152 tools
Most tools target distinct resource-action pairs, but there are overlaps like legacy vs non-legacy methods and multiple user lookup tools (by email, id, username, etc.) that could confuse selection.
All tools follow the exact pattern remnawave_<resource>_<action> with snake_case, making naming perfectly predictable and consistent.
With 152 tools, the surface is extremely bloated. Many tools are redundant or overly granular (e.g., multiple bulk operations, legacy methods), making it unwieldy for agents.
Covers major domains like users, nodes, hosts, billing, and profiles, but includes many niche or redundant operations while lacking some lifecycle operations (e.g., no straightforward user delete? Actually there is users_delete, so it's okay but uneven).