ESCAP Data Explorer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_indicatorsA | Step 1: Retrieve the full hierarchy of available SDG and Thematic indicators from UNESCAP Data Explorer. Browse the results and choose ONE indicator. The indicator code is the segment after the last # in the 'val' field. Only use indicator codes returned by this tool — do not invent or source codes from elsewhere. |
| get_indicator_metadataA | Step 2: Retrieve metadata (dimensions, attributes, structure) for a specific indicator. Call this after choosing an indicator from get_indicators. |
| get_countriesA | Step 3: Retrieve the full list of countries and reference areas available in UNESCAP Data Explorer, including their codes (id) and names. Use these codes when checking availability or fetching data. |
| check_data_availability | Step 4: Check whether data is available for a given indicator, country, and time period. Returns a list of countries with available data, or confirms/denies availability for a specific country. If no country is specified, lists all countries with data in the period. |
| get_dataA | Step 5: Retrieve actual data for a given indicator, optional country, and time period. Returns SDMX data (JSON or XML) including observation values, time periods, and attributes. It is recommended to call check_data_availability first to confirm data exists. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/un-shayani/ESCAP-SDMX-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server