Skip to main content
Glama
ducampcarlos

claude-ops-mcp

by ducampcarlos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to claude-ops-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-headers

      CACTUSCASH
      A
      license
      A
      quality
      C
      maintenance
      Enables Claude to scan a website's HTTP security headers and receive an A–F grade against OWASP best practices, including per-header pass/warn/fail results and copy-paste fixes for missing headers.
      1
      MIT

    • scanner

      warOnSaaS
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to analyze public websites, follow progress, retrieve shareable reports, compare multiple URLs, list checks and recent activity, and surface fixes ranked by impact.
      Apache 2.0

    • SEO MCP PRO

      bypixels
      A
      license
      C
      quality
      B
      maintenance
      Enables Claude with 121 tools for website operations, Google Marketing, SEO, performance analysis, security auditing, monitoring, and accessibility testing.
      121
      10 npm
      MIT

    • NEL VEIL MCP

      NELPROINC
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to perform passive security scans on domains, checking email spoofing (DMARC/SPF/DKIM), TLS weaknesses, security headers, exposed files, and subdomain-takeover risk without needing an API key.
      7
      62 npm
      MIT

    • CyberMCP

      mrobi27
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to perform cybersecurity analysis including RDAP lookup, DNS analysis, SSL inspection, security header detection, and more, returning structured security reports.
      -
    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

    A4.2/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool targets a distinct diagnostic concern (DNS, mail auth, TLS, certs, HTTP, redirects, headers, sitemaps) and descriptions cross-reference to resolve overlaps, e.g. dns_lookup explicitly redirects users to mail_auth. The main ambiguity is between tls_inspect and cert_expiry (both cert-related) and between http_probe and redirect_chain (both follow redirects), though the depth-vs-bulk distinction is explained.

    Naming Consistency4/5

    All names use snake_case consistently, which is predictable. Minor deviation in that some follow noun_verb (dns_lookup, tls_inspect) while others use noun_noun (cert_expiry, redirect_chain, security_headers), but the convention is still readable and coherent.

    Tool Count5/5

    Eight tools is well-scoped for a read-only site/infra diagnostics server. Each tool earns its place covering a distinct layer (DNS, mail, TLS, HTTP, headers, sitemap) with no filler.

    Completeness4/5

    For a read-only diagnostics surface the coverage is strong: DNS, email auth, TLS/certs, HTTP health, redirects, security headers and sitemap auditing form a coherent lifecycle. Minor gaps exist (e.g. no latency/uptime sweep across many hosts, no whois/domain-level checks, no port-level diagnostics) but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources