Skip to main content
Glama
badchars

osint-mcp-server

by badchars

osint_list_sources

List all configured OSINT data sources, their availability, API key requirements, and tool counts to verify source configuration.

Instructions

List all OSINT data sources, their availability, API key requirements, and tool counts. Use this to check which sources are configured.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool definition for 'osint_list_sources'. The execute function calls checkSources(ctx) and returns JSON. No input schema required.
    const osintListSourcesTool: ToolDef = {
      name: "osint_list_sources",
      description: "List all OSINT data sources, their availability, API key requirements, and tool counts. Use this to check which sources are configured.",
      schema: {},
      execute: async (_args, ctx) => json(await checkSources(ctx)),
    };
  • The checkSources function that produces the list of OSINT sources with their names, URLs, auth requirements, configuration status (based on env vars), and tool counts.
    import type { ToolContext } from "../types/index.js";
    
    interface SourceInfo {
      name: string;
      url: string;
      authRequired: boolean;
      configured: boolean;
      envVar?: string;
      toolCount: number;
    }
    
    export async function checkSources(ctx: ToolContext): Promise<SourceInfo[]> {
      return [
        { name: "DNS", url: "native (dns/promises)", authRequired: false, configured: true, toolCount: 6 },
        { name: "WHOIS (RDAP)", url: "rdap.org", authRequired: false, configured: true, toolCount: 2 },
        { name: "crt.sh", url: "crt.sh", authRequired: false, configured: true, toolCount: 1 },
        { name: "GeoIP", url: "ip-api.com", authRequired: false, configured: true, toolCount: 2 },
        { name: "BGP/ASN", url: "bgpview.io", authRequired: false, configured: true, toolCount: 3 },
        { name: "HackerTarget", url: "hackertarget.com", authRequired: false, configured: true, toolCount: 3 },
        { name: "Wayback Machine", url: "web.archive.org", authRequired: false, configured: true, toolCount: 2 },
        { name: "Microsoft 365", url: "login.microsoftonline.com", authRequired: false, configured: true, toolCount: 2 },
        {
          name: "Shodan",
          url: "api.shodan.io",
          authRequired: true,
          configured: !!ctx.config.shodanApiKey,
          envVar: "SHODAN_API_KEY",
          toolCount: 4,
        },
        {
          name: "VirusTotal",
          url: "virustotal.com/api/v3",
          authRequired: true,
          configured: !!ctx.config.vtApiKey,
          envVar: "VT_API_KEY",
          toolCount: 4,
        },
        {
          name: "SecurityTrails",
          url: "api.securitytrails.com",
          authRequired: true,
          configured: !!ctx.config.stApiKey,
          envVar: "ST_API_KEY",
          toolCount: 3,
        },
        {
          name: "Censys",
          url: "search.censys.io",
          authRequired: true,
          configured: !!(ctx.config.censysApiId && ctx.config.censysApiSecret),
          envVar: "CENSYS_API_ID + CENSYS_API_SECRET",
          toolCount: 3,
        },
      ];
    }
  • The tool is registered in the allTools array at index position with the rest of the Meta tools.
      osintListSourcesTool,
      osintDomainReconTool,
    ];
  • src/index.ts:35-35 (registration)
    Tool listed under the 'Meta' category in the TOOL_CATEGORIES array used for --list display.
    { label: "Meta", env: null, tools: ["osint_list_sources", "osint_domain_recon"] },
Behavior4/5

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

With no annotations, the description carries the full burden. It states the tool lists data sources, implying a read-only operation. The description adequately describes the behavior without contradictory or missing information.

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?

The description is two sentences, front-loaded with the core action, and includes a clear use case. Every sentence adds value, with no redundancy or extraneous information.

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

Completeness5/5

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

Given the tool has no parameters, no output schema, and is a simple list, the description fully explains what it does and its purpose. It specifies the fields listed (availability, API key requirements, tool counts) and the intended use (checking configuration). This is complete for the tool's complexity.

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?

The input schema has no parameters, so the description does not need to add parameter semantics. Schema coverage is 100%, and the description mentions the tool lists 'all' sources, aligning with the no-parameter interface.

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 tool lists OSINT data sources with availability, API key requirements, and tool counts. It uses specific verb 'list' and resource 'OSINT data sources', distinguishing it from sibling query tools that perform lookups on specific sources.

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

Usage Guidelines4/5

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

The description provides usage guidance: 'Use this to check which sources are configured.' This implies it is for configuration checks. While it does not explicitly exclude alternatives, the context of sibling tools makes the use case clear.

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

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