abuseipdb_mcp

Created By
gogelaa year ago
MCP server for AbuseIPDB API
Overview

what is abuseipdb_mcp?

abuseipdb_mcp is a server that acts as a simple wrapper for the AbuseIPDB API, allowing users to easily interact with the service to check IP addresses for abuse reports.

how to use abuseipdb_mcp?

To use abuseipdb_mcp, you need to have your own API token from abuseipdb.com. After obtaining the token, you can run the server and use it with the provided example.py script for integration with smolagents.

key features of abuseipdb_mcp?

  • Simple wrapper for the AbuseIPDB API
  • Easy integration with Python applications
  • Requires minimal setup with an API token

use cases of abuseipdb_mcp?

  1. Checking IP addresses for potential abuse in web applications.
  2. Integrating IP abuse checks into security monitoring tools.
  3. Automating the process of reporting abusive IP addresses.

FAQ from abuseipdb_mcp?

  • Do I need an API token to use abuseipdb_mcp?

Yes, you need to obtain your own API token from abuseipdb.com to use this service.

  • Is abuseipdb_mcp free to use?

The usage of the API may depend on the AbuseIPDB service's pricing and limits, so check their website for details.

  • What programming language is abuseipdb_mcp written in?

abuseipdb_mcp is written in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
gogela
Star
0
Language
Python
License
GPL-3.0 license

Recommend Servers

View All
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

13 hours ago