MCP.Market

Faostat MCP server

online · 100% uptime
by pipeworx-io·io.github.pipeworx-io/faostat·v0.2.1

FAOSTAT MCP — the UN Food and Agriculture Organization's statistics service.

A87/100grade A
What users say
No reviews yet
Be the first
Safety scan
A87/100

not scanned yet

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Faostat yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Faostat tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Faostat compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
87/100
higher than 73% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
1,071 ms
faster than 10% of 30,031 servers

Release history: 6 versions in the registry since 2026-09-25, latest 2026-11-01, typically one every 4 days.

Install Faostat in Claude Code, Cursor or VS Code

claude mcp add --transport http faostat https://gateway.pipeworx.io/faostat/mcp
Add to Cursor

What the publisher says

From the Faostat repository's README, as published. We do not edit it. Read it on GitHub

@pipeworx/faostat

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 1679+ live data sources.

Tools

with last-updated date and observation count. Gives you the domain code.

  • faostatdomains(search?, domaincode?, limit?) — the 69 statistical domains,

area / element / item / year codes for a domain. Call this before the next one.

  • faostatdimensions(domaincode, dimension, search?, limit?) — the valid

observations, with unit, year and data-quality flag.

  • faostatdata(domaincode, area?, element?, item?, year?, limit?) — the

Auth

Keyless.

Data sources

catalogue. Carries DateUpdate and FileRows, which the query API does not.

  • — the domain

dimension code lists.

  • —
  • — observations.

Things worth knowing:

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".

  • Two hosts, and they fail independently. fenixservices (the query API) was

401 Missing Authorization Header. It is not a drop-in substitute.

  • faostatservices.fao.org is a different host and answers

paths such as /production/QCL/QCLAreaCodesE.json; only the documented catalogue and the zip bulk files are readable.

  • bulks-faostat.fao.org serves the catalogue JSON but 403s on per-domain

an empty result, not an error, which is why faostatdimensions exists and why faostatdata says so explicitly on a zero-row answer.

  • FAOSTAT codes are numeric and domain-specific. A wrong item code returns

Alimentarius maximum residue limits.

  • Not the codex-mrl pack — that also reads fao.org but serves Codex

Verified

2026-09-17 — faostatdomains returned all 69 domains with update dates and row counts. faostatdimensions and faostat_data could not be verified: the FAO query host was down for the whole build window (see above).

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "faostat": {
      "url": "https://gateway.pipeworx.io/faostat/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/faostat/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, 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://gateway.pipeworx.io/mcp"
    }
  }
}

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Faostat: common questions

Is Faostat MCP server safe?
Yes, by our scan: it is graded A (87/100). Read the Faostat safety report
How do I install Faostat?
It runs remotely at gateway.pipeworx.io. 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 Faostat need an API key?
Yes. The registry entry asks for PIPEWORX_API_KEY.
Is Faostat maintained?
The last commit was 40 days ago (2026-09-25). The latest release is v0.2.1.
Is Faostat up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Faostat compare with other MCP servers?
safety score 87/100 (higher than 73% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 1,071 ms (faster than 10% of 30,031 servers). Full comparison.

More from pipeworx-io →