Skip to main content
Glama
KoruShield

Koru Shield MCP Server

Official
by KoruShield
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Koru Shield MCP Server

No user-submitted related servers found.

    Related Servers

    • nextdns-mcp

      dmeiser
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to manage NextDNS profiles, settings, logs, analytics, and security configurations through 70+ operations via the Model Context Protocol.
      8
      15
      MIT

    • MCP Pi-hole Server

      aplaceforallmystuff
      A
      license
      A
      quality
      C
      maintenance
      Connects AI assistants to Pi-hole network-wide ad blocker, enabling monitoring of DNS traffic statistics, controlling blocking settings, managing whitelist/blacklist domains, viewing query logs, and performing maintenance tasks through natural language.
      16
      84 npm
      8
      MIT

    • Cloudflare Control

      josephtandle
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage Cloudflare infrastructure including DNS records, cache purging, SSL settings, Workers, and analytics through the Cloudflare API. Eliminates dashboard context-switching by allowing natural language control of domain management and infrastructure operations.
      -

    • pihole-mcp

      ranklancer
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query and manage Pi-hole v6 DNS ad-blocker instances, including logs, allow/deny lists, groups, and stats. Supports multiple Pi-hole instances from a single endpoint.
      36 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.4/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: profiles, rules, filter categories, schedules, logs, analytics, devices, and account info. Overlap is minimal; simulate_policy, get_logs, and analytics_summary serve different query intents. No two tools appear to do the same thing.

    Naming Consistency4/5

    Nearly all tools follow a consistent verb_noun snake_case pattern (list_profiles, create_rule, set_filter_category). The only deviation is analytics_summary, which is a noun phrase rather than verb_noun. Still highly readable and predictable.

    Tool Count4/5

    16 tools is slightly above the ideal 3–15 range but reasonable given the multiple sub-resources (profiles, rules, categories, schedules, devices, analytics, account). Each tool maps to a clear operation, with no obvious redundancy.

    Completeness2/5

    The surface lacks profile lifecycle operations (create/update/delete profile), rule and schedule updates, and device enrollment/removal. Only list operations exist for devices and entitlements. These gaps will force agents to work around missing CRUD for core resources.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources