Abuseipdb

Check Ip

check_ip

Read-onlyIdempotent

Check an IP address against the AbuseIPDB database. Returns abuse confidence score (0-100), ISP, usage type, country, number of reports, and last reported date. Example: check_ip("8.8.8.8").

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ip": "118.25.6.39",
      "_apiKey": "your-abuseipdb-api-key"
    },
    "name": "check_ip"
  }
}

Input Schema

Name	Required	Description	Default
`ip`	Yes	IPv4 or IPv6 address to check (e.g., "118.25.6.39")
`_apiKey`	Yes	AbuseIPDB API key

Output Schema

Name	Required	Description
`ip`	Yes	The IP address checked
`isp`	Yes	Internet Service Provider name
`domain`	Yes	Associated domain name
`is_public`	Yes	Whether the IP is public
`usage_type`	Yes	Type of IP usage (e.g., Commercial, Residential)
`country_code`	Yes	Country code of the IP
`total_reports`	Yes	Total number of abuse reports for this IP
`last_reported_at`	Yes	ISO timestamp of last abuse report, or null
`abuse_confidence_score`	Yes	Abuse confidence score from 0-100

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 26, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive. The description adds the AbuseIPDB external service context and the 0-100 score scale, which is helpful but not extensive. No contradiction with annotations.

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?

Two concise sentences plus an illustrative example. The first sentence front-loads the purpose, and every part earns its place with no redundant text.

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?

The tool is simple, has output schema, and strong annotations. The description covers purpose, example, and key return fields. Could mention API key requirement explicitly, but the example covers it.

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 covers 100% of parameters with descriptions. The description's example adds a realistic invocation pattern with placeholder API key and example IP, but does not add meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool checks an IP against AbuseIPDB and lists the returned data. It does not explicitly differentiate from sibling report_ip, but the verb 'check' implies a read-only lookup distinct from reporting.

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 a concrete example of how to call the tool with an API key, which demonstrates usage. It doesn't explicitly state when to use this over alternatives like report_ip, but the read-only context is clear.

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

All Abuseipdb tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.