FAOSTAT MCP — the UN Food and Agriculture Organization's statistics service.
MCPpedia last refreshed this data
io.github.pipeworx-io/faostat is an MCP server that FAOSTAT MCP — the UN Food and Agriculture Organization's statistics service. Its tool list has not been published yet over http, requires no API key, and scores 89/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"faostat": {
"url": "https://gateway.pipeworx.io/faostat/mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
FAOSTAT MCP — the UN Food and Agriculture Organization's statistics service.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @pipeworx/mcp-faostat against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in analytics
Ask your agent about your own Apple Health data: 194 metrics, 22 tools, local, 0 deps.
MCP server for Dynatrace Managed to access logs, events, and metrics.
Official PostHog MCP Server for product analytics, feature flags, experiments, and more.
Read and manage Churnkey cancel flows, retention metrics, and payment recovery
MCP Security Weekly
Get CVE alerts and security updates for io.github.pipeworx-io/faostat and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
UN Food and Agriculture Organization statistics — crop and livestock production, food balance sheets, agricultural trade, land and input use, farm emissions, food security and producer prices, for 245 countries and territories since 1961.
Part of Pipeworx — an MCP gateway connecting AI agents to 1864+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
faostat_domains(search?, domain_code?, limit?) — the 69 statistical domains,
with last-updated date and observation count. Gives you the domain code.faostat_dimensions(domain_code, dimension, search?, limit?) — the valid
area / element / item / year codes for a domain. Call this before the next one.faostat_data(domain_code, area?, element?, item?, year?, limit?) — the
observations, with unit, year and data-quality flag.Keyless.
DateUpdate and FileRows, which the query API does not.Things worth knowing:
fenixservices (the query API) was
returning Cloudflare 521 on every path, then timing out, through
2026-09-17 22:00–23:00 UTC while this pack was built; bulks-faostat was
unaffected throughout. The pack surfaces that as a named upstream outage —
an empty array here would read as "this country grows nothing".faostatservices.fao.org is a different host and answers
401 Missing Authorization Header. It is not a drop-in substitute.bulks-faostat.fao.org serves the catalogue JSON but 403s on per-domain
paths such as /production/QCL/QCL_AreaCodes_E.json; only the documented
catalogue and the zip bulk files are readable.faostat_dimensions exists and
why faostat_data says so explicitly on a zero-row answer.codex-mrl pack — that also reads fao.org but serves Codex
Alimentarius maximum residue limits.2026-09-17 — faostat_domains returned all 69 domains with update dates and row
counts. faostat_dimensions and faostat_data could not be verified: the FAO
query host was down for the whole build window (see above).
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"faostat": {
"url": "https://gateway.pipeworx.io/faostat/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/faostat/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https
... [View full README on GitHub](https://github.com/pipeworx-io/mcp-faostat#readme)