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
erebrus-mcp
Officialby NetSepio
Related Servers
Alternatives to erebrus-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server for managing TON blockchain sites, deployments, DNS, and storage via the Resistance Tools platform.MIT
- AlicenseAqualityCmaintenanceAn MCP server for creating, settling, disputing, and refunding escrows on EVM chains.85 npmApache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server for VoidSend enabling AI agents to send and receive end-to-end encrypted messages.7 npmMIT
- AlicenseAqualityDmaintenanceMCP server for uploading, listing, and retrieving files on S3-compatible storage (AWS S3, DigitalOcean Spaces) with public/private access and temporary URLs.415 npmMIT
Swarm MCPofficial
AlicenseAqualityDmaintenanceMCP server for Ethereum Swarm decentralized storage. Provides 12 tools for uploading and downloading data and files, managing postage stamp batches, and working with Swarm feeds — all via the Bee API. Works with the public Swarm gateway or a local Bee node.712 npm9ISC
TDQS
B3/5.0
Scored across 40 tools
Disambiguation3/5
Many tools overlap in purpose: multiple node listing tools (org_nodes_list, operator_nodes_list, nodes_directory) and two VPN client creation routes (vpn_client_create, org_vpn_client_create) could confuse an agent. Detailed descriptions help, but the sheer number of similar list/create operations creates ambiguity.
Naming Consistency2/5
Naming is inconsistent: some tools use noun_verb (org_create, apikey_revoke), others use compound prefixes (drop_upload_content, auth_email_login_start), and a few are standalone (whoami, gateway_health). Verb placement and word order vary, making the pattern hard to predict.
Tool Count2/5
With 40 tools, the server feels over-scoped even for a broad domain like VPN plus file storage. Many tools are near-duplicates distinguished only by auth scope (user vs org vs API key), which could have been consolidated into fewer, more flexible tools.
Completeness3/5
Core workflows (auth, org creation, VPN client lifecycle, Drop upload/list/delete) are covered, but there are notable gaps: no org update/delete, no node removal, no Drop file download, and no upload cancellation. These missing operations could force agents to use workarounds.
Maintenance
ActivityStale
ResponsivenessNo issues