Skip to main content
Glama
aplaceforallmystuff

MCP Threat Intel Server

threatintel_status

Check the status of configured threat intelligence sources, including GreyNoise and Feodo, to verify availability for unified security research.

Instructions

Check which threat intelligence sources are configured. Currently available: greynoise, feodo

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Tool registration/definition for 'threatintel_status' in the TOOLS array. Has no required input parameters.
    {
      name: "threatintel_status",
      description: `Check which threat intelligence sources are configured. Currently available: ${configuredServices.join(", ") || "none (abuse.ch feeds work without auth)"}`,
      inputSchema: {
        type: "object" as const,
        properties: {},
        required: [],
      },
    },
  • Handler implementation for 'threatintel_status' - returns a JSON object listing configured services and all available tool names.
    case "threatintel_status": {
      return {
        content: [{
          type: "text",
          text: JSON.stringify({
            configured_services: {
              otx: services.otx ? "configured" : "not configured (set OTX_API_KEY)",
              abuseipdb: services.abuseipdb ? "configured" : "not configured (set ABUSEIPDB_API_KEY)",
              greynoise: config.greynoise.apiKey
                ? "configured with API key"
                : "available (keyless community endpoint; set GREYNOISE_API_KEY for higher rate limits)",
              abusech: services.abusech ? "configured" : "not configured (set ABUSECH_AUTH_KEY)",
              feodo: "available (public JSON feeds)",
            },
            available_tools: TOOLS.map(t => t.name),
          }, null, 2),
        }],
      };
    }
  • src/index.ts:377-379 (registration)
    Registration of the TOOLS array (including threatintel_status) via the ListToolsRequestSchema handler.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools: TOOLS };
    });
Behavior4/5

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

No annotations; description indicates a read operation without side effects. It explicitly lists current sources, but could mention it's read-only and safe.

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 that concisely states purpose and includes example output. No unnecessary words.

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?

Adequate for a simple status tool. Hints at return value (list of sources) but does not specify format or data type. Could be improved with explicit output description.

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?

No parameters; schema coverage is 100%. The description does not need to add param meaning. Baseline score for 0 parameters is 4.

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 checks which threat intelligence sources are configured, with specific examples (greynoise, feodo). This distinguishes it from sibling lookup tools.

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?

Implied usage to verify configured sources before using lookup tools, but no explicit when-to-use or when-not-to-use guidance, nor alternatives named.

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