In-depth architectural comparison of the Radio and Unhcr MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Radio
Developer Tools · Local stdio
Quality: 47/100 (Fair) | Auth: No auth required
Unhcr
Developer Tools · Local stdio
Quality: 43/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Radio if you need specialized Developer Tools tools running via a local process. Choose Unhcr if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
R
Choose Radio when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Search radio stations by name. Returns station name, URL, country, genres, and popularity vote count. Use when looking for a specific station or browsing by keyword.
get_top_stations
Get trending radio stations ranked by popularity, optionally filtered by country (e.g., 'US', 'GB', 'DE'). Returns station URLs, genres, and vote counts.
list_countries
Browse available countries with radio stations. Returns country names and station counts to help target your search geographically.
list_tags
Discover radio genres and tags ranked by station count. Use to explore what categories are available before searching.
Unhcr Tools (4)
population
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Radio is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Unhcr belongs to Developer Tools using local stdio subprocess. Select Radio when you need capabilities focused on developer tools and Unhcr when you require tools for developer tools.
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 (on…
asylum_applications
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).
asylum_decisions
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).
list_countries
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 thro…