Back to Browse

Acled MCP Server

Developer ToolsLow Risk9.8MCP RegistryRemote
Free

Server data from the Official MCP Registry

ACLED MCP — Armed Conflict Location & Event Data Project

About

ACLED MCP — Armed Conflict Location & Event Data Project

Remote endpoints: streamable-http: https://gateway.pipeworx.io/acled/mcp

Security Report

9.8
Low Risk9.8Low Risk

Valid MCP server (1 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. Trust signals: trusted author (271/273 approved). 1 finding(s) downgraded by scanner intelligence.

10 tools verified · Open access · 2 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "io-github-pipeworx-io-acled": {
      "url": "https://gateway.pipeworx.io/acled/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

@pipeworx/acled

ACLED MCP — armed-conflict and protest event data. OAuth (myACLED email + password).

Part of Pipeworx — an MCP gateway connecting AI agents to 1394+ live data sources.

Tools

  • search_events(...) — filter by country, region, event type, actor, date, fatalities.
  • event_counts_by_country(...) — aggregated event/fatality counts.

Auth

BYO only.

ACLED migrated to OAuth in 2025. You provide your myACLED email + password; the pack exchanges them for a 24h access token (cached in-memory).

Pass ?_email=...&_password=... on the gateway URL.

Activation caveat

Registration alone is not enough — ACLED gates API access per account. After registering at https://acleddata.com/register/, email access@acleddata.com to request API access. Until they enable it, data requests return HTTP 403 even with a valid OAuth token.

Data sources

  • Token: https://acleddata.com/oauth/token
  • Data: https://acleddata.com/api/acled/read

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "acled": {
      "url": "https://gateway.pipeworx.io/acled/mcp"
    }
  }
}

Or connect to the full Pipeworx gateway for access to all 1394+ data sources:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English:

ask_pipeworx({ question: "your question about Acled data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Reviews

No reviews yet

Be the first to review this server!