Skip to main content
Glama
nickjlucker

mcp-greynoise

by nickjlucker
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to mcp-greynoise

No user-submitted related servers found.

    Related Servers

    • greynoise-mcp-server by GreyNoise-Intelligence

      greynoise-mcp-serverofficial

      GreyNoise-Intelligence
      A
      license
      A
      quality
      A
      maintenance
      MCP server for GreyNoise threat intelligence, enabling IP analysis, GNQL queries, tag and vulnerability lookups, and session/pcap retrieval via natural language.
      48
      126 npm
      5
      MIT

    • mcp-ipquery

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables IP address lookups and risk assessments for IPv4/IPv6, providing geolocation, ISP/ASN, and security flags such as VPN, proxy, Tor, datacenter, and mobile with a risk score.
      184 npm
      MIT

    • MCP AbuseIPDB Server

      alephnan
      A
      license
      A
      quality
      D
      maintenance
      Provides threat intelligence lookups against the AbuseIPDB database, enabling IP reputation checks, CIDR block analysis, and log enrichment. It features intelligent caching and rate limiting to efficiently manage API usage for security analysis and automated workflows.
      5
      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

    A3.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one checks a single IP address, the other checks multiple IPs in bulk. An agent can easily distinguish between them based on the singular/plural naming and the explicit descriptions.

    Naming Consistency5/5

    Both tools follow the consistent pattern of 'check_' followed by a noun indicating the input type ('ip' vs 'ips'). The naming is predictable and uses consistent snake_case throughout.

    Tool Count3/5

    With only two tools, the server feels minimal for its domain. While both tools are necessary and well-scoped, a more comprehensive IP intelligence server would typically benefit from additional tools (e.g., contextual enrichment, history). The count is borderline thin.

    Completeness3/5

    The tool set covers the basic use case of checking IPs against GreyNoise data, both individually and in bulk. However, it lacks other common operations like fetching detailed threat context, searching by tags or queries, or retrieving known-good RIOT entries specifically. Notable gaps exist for a more complete threat intelligence surface.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources