Ucdp
NPM · @PIPEWORX/MCP-UCDP · 2 COMPONENTS
Armed-conflict deaths, active wars and violence events from the Uppsala Conflict Data Program…
Available components
Last scanned (19 hours ago)
Scores higher than 61% of npm servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-ucdp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1249 tokens (~249/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed npm/@pipeworx/mcp-ucdp@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-ucdp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-ucdp/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560614206 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:10cd6857f3c8b367bbecd47706fed54c199e5cacd68d9813b2aa4c55683dc93b100a3510657115b8994f214d16402712749cfe7c61867e4ceb431fdef |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ucdp_conflicts ~246
Armed conflicts recorded by UCDP/PRIO for a country or year: the government and rebel/state parties, whether the fight is over territory or government, intrastate / interstate / internationalized type, intensity (minor vs war), episode start and end dates, and battle-related deaths (best/low/high) for that year. Answers "which armed conflicts were active in Ethiopia in 2023", "how many battle deaths did the Russia-Ukraine war cause in 2024", "list wars with over 1,000 deaths". Example: ucdp_conflicts({ country: "Ethiopia", year: 2023 })
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Country name or Gleditsch-Ward code of the conflict location. Omit for all countries. |
| intensity | string | – | Filter by intensity: minor (25-999 battle deaths) or war (1,000+) |
| limit | integer | – | Max conflicts to return (default 50, max 500), sorted by battle deaths |
| year | integer | – | Conflict-year, 1946 onward (battle deaths from 1989). Omit for the latest year. |
No output schema declared.
No examples provided.
ucdp_countries ~158
The countries the Uppsala Conflict Data Program codes, with their Gleditsch-Ward country codes, region, years covered and the latest year's total deaths from organized violence. Use it to resolve a country name or code before calling other ucdp tools, or to rank countries by conflict deaths. Example: ucdp_countries({ query: "congo" })
| Name | Type | Req | Description |
|---|---|---|---|
| min_deaths | integer | – | Only countries with at least this many organized-violence deaths (best estimate) in the latest year |
| query | string | – | Substring of the country name; omit for the full list |
| region | string | – | Filter by UCDP region: Africa, Americas, Asia, Europe, Middle East |
No output schema declared.
No examples provided.
ucdp_events ~333
Georeferenced armed-conflict events from the UCDP Georeferenced Event Dataset (GED) for a country and date range, 1989 to the latest yearly release: each event with date, location and coordinates, sides, violence type and best/low/high deaths. Answers "list the deadliest events in Sudan in 2024" or "battles in Donetsk in March 2023". Requires a UCDP API access token passed as _apiKey. Example: ucdp_events({ country: "Sudan", start: "2024-01-01", end: "2024-12-31", limit: 100, _apiKey: "your-token" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | UCDP API access token (x-ucdp-access-token). Request one free from the API maintainer at https://ucdp.uu.se/apidocs |
| country | string | yes | Country name or Gleditsch-Ward code |
| end | string | – | Latest event end date, YYYY-MM-DD |
| limit | integer | – | Events per page (default 100, max 1000) |
| page | integer | – | Page number, 1-based |
| start | string | – | Earliest event end date, YYYY-MM-DD |
| type_of_violence | string | – | state-based | non-state | one-sided (or 1 | 2 | 3) |
| version | string | – | GED release, default "26.1"; candidate releases like "26.0.7" work too |
No output schema declared.
No examples provided.
ucdp_fatalities_summary ~241
Deaths from armed conflict and organized violence in a country for a year or range of years, from the Uppsala Conflict Data Program (UCDP) country-year dataset: best, low and high fatality estimates split into state-based conflict, non-state conflict and one-sided violence against civilians, plus combatant vs civilian victims and the named warring dyads. Answers "how many people were killed in the Sudan war in 2024", conflict death tolls, casualty trends since 1989. Country names resolve to Gleditsch-Ward codes. Example: ucdp_fatalities_summary({ country: "Sudan", year: 2024 })
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Country name ("Sudan", "DR Congo", "Myanmar") or Gleditsch-Ward code ("625") |
| from | integer | – | Start year of a range (with `to`) — returns one row per year |
| to | integer | – | End year of a range (with `from`) |
| year | integer | – | Calendar year, 1989 to the latest released year. Omit for the latest year. |
No output schema declared.
No examples provided.
ucdp_recent_events ~217
Individual violence events from the newest monthly UCDP GED Candidate release — the preliminary current-year event list, published monthly: date, place with coordinates, warring sides, type (state-based, non-state, one-sided), fatality best/low/high and the source headline. Answers "what attacks happened in Nigeria last month", "recent conflict events in Myanmar with fatalities". For yearly totals use ucdp_fatalities_summary; for events in earlier years use ucdp_events. Example: ucdp_recent_events({ country: "Nigeria", limit: 20 })
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Country name or Gleditsch-Ward code; omit for all countries |
| limit | integer | – | Max events (default 50, max 500), newest first |
| min_deaths | integer | – | Only events with at least this many deaths (best estimate) |
| type_of_violence | string | – | state-based | non-state | one-sided (or 1 | 2 | 3) |
No output schema declared.
No examples provided.
How do I install the Ucdp MCP server?
Ucdp runs locally as an npm package, launched with npx -y @pipeworx/mcp-ucdp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-ucdp
claude mcp add pipeworx-io-ucdp -- npx -y @pipeworx/mcp-ucdp
What is the Ucdp MCP server?
Ucdp is an MCP server listed in the public MCP registry as io.github.pipeworx-io/ucdp. Armed-conflict deaths, active wars and violence events from the Uppsala Conflict Data Program… This page covers its npm package (@pipeworx/mcp-ucdp).
Is the Ucdp MCP server safe to use?
Ucdp scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Ucdp MCP server expose?
Ucdp exposes 5 tools: ucdp_fatalities_summary, ucdp_conflicts, ucdp_countries, ucdp_recent_events, ucdp_events. Their descriptions and schemas cost roughly 1,195 tokens of context every time the server is loaded.
Is the Ucdp MCP server still maintained?
Ucdp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Ucdp MCP server under?
Ucdp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.