Development Indicators MCP server
online · 100% uptimeio.github.lbruce-wq/development-indicators·v0.4.1·2 starsOpen-source MCP for official development indicators with provenance and citations.
2 stars
Reviews
Write oneNobody has reviewed Development Indicators MCP yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Development Indicators MCP tools (10)
write = sends, deletes, buys or postscompare_observationsFreeRetrieve series side by side and flag obvious metadata differences without merging them.
faostat_list_domainsFreeList live FAOSTAT groups and domains available to build source-qualified series.
faostat_search_dimensionFreeSearch a FAOSTAT domain's area, item, element, unit, or other definition table.
find_microdataFreeFind relevant public microdata catalogues and state their access conditions.
get_indicator_metadataFreeRetrieve authoritative metadata for a source-qualified series reference.
get_observationsFreeRetrieve official observations while retaining metadata, citations and warnings.
get_source_setupFreeExplain source access requirements without exposing server secrets.
list_sourcesFreeList supported and planned official data sources and their access characteristics.
resolve_geographiesFreeResolve country names or codes to ISO 3166-1 alpha-3 codes such as GHA and KEN.
search_indicatorsFreeRank official indicators; returns match evidence, retrieval health and source failures.
Public scan report
scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 1144ms20/20
- Tool poisoning10 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 15 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Development Indicators MCP compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 91/100
- higher than 85% of 48,255 servers
- Tools
- 10
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 798 ms
- faster than 16% of 30,031 servers
- GitHub stars
- 2
- more than 75% of 28,688 servers
What its tools let an agent do: 10 read
Install Development Indicators MCP in Claude Code, Cursor or VS Code
claude mcp add --transport http development-indicators https://indicatorsmcp.impactengines.ai/mcp
What the publisher says
From the Development Indicators MCP repository's README, as published. We do not edit it. Read it on GitHub
Development Indicators MCP
A provenance-first Model Context Protocol gateway for official international-development indicators.
Hosted MCP endpoint: https://indicatorsmcp.impactengines.ai/mcp
The project aims to let AI agents discover and query authoritative indicators across institutions such as the World Bank, UN agencies, FAO, WHO, UNICEF, ILO and the DHS Program through one consistent interface. It preserves definitions, units, dimensions, source codes and citations rather than returning uncited prose.
Current milestone
The repository contains a working vertical slice:
UNESCO UIS, OECD and ADB adapters;
- remote-capable MCP server using Streamable HTTP, with stdio support for local clients;
- source registry describing APIs, authentication and capabilities;
- normalized indicator and observation schemas;
- live World Bank, WHO GHO, UNICEF, FAOSTAT, ILOSTAT, IMF, UNSD SDG,
bounded provider waits and a 15-minute query cache;
- on-demand FAOSTAT authentication with no background token refresh;
- dynamic FAOSTAT domain, country, item and element discovery;
- weighted live catalogue search with aliases, match explanations, retrieval-health signals,
- partial-failure comparisons, typed errors, native structured outputs and compact responses;
- partial-success geography resolution with structured unresolved-country errors;
- normalized ILOSTAT frequency labels and FAOSTAT dimension-ranking evidence;
- tools to resolve country names, inspect metadata and retrieve observations;
- unit tests for normalization and source behaviour.
This is a public beta, not a production statistical service. The hosted instance is provided for evaluation; you can also run or deploy your own copy.
MCP tools
- list_sources(topic=None)
- getsourcesetup(source_id)
- searchindicators(query, sourceids=None, limit=10)
- getindicatormetadata(series_ref)
- getobservations(seriesref, countrycodes, startyear=None, endyear=None, latestonly=False, include_original=False)
- compareobservations(seriesrefs, country_codes, ...)
- find_microdata(query, country=None)
- faostatlistdomains(limit=50, cursor=0, groupcode=None, status=None, includearchived=False)
- faostatsearchdimension(dataset, dimension, query, limit=20, cursor=0)
- resolvegeographies(namesor_codes)
Series references use the form sourceid:seriescode, for example worldbank:SP.POP.TOTL. Observation calls accept ISO 3166-1 alpha-3 codes such as GHA and KEN; use resolvegeographies when a prompt supplies country names. Mixed batches return both resolved and unresolved entries instead of failing the entire request.
Local development
py -3.11 -m venv .venv
.venv\Scripts\Activate.ps1
pip install -e ".[dev]"
pytest
development-data-mcpFor macOS or Linux, activate the environment with source .venv/bin/activate.
Run the live-source smoke benchmark with:
python -m benchmarks.runThe FAOSTAT check is skipped until FAOSTATUSER and FAOSTATPASSWORD are configured; all public-source checks run without credentials.
The default transport is stdio. To run a hosted-style HTTP endpoint:
$env:MCP_TRANSPORT = "streamable-http"
$env:MCP_HOST = "127.0.0.1"
$env:MCP_PORT = "8000"
development-data-mcpThe MCP endpoint is then exposed at /mcp. Production deployment must add HTTPS, authentication, rate limiting and audit logging at the application or gateway layer.
Install in Codex
The hosted service uses Streamable HTTP:
codex mcp add development-indicators --url https://indicatorsmcp.impactengines.ai/mcp
codex mcp listShortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Development Indicators MCP: common questions
- Is Development Indicators MCP server safe?
- Yes, by our scan: it is graded A (91/100). Read the Development Indicators MCP safety report
- How do I install Development Indicators MCP?
- It runs remotely at indicatorsmcp.impactengines.ai. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Development Indicators MCP need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Development Indicators MCP maintained?
- The last commit was 49 days ago (2026-09-16). The latest release is v0.4.1.
- Is Development Indicators MCP up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Development Indicators MCP compare with other MCP servers?
- safety score 91/100 (higher than 85% of 48,255 servers); tools 10 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.