Skip to main content
Glama
aplaceforallmystuff

MCP Threat Intel Server

greynoise_ip

Identify if an IP address is internet background noise or a targeted threat using GreyNoise intelligence.

Instructions

Check if an IP is internet background noise or a targeted threat (GreyNoise)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ipYesIP address to check

Implementation Reference

  • The handler function for the greynoise_ip tool. It extracts the 'ip' argument, calls the GreyNoise community API endpoint, and returns the JSON result. Works without an API key (keyless community endpoint), but if GREYNOISE_API_KEY is set, it's passed in the request header for higher rate limits.
    case "greynoise_ip": {
      const { ip } = args as { ip: string };
    
      const result = await apiRequest<unknown>(
        `${config.greynoise.baseUrl}/community/${ip}`,
        config.greynoise.apiKey
          ? { headers: { key: config.greynoise.apiKey } }
          : {}
      );
    
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
  • The tool definition and input schema for greynoise_ip. Defines the tool name, description ('Check if an IP is internet background noise or a targeted threat'), and input schema requiring an 'ip' string parameter.
      name: "greynoise_ip",
      description: "Check if an IP is internet background noise or a targeted threat (GreyNoise)",
      inputSchema: {
        type: "object" as const,
        properties: {
          ip: {
            type: "string",
            description: "IP address to check",
          },
        },
        required: ["ip"],
      },
    });
  • src/index.ts:227-242 (registration)
    Registration of the greynoise_ip tool. The tool is conditionally pushed into the TOOLS array only if services.greynoise is enabled (always true, since GreyNoise community endpoint works without auth).
    if (services.greynoise) {
      TOOLS.push({
        name: "greynoise_ip",
        description: "Check if an IP is internet background noise or a targeted threat (GreyNoise)",
        inputSchema: {
          type: "object" as const,
          properties: {
            ip: {
              type: "string",
              description: "IP address to check",
            },
          },
          required: ["ip"],
        },
      });
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must disclose behavioral traits. It only implies a lookup operation but does not mention side effects, rate limits, authentication requirements, or whether results are cached.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, focused sentence that front-loads the purpose. No unnecessary words or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one parameter and no output schema, the description is complete enough to convey the core functionality. It could mention API key requirements, but the current text is adequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds meaningful context by explaining the classification (noise vs. threat), which goes beyond the schema's simple 'IP address to check'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Check'), the resource (an IP), and the two possible outcomes (internet background noise or targeted threat). This distinguishes it from sibling tools that check domains, hashes, or URLs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, such as threatintel_lookup_ip. There is no mention of prerequisites or conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aplaceforallmystuff/mcp-threatintel'

If you have feedback or need assistance with the MCP directory API, please join our Discord server