Skip to main content
Glama
BreezeDelegate

wisp-mcp

by BreezeDelegate
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to wisp-mcp

No user-submitted related servers found.

    Related Servers

    • anthropic_skill

      williamchek
      F
      license
      Not graded
      quality
      D
      maintenance
      A robust, lightweight Model Context Protocol (MCP) server designed to empower your AI Agents with context-awareness, safe execution sandboxes, and dedicated thought logs.
      -

    • RL-MCP

      rlefko
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides AI models with structured access to external data and services, acting as a bridge between AI assistants and applications, databases, and APIs in a standardized, secure way.
      2
      -

    • MCP Toolkit

      zxfgds
      A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive Model Context Protocol server implementation that enables AI assistants to interact with file systems, databases, GitHub repositories, web resources, and system tools while maintaining security and control.
      23 npm
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 35 tools

    Disambiguation5/5

    Every tool targets a distinct operation or resource: file reads/writes/deletes, backups, databases, power, console, settings, etc. Even closely related file tools (read_file, read_file_chunk, read_log_tail, find_in_file) have clearly different purposes, so an agent can reliably select the right one.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern (e.g., list_servers, create_backup, delete_file). A few nouns stand alone (capabilities, server_details, server_status, audit_logs, file_fingerprint, backup_download), which is a minor but noticeable deviation from the predominant style.

    Tool Count2/5

    With 35 tools, the set is well beyond the 25+ threshold and feels heavy. While the server covers multiple domains (files, backups, databases, console, settings), the sheer number of tools makes it more complex to navigate than a typical MCP server, and many could be consolidated or exposed via subcommands.

    Completeness4/5

    The tool surface is comprehensive for server management: CRUD for files, backups, databases, plus power, console, monitoring, and settings. A few gaps exist (no server creation/deletion, no user/permission management), but these are likely outside the intended read-only or operational scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources