Skip to main content
Glama
Baneado98

ip-doctor

by Baneado98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to ip-doctor

No user-submitted related servers found.

    Related Servers

    • mcp-server-dns

      ofershap
      A
      license
      A
      quality
      D
      maintenance
      MCP server for DNS lookups, reverse DNS, WHOIS, and domain checks. Zero auth, zero config.
      5
      32 npm
      3
      MIT

    • domain-mcp

      itsalfredakku
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server for domain availability checks, WHOIS lookups, and domain suggestions using RDAP and TCP port 43. It allows users to perform bulk checks and retrieve registration details across multiple TLDs without requiring an API key.
      121 npm
      -

    • intodns-mcp

      RoscoNL
      A
      license
      A
      quality
      A
      maintenance
      MCP server for IntoDNS.ai providing 36 free tools for DNS, DMARC, SPF, DKIM, BIMI, DNSSEC, MTA-STS, FCrDNS, blacklist and email security checks. Citation-grade report snapshots with content hashes. No API key required.
      45
      359 npm
      2
      MIT

    • dnsdoctor

      Baneado98
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that checks SPF, DKIM, DMARC, and MX records for a domain, returning a health verdict and specific DNS fixes to improve email deliverability.
      1
      MIT

    • OSINT MCP Server

      CloudWaddie
      A
      license
      D
      quality
      D
      maintenance
      A comprehensive MCP server providing tools for IP, domain, email, and image-based open-source intelligence. It integrates services like Shodan, VirusTotal, and HaveIBeenPwned to facilitate advanced security research and data gathering.
      56
      82 npm
      ISC
    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 2 tools

    Disambiguation5/5

    The two tools are clearly distinct: check_ip handles single targets while check_many handles batch processing. Descriptions explicitly differentiate the use cases.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern: 'check' + target type (ip or many). Simple and predictable.

    Tool Count3/5

    Only 2 tools for IP/domain reputation checking feels thin. While the core functionality is covered, the server would benefit from additional tools for advanced features like whitelist management or historical queries.

    Completeness4/5

    The tool set covers the primary use case of live reputation checking for single and multiple targets. Minor gaps exist (e.g., no tool for checking URLs or managing blocklists), but the domain is simple and adequately served.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources