UNHCR Population Data MCP Server
# UNHCR Refugee Statistics
## Description
This MCP (Model Context Protocol) server provides access to UNHCR data through a standardized interface. It allows AI agents to query data related to forcibly displaced persons, including population statistics, Refugee Status Determination (RSD) applications, and RSD decisions. The data can be filtered by country of origin, country of asylum, and year(s).
## Features
- **Population Data**: Get statistics on refugees, asylum seekers, and stateless persons.
- **Demographics**: Breakdown by age and sex.
- **RSD Applications**: Query asylum applications data.
- **RSD Decisions**: Query refugee status determination decisions.
- **Solutions**: Data on resettlement, naturalization, and returns.
## Usage
This server is designed to be used with MCP clients (like Claude Desktop, Smithery, etc.).
### Tools
- `get_population_data`
- `get_demographics_data`
- `get_rsd_applications`
- `get_rsd_decisions`
- `get_solutions`
## License
MIT
TDQS
Scored across 5 tools
The tools are mostly distinct, covering demographics, population, RSD applications, RSD decisions, and solutions. However, get_demographics_data and get_population_data could be confused as both handle forcibly displaced populations, though demographics focuses on age/sex breakdowns while population covers types like refugees. Descriptions help clarify, but overlap exists.
All tools follow a consistent verb_noun pattern with 'get_' prefix and descriptive nouns (e.g., get_demographics_data, get_population_data). This predictable naming makes it easy for agents to understand and navigate the toolset without confusion.
With 5 tools, the server is well-scoped for UNHCR population data, covering key aspects like demographics, population figures, RSD processes, and solutions. Each tool serves a clear purpose, avoiding bloat while providing comprehensive coverage for the domain.
The toolset covers core UNHCR data areas well, including demographics, population types, RSD applications/decisions, and solutions. A minor gap is the lack of tools for updating or managing data (e.g., CRUD operations), but this is reasonable for a read-only data query server focused on retrieval from an external API.