# Faostat (npm · @pipeworx/mcp-faostat)

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

- Trust score: 89/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- remote · `gateway.pipeworx.io`: 88/100, [markdown](https://verifymcp.io/servers/pipeworx-io-faostat/faostat-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-faostat/faostat-mcp)
- npm · `@pipeworx/mcp-faostat`: 89/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-faostat/pipeworx-mcp-faostat.md), [page](https://verifymcp.io/servers/pipeworx-io-faostat/pipeworx-mcp-faostat)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-faostat`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-22.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-faostat).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 20 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 906 tokens (~302/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Faostat MCP server?

Faostat runs locally as an npm package, launched with npx -y @pipeworx/mcp-faostat. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-faostat -- npx -y @pipeworx/mcp-faostat
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-faostat": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-faostat"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-faostat": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-faostat"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-faostat -- npx -y @pipeworx/mcp-faostat
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-faostat": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-faostat"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-faostat --command npx --arg -y --arg @pipeworx/mcp-faostat
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-faostat:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-faostat"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-faostat": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-faostat"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-faostat -t stdio -c npx -a -y @pipeworx/mcp-faostat
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-faostat": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-faostat"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-22 (score 89, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-11-21 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-08 (score 83, +1)

- [functional regression] Security disclosure: unverified → fail

## MCP tools (3)

### `faostat_domains` (~235 tokens)

The 69 statistical domains FAOSTAT publishes, with what each covers, when it was last updated and how many observations it holds. AUTHORITATIVE starting point for any question about world agriculture, food production, food security, agricultural trade, land use or farm emissions — FAOSTAT is the UN Food and Agriculture Organization's own statistics service and the reference series for these subjects. Returns the domain code (e.g. "QCL" crops and livestock production, "FBS" food balance sheets, "TCL" crops and livestock trade, "RFN" fertilisers by nutrient, "GT" agri-environmental emissions) that faostat_dimensions and faostat_data need. Search for "production", "trade", "emissions", "food security", "prices", "land".

Input parameters:

- `domain_code` (string): Return just this domain, e.g. "QCL".
- `limit` (number): Max domains to return (default 20, max 69).
- `search` (string): Case-insensitive substring matched against domain code, name, topic and description, e.g. "production".

### `faostat_dimensions` (~273 tokens)

The valid codes for one dimension of one FAOSTAT domain — the country/area codes, element codes (production quantity, area harvested, yield, import value, ...), item codes (wheat, cattle, nitrogen fertiliser, ...) or years a domain actually carries. Call this BEFORE faostat_data: FAOSTAT codes are numeric and domain-specific, so guessing them returns nothing rather than an error. Example: domain "QCL" dimension "element" lists production quantity (5510), area harvested (5312) and yield (5412); domain "QCL" dimension "item" lists the 278 crops and livestock products.

Input parameters:

- `dimension` (string, required): Which dimension to list: "area" (countries and territories), "areagroup" (regional aggregates), "element" (the measured quantity), "item" (the commodity), "itemsgroup" (commodity aggregates), "year",…
- `domain_code` (string, required): FAOSTAT domain code from faostat_domains, e.g. "QCL".
- `limit` (number): Max codes to return (default 50, max 1000).
- `search` (string): Case-insensitive substring filter on the code label, e.g. "wheat".

### `faostat_data` (~346 tokens)

Observations from a FAOSTAT domain — the actual numbers, with units, year and data-quality flag. AUTHORITATIVE for "how much <crop> did <country> produce in <year>", world agricultural trade flows, fertiliser and pesticide use, agricultural emissions and food-balance data. Pass codes from faostat_dimensions: area (country), element (what is measured) and item (the commodity) are all numeric domain-specific codes, not names. Example: domain "QCL", area "231" (United States of America), element "5510" (production quantity), item "15" (wheat), years "2020,2021,2022".

Input parameters:

- `area` (string): One or more FAOSTAT area codes, comma-separated, e.g. "231" or "231,68,100". From faostat_dimensions dimension "area".
- `domain_code` (string, required): FAOSTAT domain code, e.g. "QCL". From faostat_domains.
- `element` (string): One or more element codes, comma-separated, e.g. "5510" (production quantity). From faostat_dimensions dimension "element".
- `item` (string): One or more item codes, comma-separated, e.g. "15" (wheat). From faostat_dimensions dimension "item".
- `limit` (number): Max observations to return (default 100, max 2000).
- `year` (string): One or more years, comma-separated, e.g. "2022" or "2018,2019,2020,2021,2022". Omit for every year the domain holds.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-faostat/pipeworx-mcp-faostat#diagnostics

## Score history

- 2026-11-22: 89
- 2026-11-21: 89
- 2026-11-20: 88
- 2026-11-19: 88
- 2026-11-18: 88
- 2026-11-17: 87
- 2026-11-16: 87
- 2026-11-15: 86
- 2026-11-14: 86
- 2026-11-13: 85
- 2026-11-12: 85
- 2026-11-11: 84
- 2026-11-10: 84
- 2026-11-09: 83
- 2026-11-08: 83
- 2026-11-07: 82
- 2026-11-06: 82
- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### What is the Faostat MCP server?

Faostat is an MCP server listed in the public MCP registry as io.github.pipeworx-io/faostat. FAOSTAT MCP, the UN Food and Agriculture Organization's statistics service. This page covers its npm package (@pipeworx/mcp-faostat).

### Is the Faostat MCP server safe to use?

Faostat scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Faostat MCP server expose?

Faostat exposes 3 tools: faostat_domains, faostat_dimensions, faostat_data. Their descriptions and schemas cost roughly 854 tokens of context every time the server is loaded.

### Is the Faostat MCP server still maintained?

Faostat is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Faostat MCP server under?

Faostat declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Faostat MCP server?

VerifyMCP ran 15 checks on Faostat, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Faostat: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-faostat
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-faostat
- Repository: https://github.com/pipeworx-io/mcp-faostat
- Website: https://pipeworx.io/packs/faostat
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-faostat/pipeworx-mcp-faostat.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-faostat/pipeworx-mcp-faostat/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-faostat/pipeworx-mcp-faostat.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-faostat/pipeworx-mcp-faostat
