mcp-abuseipdb

Purpose: Enabling developers to integrate AbuseIPDB threat intelligence into their systems via MCP server.

Inferred · not functionally tested

Audience: security developers

Inferred · not functionally tested

Functions: data_extraction, workflow_automation

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, api_only, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: github.com. These links do not verify the individual claims.

mcp-abuseipdb sits in PulseGate's Threat intelligence, SIEM & detection category. Inferred · not functionally tested: Enabling developers to integrate AbuseIPDB threat intelligence into their systems via MCP server. Inferred · not functionally tested: It is built as an open-source project for security developers. Basis unknown · not verified: The project is open source (MIT). Basis unknown · not verified: mcp-abuseipdb is available on the command line and API, and it can be self-hosted.

It is developed by n3r0-b1n4ry, and it first shipped in 2025. The project is developed in the open on GitHub with 7 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include abuseIPDB integration, threat intelligence, and MCP server. Inferred · not functionally tested: Catalogued interfaces include a public API and an MCP server.

Summary written by a language model from the project’s public pages.