Skip to main content
Glama
BearstOzawa

@bearst/lucky-mcp-server

by BearstOzawa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @bearst/lucky-mcp-server

No user-submitted related servers found.

    Related Servers

    • Technitium DNS MCP

      X1pheR
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables managing and observing Technitium DNS Server through MCP, including read-only or read-write tool surfaces, scoped bearer authentication, audit logging, and confirmation gates for destructive operations.
      MIT

    • mcp-gateway

      shamalawy
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables centralized management, proxying, and aggregation of multiple MCP servers behind unified endpoints, with a web GUI, server groups, tool filtering, and lifecycle controls.
      9 npm
      Apache 2.0

    • AccelMCP

      t-ogawa-dev
      F
      license
      Not graded
      quality
      B
      maintenance
      An MCP server with HTTP/stdio support, a web admin panel for managing services, capabilities, and user permissions with Bearer token authentication, enabling relay and access control for MCP tools.
      -

    • OPNsense MCP Server

      lucamarien
      A
      license
      A
      quality
      B
      maintenance
      A secure MCP server for managing OPNsense firewalls through AI assistants. Provides 81 tools across system, firewall, network, DNS, DHCP, VPN, HAProxy, services, diagnostics, and security domains.
      81
      125 PyPI
      21
      MIT

    • MCP Gateway

      kyopread
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables centralized management of external MCP servers with Keycloak authentication, per-user and per-group access controls, and audit logging.
      9 npm
      -

    • mcp-gateway

      R0Wi
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables clients to access multiple backend MCP servers through a single endpoint, with OAuth 2.1 authorization, namespaced tools, and secure credential management.
      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

    C2.2/5.0

    Scored across 61 tools

    Disambiguation4/5

    Most tools follow a clear pattern of module plus action (e.g., list_web_rules, upsert_cron_job), making them distinguishable. A few pairs like list_storage vs list_local_paths or logs_stats vs query_logs could be confused, but overall the boundaries are mostly clear.

    Naming Consistency5/5

    All tools share the lucky_ prefix and use lowercase snake_case with consistent action verbs: list, get, upsert, set, delete, run, sync, wake. Minor deviations like cron_logs instead of get_cron_logs do not break the predictable pattern.

    Tool Count1/5

    61 tools is well beyond the 50+ threshold and imposes a huge cognitive load on agents. Even though the tools span multiple modules, the sheer number makes the set feel excessive and hard to navigate.

    Completeness2/5

    The surface is uneven: some modules have full CRUD (cron, port forwards), but many lack common operations such as deleting WoL devices, creating/removing DDNS tasks, deleting certificates, or managing security groups. The generic api_call escape hatch is restricted and cannot fully compensate.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources