Skip to main content
Glama
Sign In
MCP AbuseIPDB Server

MCP AbuseIPDB Server

by alephnan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

check_block

Check the reputation of a CIDR network block using AbuseIPDB threat intelligence to identify potentially malicious IP ranges for security analysis.

Instructions

Check the reputation of a CIDR block using AbuseIPDB

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "network": "<network>"
    },
    "name": "check_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
networkYesCIDR network to check (e.g., '192.168.1.0/24')
max_age_daysNoMaximum age of reports to consider in days

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions the service (AbuseIPDB) but does not disclose behavioral traits such as rate limits, authentication requirements, error handling, or what the output looks like (e.g., reputation score, report details). This is a significant gap for a tool with external dependencies.

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 a single, efficient sentence that directly states the tool's purpose without any wasted words. It is appropriately sized and front-loaded with the core action.

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

Completeness2/5

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

Given the complexity of reputation checking with an external service, no annotations, and no output schema, the description is incomplete. It lacks details on behavioral aspects (e.g., rate limits, auth), output format, and error handling, which are crucial for effective tool use.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema fully documents both parameters ('network' as CIDR and 'max_age_days' with constraints). The description adds no additional parameter semantics beyond what the schema provides, such as examples of valid CIDR formats or implications of the age filter.

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 specific action ('check the reputation') and resource ('CIDR block') using a named service ('AbuseIPDB'). It distinguishes this tool from sibling tools like 'check_ip' (likely for individual IPs) and 'bulk_check' (likely for multiple checks).

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?

The description implies usage for reputation checking of CIDR blocks, but does not explicitly state when to use this tool versus alternatives like 'check_ip' for single IPs or 'bulk_check' for multiple blocks. No exclusions or prerequisites are mentioned.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools