Skip to main content
Glama
WYRE-AI

DNSFilter MCP Server

by WYRE-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to DNSFilter MCP Server

No user-submitted related servers found.

    Related Servers

    • action1-mcp

      molnkontakt
      A
      license
      A
      quality
      C
      maintenance
      Read-only MCP server for the Action1 RMM REST API, enabling access to endpoints, missing updates, vulnerabilities, installed software, policies, automations, and reports.
      21
      Apache 2.0

    • Crisp

      mcp-dir
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to Crisp customer support, live chat, CRM, and helpdesk data, including conversations, contacts, knowledge base, campaigns, operators, visitors, and site settings, via the official REST API v1.
      MIT

    • Teramind MCP Server

      WYRE-AI
      F
      license
      A
      quality
      B
      maintenance
      Enables read-only access to Teramind's employee-monitoring metadata, including computer and agent inventory, departments, alerts, anomaly rules, behavior policies, and monitoring profiles.
      16
      -

    • cf-mcp

      wojtekkura
      A
      license
      B
      quality
      D
      maintenance
      Read-only Cloudflare MCP server for SOC investigation, exposing Cloudflare services like WAF, bot management, analytics, and Zero Trust for querying and discovery.
      32
      MIT

    • tiktok-ads-mcp

      ysntony
      A
      license
      B
      quality
      D
      maintenance
      Provides read-only access to TikTok advertising data, including campaigns, ad groups, ads, and performance reports through the TikTok Business API.
      6
      42
      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.6/5.0

    Scored across 57 tools

    Disambiguation2/5

    The entity getters are distinct, but the report tools overlap heavily: dnsfilter_get_top_*, dnsfilter_get_total_*, and dnsfilter_get_total_*_organizations/users/agents variants are easy to confuse. For example, dnsfilter_get_total_requests_organizations and dnsfilter_get_total_organizations_requests are nearly indistinguishable from their names alone.

    Naming Consistency4/5

    Almost every tool follows a consistent dnsfilter_ + get/list/lookup + snake_case pattern, making the naming highly predictable. Minor inconsistencies exist, such as get_networks_geo being a plural/list-style operation and report names mixing top/total/qps without a strict semantic convention.

    Tool Count2/5

    57 tools is far above the typical well-scoped MCP surface, and many are minor permutations of the same reporting concept broken out by organization, user, network, collection, or agent. A much smaller set of parameterized report tools could likely cover the same capabilities.

    Completeness2/5

    The tool surface is almost entirely read-only: it retrieves organizations, networks, policies, categories, block pages, and extensive traffic reports, but has no create, update, delete, assign, or configuration-management tools. Agents cannot act on DNSFilter settings, only observe them, which is a significant gap for a management-oriented server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources