Skip to main content
Glama
aplaceforallmystuff

MCP Threat Intel Server

feodo_tracker

Retrieve active botnet command-and-control servers from Feodo Tracker, covering Emotet, Dridex, QakBot, and others. Get current C2 IPs for threat detection and blocking.

Instructions

Get active botnet C2 servers from Feodo Tracker (Emotet, Dridex, QakBot, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the feodo_tracker tool. Fetches active botnet C2 server data from the public Feodo Tracker JSON feed (ipblocklist_recommended.json) and returns it as formatted JSON.
    case "feodo_tracker": {
      // Feodo provides JSON feed of active C2s
      const result = await apiRequest<unknown>(
        "https://feodotracker.abuse.ch/downloads/ipblocklist_recommended.json"
      );
    
      return {
        content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
      };
    }
  • src/index.ts:352-361 (registration)
    Registration of the feodo_tracker tool with its name, description, and input schema (empty object, no parameters required).
    // Feodo Tracker (public JSON feed - no auth required)
    TOOLS.push({
      name: "feodo_tracker",
      description: "Get active botnet C2 servers from Feodo Tracker (Emotet, Dridex, QakBot, etc.)",
      inputSchema: {
        type: "object" as const,
        properties: {},
        required: [],
      },
    });
  • Input schema for feodo_tracker — accepts no parameters (empty object, no required fields).
      inputSchema: {
        type: "object" as const,
        properties: {},
        required: [],
      },
    });
  • Service flag for Feodo Tracker — always enabled (true) since the feed is public and requires no authentication.
    feodo: true, // Feodo Tracker public JSON feeds still work
  • Base URL configuration for the Feodo Tracker service, pointing to the abuse.ch downloads directory.
    feodo: "https://feodotracker.abuse.ch/downloads",
Behavior2/5

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

No annotations provided, so description carries full burden. It only states what the tool retrieves, but does not disclose behavioral traits like whether it's read-only, rate limits, data freshness, or output specifics.

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?

Single sentence, front-loaded with action and key subject, no extraneous words. Highly efficient.

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

Completeness3/5

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

For a zero-parameter tool, the description is adequate but minimal. It lacks output format or data reliability context, which could leave an agent slightly uncertain about what to expect.

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?

Input schema has 0 parameters, so no param info needed. Description covers the tool's purpose adequately, meeting the baseline for zero-parameter tools.

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?

Description clearly states verb 'Get', resource 'active botnet C2 servers', and source 'Feodo Tracker', with examples of botnet families. It distinguishes from sibling tools like 'greynoise_ip' or 'threatintel_lookup_*' by specifying a specific threat feed.

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

Usage Guidelines3/5

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

Description implies usage for retrieving Feodo Tracker data but does not explicitly state when to use this tool versus alternatives, nor provide conditions or exclusions.

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