UUnhcr Data PortalA custom-built MCP (Model Context Protocol) server designed to streamline data access from data.unhcr.org. This server efficiently pulls structured humanitarian data from UNHCR’s public platform, enabling real-time integration with local systems, dashboards, and analytics pipelines. Hosted securely on mscp.so, it ensures reliable performance, optimized data throughput, and easy scalability for humanitarian applications. Key Features: Automated data extraction from UNHCR's open datasets Custom endpoint handling and transformation JSON/CSV-ready output for downstream use Secure, lightweight, and scalable architecture Real-time and scheduled pull options Use Cases: ✓ Humanitarian needs analysis ✓ Refugee response dashboards ✓ Donor and partner reporting ✓ Integration with local WMS or data lakes
mcp-so:unhcr-data-portal_Shahzad ASGHAR
View sourceFirst Seen
Feb 19, 2026
Last Scanned
Feb 20, 2026
Findings
2
Score
92/100
Findings (2)
Detects -y, --yes, or --auto-approve flags in MCP/skill install commands that bypass user confirmation
"-y" Remove the -y/--yes auto-confirm flag from MCP server launch arguments. This flag bypasses user confirmation prompts and allows unattended execution of potentially dangerous operations.
Likely FP if the matched text is an isolated flag (-y or --yes) in documentation describing command-line options, not in an actual MCP config.
Detects MCP server configs using npx to run packages without version pinning
"command": "npx" Pin the npx package in the MCP config to an exact version (e.g., @scope/server@1.2.3). Unpinned npx commands can silently fetch a compromised package version.
Likely FP if the MCP config is a local development setup example, though unpinned npx in production configs is a real supply chain risk.