Unhcr
NPM · @PIPEWORX/MCP-UNHCR · 2 COMPONENTS
UNHCR Refugee Data Finder MCP (keyless).
Available components
Last scanned (13 hours ago)
Scores higher than 62% 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-unhcr). 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 Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 795 tokens (~198/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-unhcr@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-unhcr |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-unhcr/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560802354 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a070698e99afd642298dfb73e6d3dba83af2926173e304ef2a34d3274f42a50b9732aa0ba81c2b58bd93b03b78060356afbff926f18c27924a6823b20 |
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 →
asylum_applications ~164
Asylum applications lodged, by year, country of origin (coo) and country of asylum (coa). Rows carry procedure_type, app_type, dec_level and the `applied` count; response.total.applied is the aggregate. coo/coa take UNHCR 3-letter codes (see list_countries).
| Name | Type | Req | Description |
|---|---|---|---|
| coa | string | – | Country of ASYLUM — UNHCR 3-letter code. |
| coo | string | – | Country of ORIGIN — UNHCR 3-letter code. |
| limit | integer | – | Rows per page (default 25). |
| page | integer | – | 1-based page. |
| yearFrom | integer | – | Start year, inclusive. |
| yearTo | integer | – | End year, inclusive. |
No output schema declared.
No examples provided.
asylum_decisions ~167
Decisions on asylum claims, by year, country of origin (coo) and country of asylum (coa). Each row breaks out dec_recognized, dec_other, dec_rejected, dec_closed and dec_total; response.total aggregates the same fields. coo/coa take UNHCR 3-letter codes (see list_countries).
| Name | Type | Req | Description |
|---|---|---|---|
| coa | string | – | Country of ASYLUM — UNHCR 3-letter code. |
| coo | string | – | Country of ORIGIN — UNHCR 3-letter code. |
| limit | integer | – | Rows per page (default 25). |
| page | integer | – | 1-based page. |
| yearFrom | integer | – | Start year, inclusive. |
| yearTo | integer | – | End year, inclusive. |
No output schema declared.
No examples provided.
list_countries ~134
Reference list of countries/territories UNHCR tracks. Use this to map a country name to the `code` you pass as coo/coa in the other tools. Each item has: code (UNHCR 3-letter, USE THIS for filtering), iso (true ISO3), iso2, name, region, majorArea. Paginated — large list, raise `limit` or page through (response.maxPages).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Rows per page (default 25; raise to fetch more at once). |
| page | integer | – | 1-based page; see response.maxPages. |
No output schema declared.
No examples provided.
population ~277
Forcibly displaced & stateless persons by year and country: refugees, asylum_seekers, idps (internally displaced), returned_refugees, returned_idps, stateless, others. Filter by coo (country of origin) and/or coa (country of asylum). coo_all/coa_all=true breaks the totals DOWN by that dimension (one row per origin or asylum country). NOTE: coo/coa take UNHCR's 3-letter code (e.g. Germany='GFR', not ISO3 'DEU') — resolve with list_countries first.
| Name | Type | Req | Description |
|---|---|---|---|
| coa | string | – | Country of ASYLUM — UNHCR 3-letter code (see list_countries.code). |
| coa_all | boolean | – | true = break results down per country of asylum. |
| coo | string | – | Country of ORIGIN — UNHCR 3-letter code (see list_countries.code). |
| coo_all | boolean | – | true = break results down per country of origin. |
| limit | integer | – | Rows per page (default 25). |
| page | integer | – | 1-based page; response.maxPages tells you the total. |
| yearFrom | integer | – | Start year, inclusive (data spans 1951+). |
| yearTo | integer | – | End year, inclusive. |
No output schema declared.
No examples provided.
How do I install the Unhcr MCP server?
Unhcr runs locally as an npm package, launched with npx -y @pipeworx/mcp-unhcr. 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-unhcr
claude mcp add pipeworx-io-unhcr -- npx -y @pipeworx/mcp-unhcr
What is the Unhcr MCP server?
Unhcr is an MCP server listed in the public MCP registry as io.github.pipeworx-io/unhcr. UNHCR Refugee Data Finder MCP (keyless). This page covers its npm package (@pipeworx/mcp-unhcr).
Is the Unhcr MCP server safe to use?
Unhcr scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Unhcr MCP server expose?
Unhcr exposes 4 tools: population, asylum_applications, asylum_decisions, list_countries. Their descriptions and schemas cost roughly 742 tokens of context every time the server is loaded.
Is the Unhcr MCP server still maintained?
Unhcr is still listed as active in the MCP registry. We last reached this channel on 5 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 Unhcr MCP server under?
Unhcr declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Unhcr MCP server?
VerifyMCP ran 15 checks on Unhcr, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Unhcr: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.