WHO Athena API MCP for AI. Audit global health trends and metrics.
Works with every AI agent you already use
…and any MCP-compatible client








Connect to your AI in seconds.
WHO Athena API provides programmatic access to global health indicators from the World Health Organization. It lets your AI agent audit historical medical data and track public health trends across countries, regions, or specific demographics.
Instead of manually searching through WHO portals, you can ask your agent to pull precise statistical datasets—like child mortality rates or life expectancy—and get verified data back instantly.
What your AI can do
Get health indicator data
Retrieves actual data points for a specific, identified health indicator code.
List health dimensions
Lists all metadata fields you can filter by, like 'country' or 'year'.
List health indicators
Provides a complete catalog of every possible health metric code available in the database.
List every available health metric code in the WHO database so you know exactly what data series exists.
See all possible organizational filters, like countries or years, to scope your search correctly.
Pull high-resolution statistical records for a specific indicator code and defined parameters.
Ask an AI about this
Waiting for input…
WHO Athena API: 4 Tools
Use these tools to check service status, list available dimensions, find indicator codes, and pull specific global health data points.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using WHO Athena API on VinkiusGet Health Indicator Data
Retrieves actual data points for a specific, identified health indicator code.
List Health Dimensions
Lists all metadata fields you can filter by, like 'country' or 'year'.
List Health Indicators
Provides a complete catalog of every possible health metric code available in the...
Check Api Status
Confirms if the WHO GHO Athena service is running and available right now.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
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 5,000+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,000+ 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
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 connection provides 4 powerful capabilities that interface natively with Claude, ChatGPT, Cursor, and other compatible AI platforms. No middleware. No custom integration required.
Sifting through web dashboards today is a nightmare.
Right now, getting global health stats means logging into multiple WHO portals. You click country dropdowns, select years, and run searches that spit out endless PDFs or complex CSV files. Then you spend hours copy-pasting numbers between spreadsheets just to compare two metrics.
With this MCP, the process vanishes. You tell your agent what you need—say, 'Show me life expectancy for Country A versus Country B in 2019.' Your agent handles the multiple API calls, gathers the data, and hands you a clean result set, period.
Retrieving structured health metrics with the WHO Athena API MCP
You no longer have to manually discover indicator codes or cross-reference dimension names. Your agent uses `list_health_indicators` to find the code and `list_health_dimensions` to define the scope, all before it executes a single data pull.
What's different now is control. You move from hoping a website has the data you need to demanding exactly what you want, with verifiable structure.
What your AI can actually do with this
This MCP connects your AI client directly to the World Health Organization’s authoritative repository for global health statistics. You stop wading through complex government websites and start asking natural language questions that yield verifiable, structured data. Your agent can pull high-resolution datasets, letting you audit regional trends or compare indicators across different countries without ever touching a web portal.
It's built to handle deep research workflows. For instance, your agent can use the WHO Athena API to identify all relevant health metrics, retrieve historical observations for those metrics, and then pass that structured data into another MCP—say, a policy drafting tool—to automatically generate an evidence-based report. This cross-MCP chaining ability is key; you move beyond just finding data to using it immediately in complex automation pipelines.
You'll find this runs on Vinkius, which manages the execution environment and ensures your credentials pass through a zero-trust proxy so your keys never sit unprotected on any disk.
019d849d-9c1f-726d-bd57-4984e8a63a26 Here's how it actually works
The bottom line is: you get verified global health stats without manual searching or spreadsheet cleanup.
First, use the API to discover the necessary health metrics or the dimensions (like country codes) required for your research.
Next, define the scope. Specify the exact indicator code and the time frame you need data for.
Finally, trigger a query to pull the dataset. Your agent gets back structured observations that fit right into your workflow.
Who is this actually for?
Epidemiologists, public health policy analysts, and medical researchers need this. They're tired of manually navigating dozens of WHO dashboards just to compare two metrics from three different continents.
Uses the MCP to audit global trends, comparing indicators across regions or over decades for policy reports.
Runs comparative analyses on specific disease markers, verifying data consistency without downloading and cleaning massive CSV files.
Identifies unique indicator codes and metadata to classify archival health datasets for deep-dive academic work.
What Changes When You Connect
Stop guessing codes. Use list_health_indicators to pull a full catalog of every available metric, guaranteeing you find the exact code for your research.
Get immediate operational visibility using check_api_status. You know if the data source is down before your agent starts wasting time on broken calls.
Scope your queries instantly. Use list_health_dimensions to see every available filter, like 'year' or 'region', so you never pull irrelevant datasets.
Retrieve complex data without manual steps. Once you have the code and dimensions, get_health_indicator_data pulls accurate observations directly into your agent’s context.
Maintain an auditable trail of all calls. Every action generates a cryptographically signed log, giving you proof of exactly what data was accessed and when.
See it in action
Comparing mortality rates across continents
A public health analyst needs to compare the child mortality rate from 2015 versus 2023. They use list_health_indicators to get the code, then run get_health_indicator_data, specifying 'country' and 'year' in the dimensions list to get a clean, comparative table for their report.
Auditing data source reliability
An operations lead needs to know if the WHO API is up before running an expensive job. They first call check_api_status. If it fails, they don't waste time on complex queries.
Finding a niche indicator code
A researcher knows they need data for 'Malnutrition prevalence' but doesn't know the code. They use list_health_indicators to browse the full catalog until they find the correct, unique identifier.
Building a multi-platform report
An agent uses this MCP to pull global health statistics, then chains that data output into a messaging MCP to automatically draft and send an executive summary email to policy stakeholders.
The honest tradeoffs
Guessing indicator codes
The user tries to query 'Child Mortality' using a common name, but the API fails because it needs the official WHO code.
Don't guess. Start by running list_health_indicators first. Find the exact required identifier before attempting any data retrieval with get_health_indicator_data.
Forgetting dimensions
The user runs a query for 'Life Expectancy' but forgets to specify the year or country, resulting in ambiguous or useless data.
Always call list_health_dimensions before querying. It shows you what filters are available, guaranteeing your results have proper scope.
Relying on manual dashboards
A team spends half a day downloading multiple CSVs from different WHO web pages, then manually merging them in Excel to find a trend.
Let your agent handle it. Use this MCP to pull the raw data programmatically and immediately pass it into another tool for analysis.
When It Fits, When It Doesn't
Use this MCP if your job requires deep, auditable comparisons of global health metrics across specific parameters (country, year). It's essential when you need proof that a statistic came from an authoritative source. Don't use it if all you need is a simple 'green/red' status check; in that case, a basic monitoring tool is enough. You must use this MCP for any workflow where the data integrity and specific metadata dimensions are non-negotiable.
Questions you might have
How do I check if the WHO Athena API MCP works? +
You call check_api_status. This simply confirms that the underlying service is operational and available for use right now.
What data does get_health_indicator_data pull? +
It pulls actual statistical observations. You give it an indicator code, and it returns the recorded values for that metric across your defined dimensions.
Why do I need to run list_health_indicators first? +
You must find the precise indicator code before pulling data. Running list_health_indicators gives you the full catalog, preventing guesswork and failed queries.
Can this MCP help me automate a report? +
Yes. You can use this MCP to pull raw metrics and then chain that output into another agent or tool—like a messaging MCP—to automatically draft the final policy document.
How do I use `list_health_dimensions` to make sure my query is properly scoped? +
It lists all valid observation dimensions, like 'country' or 'year'. Running this tool first helps you structure your data requests and ensures that when you call get_health_indicator_data, the output segments correctly.
Do I need to manage API keys or credentials for this WHO Athena MCP? +
No. Since the underlying WHO GHO service is free and open, your agent doesn't require an API key. You simply connect through Vinkius, keeping your workflow secure.
What happens if I use a non-existent code with `get_health_indicator_data`? +
The MCP will return a specific error message telling you the indicator is invalid. Before querying data, always verify your desired code by running list_health_indicators to confirm its status.
Is this MCP limited by rate limits or usage caps? +
The platform handles infrastructure updates and manages API calls securely within Vinkius's sandbox. For operational details, you can always check the system health using the check_api_status tool.
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).
We've already built the connector for WHO Athena API. Just plug in your AI agents and start using Vinkius.
No hosting. No infrastructure. No complex setup.
All 4 tools are live and waiting.
You're up and running in seconds.
Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.
Built, hosted, and secured by Vinkius. You just connect and go.