MCP AbuseIPDB Server
Related Servers
Alternatives to MCP AbuseIPDB Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables querying AbuseIPDB threat intelligence via natural language, including IP reputation checks, subnet scans, and abuse report retrieval.49 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to check IP reputation and abuse reports via AbuseIPDB, including abuse confidence scores, report details, and bulk IP triage.9 npm1MIT
- AlicenseNot gradedqualityDmaintenanceIntegrates with the AbuseIPDB API to check IP addresses for abuse reports and report abusive IP addresses.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to check IPv4/IPv6 addresses for abuse reports and submit malicious IP reports through the AbuseIPDB API.MIT
- AlicenseNot gradedqualityBmaintenanceProvides access to AbuseIPDB v2 API for checking IP reputation, reporting abuse, and querying blacklists via the Pipeworx MCP gateway.306 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides comprehensive IP and domain security intelligence, enabling analysis of IP addresses and domains for threat and reputation information.1MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: bulk_check handles multiple IPs, check_block covers CIDR blocks, check_ip is for single IPs, enrich_log_line processes log lines, and get_blacklist retrieves a blacklist. There is no overlap or ambiguity between these functions.
All tools follow a consistent verb_noun pattern (e.g., check_ip, get_blacklist) with clear, descriptive names. There are no deviations in style or convention across the set.
With 5 tools, the server is well-scoped for AbuseIPDB functionality, covering key operations like single/bulk IP checks, block analysis, log enrichment, and blacklist retrieval. Each tool earns its place without feeling excessive or insufficient.
The tool set provides comprehensive coverage for the AbuseIPDB domain, including reputation checks at different scales (single, bulk, block), log enrichment, and blacklist access. There are no obvious gaps in the core workflows for this purpose.