WHO Athena API MCP. Audit global health indicators with AI.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
WHO Athena API gives your agent direct read access to World Health Organization global health data. Use it to audit specific indicators, track regional trends over time, and browse the entire WHO indicator catalog—all through natural language commands from your AI client.
What your AI agents can do
Check api status
Checks if the WHO GHO Athena service is currently running and accessible.
Get health indicator data
Fetches specific data points for a single, named WHO health indicator code.
List health dimensions
Lists all available metadata axes, such as 'country' or 'year,' to guide your research scope.
Your agent fetches data points (e.g., life expectancy) for a single, defined WHO indicator code.
It pulls time-series data to show how a given metric has changed across years and regions.
The agent accesses the WHO catalog, providing a complete list of every health indicator code you can research.
You prompt it to list metadata like 'country' or 'year,' ensuring your query is scoped correctly for comparison.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
WHO Athena API MCP Server: 4 Tools for Data Access
These tools let your agent check service status, pull specific metrics, list all available dimensions, or browse the entire catalog of global health indicators.
019d849dcheck api status
Checks if the WHO GHO Athena service is currently running and accessible.
019d849dget health indicator data
Fetches specific data points for a single, named WHO health indicator code.
019d849dlist health dimensions
Lists all available metadata axes, such as 'country' or 'year,' to guide your research scope.
019d849dlist health indicators
Retrieves the complete catalog of every health indicator series available in the WHO GHO database.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with WHO Athena API, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
WHO Athena API gives your agent direct read access straight into World Health Organization global health data. You won't gotta navigate any web portal or manually query spreadsheets; your AI client handles all that heavy lifting using natural language commands.
This server acts like a real-time public health analyst, pulling verified statistics and metadata right from the WHO GHO database. It lets you audit complex public health indicators and map historical trends without needing to know internal code structures beforehand. You're gonna be able to run deep research workflows by simply asking your agent what you need.
When you plug in your AI client, it first uses check_api_status to confirm the WHO GHO Athena service is up and running before doing anything else. This keeps sure everything is accessible right out of the gate.
To scope out a project, your agent can run list_health_indicators, which pulls the complete catalog of every single health indicator series available in the entire WHO GHO database. If you need to figure out what metrics exist—like rates for specific diseases or life expectancy measurements—this function gives you that full list of codes.
Before getting data, your agent often needs context. It runs list_health_dimensions if you need to know what metadata axes are available for comparison; this lists things like 'country,' 'year,' or other geographical boundaries so you can scope your research correctly. This function ensures that when you pull a dataset, it's set up for precise comparison.
Once you have the indicator code and the dimensions locked down, your agent uses get_health_indicator_data. This tool fetches specific data points—say, life expectancy or maternal mortality rates—for a single, defined WHO health indicator code across the parameters you selected. You can track how one metric changes over multiple years for different regions using this method.
Your workflow looks like this: first, your agent checks if the API is live. Then, it lets you browse the entire catalog of available indicators with list_health_indicators. Next, it shows you what dimensions are possible—whether that's by country or year—using list_health_dimensions. Finally, when you tell it exactly what data you want, it uses get_health_indicator_data to pull those specific statistics.
It's a clean chain of commands for auditing global health trends.
It’s designed for deep archival work, allowing your agent to read thousands of official WHO health identifiers and map out longitudinal spread across various metrics. You don't gotta worry about the underlying database structure; you just talk to your agent, and it handles querying the whole thing.
How WHO Athena API MCP Works
- 1 Subscribe to the WHO Athena API server. No API key is needed because this is a free, open service.
- 2 Connect your preferred AI client (Claude, Cursor, etc.) to the MCP Server.
- 3 Ask your agent to perform an action: e.g., 'Get data for child mortality rate' or 'List all country codes.' The agent runs the necessary tool and returns structured data.
The bottom line is that you talk to your AI client, and it manages the complex data calls to WHO in the background.
Who Is WHO Athena API MCP For?
This server is for researchers who spend too much time manually clicking through dashboards. If you’re an epidemiologist needing longitudinal data or a policy maker checking global trends, this cuts out all the friction and lets your agent do the heavy lifting.
Runs audits comparing indicator patterns across multiple regions to spot public health anomalies.
Retrieves official, verified global data points to build case studies for policy recommendations.
Performs rapid checks on regional health status and pulls specific stats without needing an internal database connection.
What Changes When You Connect
- Check data integrity immediately. Use
check_api_statusto verify the entire WHO GHO service is operational before starting a deep research audit. - Get specific metrics fast. The
get_health_indicator_datatool retrieves exact statistical values for any indicator code you name, skipping manual searches entirely. - Structure your query perfectly. Call
list_health_dimensionsfirst to see all available metadata axes (like 'region' or 'year') so you don’t scope your data incorrectly. - Know what you can research. Running
list_health_indicatorsgives you the entire catalog, letting you find indicator codes like WHOSIS_000001 without reading a massive manual. - Maintain workflow continuity. Your agent handles cross-referencing dimensions and indicators automatically, so you never lose track of your data lineage.
Real-World Use Cases
Comparing child mortality across continents
A researcher needs to compare the rate for 'Child mortality rate' (WHOSIS_XXXX) between Asia and Africa. They first run list_health_indicators to confirm the code, then use list_health_dimensions to ensure both 'country' and 'region' are available axes before calling get_health_indicator_data for a comparative audit.
Verifying an old policy statistic
A policy analyst needs the exact data point for life expectancy in 1995. Instead of searching archives, they ask their agent to use get_health_indicator_data, passing the specific code and year/country metadata, instantly validating the historical number.
Building a new research dataset
A medical journalist wants to know what kind of data is available for infectious diseases. They first call list_health_indicators to get thousands of potential codes, then use get_health_indicator_data on the top five candidates to build their article's core stats.
Checking system readiness before launch
An operations lead needs to confirm if any data pull is possible. They first run check_api_status to ensure connectivity, then use list_health_dimensions to confirm the basic structure is online and ready for querying.
The Tradeoffs
Guessing indicator codes
Trying to query 'Life expectancy' without knowing its official code (e.g., WHOSIS_000001) and getting an error.
→
Don't guess. First, run list_health_indicators to get the full catalog. Then, use that precise code with get_health_indicator_data. This guarantees you query the right series.
Forgetting scope details
Running a data pull without specifying if the data should be for 'country' or 'region,' leading to ambiguous results.
→
Before querying, always run list_health_dimensions. This shows you all valid axes. Then, include that dimension in your call to get_health_indicator_data.
Ignoring service status
Starting a complex audit and failing halfway through because the WHO endpoint was temporarily down or rate-limited.
→
Always run check_api_status first. This simple check confirms the entire workflow is viable before you spend time crafting detailed queries.
When It Fits, When It Doesn't
Use this server if your task requires retrieving official, global health statistics sourced directly from WHO. It's perfect for research teams that need to audit historical trends or compare indicators across different countries and years.
Don't use it if you are looking for proprietary data (like private hospital records) or localized datasets not indexed by the WHO GHO service. If your problem is internal, you need a database connector; this tool only handles public global health metadata. Use list_healthindicators when you need to know what can be checked, and use get_health_indicator_data when you already know what you want.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by WHO Athena. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 4 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Auditing global data used to be a nightmare of clicks.
Before the WHO Athena API, gathering comprehensive health statistics meant bouncing between multiple WHO portals. You'd manually search for an indicator code, then filter by country, and finally pull a time-series graph—a process that took hours and was prone to copy/paste errors.
Now, you just tell your agent: 'Give me the trend for child mortality in Southeast Asia from 2010 to 2020.' The agent calls `get_health_indicator_data`, handles all the dimension filtering using `list_health_dimensions`, and returns clean data. It’s that simple.
WHO Athena API MCP Server: Accessing Global Health Indicators
You used to have to contact a WHO representative or download massive CSV files just to check one statistic, and you often didn't know which exact indicator code (like WHOSIS_...) was needed. The process was slow, opaque, and required specialized knowledge.
Now, your agent handles the discovery work. You run `list_health_indicators` to see every single available series, eliminating guesswork. It brings institutional-grade data directly into your conversation.
Common Questions About WHO Athena API MCP
Is an API Key required for WHO Athena API? +
No. The WHO Global Health Observatory API is a free and open service. This server works out of the box without any static credentials required.
What format is the data returned in? +
The API returns detailed health indicator data including numeric values, spatial dimensions (countries), and time dimensions (years).
Can I filter by indicator code? +
Yes. Use the get_health_indicator_data tool and provide the WHO indicator code (e.g., 'WHOSIS_000001' for life expectancy).
If I get an error running `get_health_indicator_data`, how do I check if the server itself is down? +
Use the check_api_status tool first. This immediately confirms whether the WHO GHO Athena service is operational before you run a complex data pull. It saves time and points directly to connection issues versus query errors.
Before I run `get_health_indicator_data`, how do I see all possible codes available using `list_health_indicators`? +
list_health_indicators pulls the full catalog of thousands of WHO health identifiers. This is crucial for knowing exactly which data series you can audit, eliminating guesswork before writing a query.
How do I find out what grouping options (like 'country' or 'year') exist for my data when querying with `get_health_indicator_data`? +
Run the list_health_dimensions tool. It shows every available observation dimension, giving you strict control over how your resulting dataset is filtered and organized.
What clients or AI agents can I connect to use these tools in my workflow? +
This server works with any MCP-compatible agent. As long as your client supports the Model Context Protocol, you can route global health data through it—whether that's Cursor, Claude, or another system.
Are there rate limits when I use `get_health_indicator_data` or other tools? +
The underlying WHO GHO API is a free and open service. While we recommend thoughtful querying to avoid overloading the endpoint, any specific usage quotas are managed according to standard WHO guidelines.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
GameScorekeeper
Access live sports scores, fixtures, lineups, team form, and player statistics via AI — covering major football competitions worldwide.
Countly
Manage product analytics via Countly — track user sessions, record custom events, and query deep behavioral metrics directly from your AI agent.
Harmonyscan (Harmony One Block Explorer API)
Access Harmony One blockchain data — query balances, transactions, smart contracts, and network status directly from your AI agent.
You might also like
NASA Asteroids — Near-Earth Objects & Planetary Defense
Track near-Earth asteroids and space rocks in real-time: browse the NeoWs asteroid database, monitor upcoming close approaches from JPL CNEOS, look up specific asteroids by ID, and review atmospheric fireball events detected by government sensors worldwide.
NASA DONKI — Space Weather Intelligence
NASA's Space Weather Database: coronal mass ejections (CMEs), solar flares (C/M/X class), geomagnetic storms, interplanetary shocks, solar energetic particles, radiation belt events, and real-time notifications from the DONKI system.
Leiting Games
Leading game publisher and developer platform — manage submissions, track performance, and audit compliance via AI.