Skip to main content
Glama
CloudWaddie

OSINT MCP Server

username_search

Search for a username across multiple online platforms to identify associated accounts and digital footprints for security research and OSINT investigations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYesUsername to search for across platforms

Implementation Reference

  • The search() method in UsernameSearchClient executes parallel checks against a list of social media platforms to see if a username exists.
    async search(username: string): Promise<any[]> {
      const results: any[] = [];
      const timeout = 5000;
    
      // Run searches in parallel with a concurrency limit
      const checkPlatform = async (platform: any) => {
        const url = platform.url.replace("{}", username);
        try {
          const controller = new AbortController();
          const id = setTimeout(() => controller.abort(), timeout);
          
          const response = await fetch(url, { 
            method: "GET",
            signal: controller.signal,
            headers: {
              "User-Agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36"
            }
          });
          
          clearTimeout(id);
          
          if (response.status === 200) {
            results.push({
              platform: platform.name,
              url: url,
              status: "found"
            });
          }
        } catch (error) {
          // Ignore errors, just means it's likely not found or blocked
        }
      };
    
      // Parallel execution with small batches to avoid being blocked
      const batchSize = 5;
      for (let i = 0; i < PLATFORMS.length; i += batchSize) {
        const batch = PLATFORMS.slice(i, i + batchSize);
        await Promise.all(batch.map(p => checkPlatform(p)));
      }
    
      return results;
    }
  • src/index.ts:401-410 (registration)
    The "username_search" tool is registered here, delegating the execution to the UsernameSearchClient.search method.
    server.tool(
      "username_search",
      { username: z.string().describe("Username to search for across platforms") },
      async ({ username }) => {
        const result = await userClient.search(username);
        return {
          content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
        };
      }
    );
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