mcpField
U
Ucdp

Ucdp

Remote
pipeworx.ioScience & Education0Updated 5w ago
RepositoryVisit website

About Ucdp

Ucdp is an MCP server for conflict researchers and data analysts, exposing UCDP fatality, active-conflict, and georeferenced violence-event data dating from 1989. Its first four tools require no key; historical GED API queries require a UCDP token.

Key features

  1. 01Summarize annual organized-violence deaths by country
  2. 02Query active armed conflicts by year
  3. 03Browse countries, coverage years, and fatalities
  4. 04Retrieve the latest monthly candidate events
  5. 05Query GED events across date ranges

Use cases

  1. 01Analyze a country's conflict deaths in a given year
  2. 02Review conflict parties and intensity
  3. 03Screen recent violence events
  4. 04Study georeferenced events from a historical period

MCP support

The MCP server exposes tools for querying fatality statistics, conflicts, countries, and events. The historical GED API tool requires the caller to provide a UCDP API token.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://gateway.pipeworx.io/ucdp/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

@pipeworx/ucdp

Uppsala Conflict Data Program (UCDP) — armed-conflict fatalities, active conflicts and georeferenced violence events for every country since 1989, from the published UCDP yearly datasets, the monthly GED Candidate release, and (with a token) the UCDP API.

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

Tools

  • ucdp_fatalities_summary(country, year? | from?/to?) — deaths from organized violence for a country-year: best/low/high, split state-based / non-state / one-sided, combatants vs civilians, named dyads. Answers "how many people were killed in the Sudan war in 2024".
  • ucdp_conflicts(country?, year?, intensity?) — UCDP/PRIO armed conflicts active in a year with parties, incompatibility, type, intensity, episode dates and battle-related deaths.
  • ucdp_countries(query?, region?, min_deaths?) — the 199 coded countries with Gleditsch-Ward codes, coverage years and latest-year deaths (sorted by deaths).
  • ucdp_recent_events(country?, type_of_violence?, min_deaths?, limit?) — individual events from the newest monthly GED Candidate file (preliminary, current year).
  • ucdp_events(country, start?, end?, type_of_violence?, limit?, page?, version?, _apiKey) — GED events for any date range 1989 onward via the UCDP API. Requires an API key.

Auth

Keyless for the first four tools. ucdp_events is BYO only: pass a UCDP API access token as _apiKey (sent as the x-ucdp-access-token header). This is a standing decision, not a gap: Bruce ruled BYOK on 2026-09-03 (fleet #1226), so Pipeworx will not request a platform token, and the refusal without one says "requires an API key" and points at https://ucdp.uu.se/apidocs.

Activation caveat

UCDP tokens are not self-service. Since 2025 every API call needs a token, and tokens are issued by emailing the API maintainer (address and template at https://ucdp.uu.se/apidocs) with a description of the intended use; requests are answered in 3–5 working days. Without a token every ucdpapi.pcr.uu.se call returns HTTP 401 "API token required" — that is the vendor gate, not an outage.

If that decision is ever revisited and a platform token exists: set PLATFORM_UCDP_TOKEN on the gateway AND add platformKeyEnv: 'PLATFORM_UCDP_TOKEN' to the pack's MCP_PACKS entry in the same deploy. Declaring platformKeyEnv while the secret is unset key-blocks every tool in the pack from routing, including the keyless ones.

Data sources

Traps:

  • The full GED zip (ged261-csv.zip) is 39 MB and inflates far beyond what a Worker can hold — event history before the current month needs the API.
  • UCDP names states by continuity: "Russia (Soviet Union)", "Yemen (North Yemen)", "DR Congo (Zaire)", "Myanmar (Burma)". The resolver accepts the common names and aliases (DRC, USA, UK, Côte d'Ivoire, Eswatini, Czechia, Türkiye, Timor-Leste…) and Gleditsch-Ward codes; Palestine/Gaza/West Bank map to Israel because UCDP codes sovereign states only.
  • sb_dyad_names / ns_dyad_names / os_dyad_names are ;-separated inside one CSV field.
  • All UCDP counts use a 25-deaths-per-dyad-year inclusion threshold; a country with real but diffuse violence can show zero.

Quick Start

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

{
  "mcpServers": {
    "ucdp": {
      "url": "https://gateway.pipeworx.io/ucdp/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/ucdp/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

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

Both URLs reach the same gateway and the same 1684+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/ucdp_fatalities_summary \
  -H 'Content-Type: application/json' \
  -d '{"country":"Sudan","year":2024}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/ucdp_fatalities_summary. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

{
  "mcpServers": {
    "ucdp": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-ucdp"]
    }
  }
}

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-ucdp

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

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

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

More

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.