Skip to main content
Glama
CloudWaddie

OSINT MCP Server

shodan_whois

Retrieve WHOIS information for IP addresses or domains using Shodan Labs data to identify ownership and registration details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesIP or domain to lookup WHOIS in Shodan Labs

Implementation Reference

  • Tool registration for "shodan_whois" in src/index.ts, which delegates to the shodanClient.getWhois method.
    server.tool(
      "shodan_whois",
      { query: z.string().describe("IP or domain to lookup WHOIS in Shodan Labs") },
      async ({ query }) => {
        const result = await shodanClient.getWhois(query);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
        };
      }
    );
  • Implementation of the getWhois method in ShodanApiClient, which interacts with the Shodan Labs WHOIS endpoint.
    async getWhois(ip: string): Promise<any> {
      const apiKey = configManager.get("SHODAN_API_KEY");
      if (!apiKey) {
        throw new McpError(
          ErrorCode.InvalidRequest,
          "SHODAN_API_KEY is not configured"
        );
      }
    
      try {
        // Shodan has a labs/whois endpoint but it's for domains usually.
        // For IP whois, shodan/host/{ip} already contains some info.
        // Let's use the dedicated labs/whois if it supports IP, or just stick to host.
        const data = await this.fetch<any>(`labs/whois`, {
          method: "GET",
        }, {
          key: apiKey,
          query: ip
        });
    
        return data;
      } catch (error) {
        if (error instanceof McpError) throw error;
        throw new McpError(
          ErrorCode.InternalError,
          `Shodan WHOIS error: ${(error as Error).message}`
        );
      }
    }
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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/CloudWaddie/osint-mcp'

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