Faostat
NPM · @PIPEWORX/MCP-FAOSTAT · 2 COMPONENTS
FAOSTAT MCP — the UN Food and Agriculture Organization's statistics service.
Available components
Last scanned (12 hours ago)
Scores higher than 83% of npm servers
Category Data and Analytics
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-faostat). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 20 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 21 Nov 26 +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.
- 18 Nov 26 +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.
- 16 Nov 26 +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.
- 14 Nov 26 +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.
- 12 Nov 26 +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.
- 10 Nov 26 +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.
- 8 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Nov 2026 · Analysed npm/@pipeworx/mcp-faostat@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-faostat |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-faostat/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635936457 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b5106b47e93741edca5f15da2f12a33d355cd64f00e5c43201f6d6387ac3926961cfd589db7d9b7275b99940cc919d2925f0c538f5add1f87d7f31c31 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
faostat_data ~346
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".
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
faostat_dimensions ~273
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dimension | string | yes | 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 | yes | 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". |
No output schema declared.
No examples provided.
faostat_domains ~235
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".
| Name | Type | Req | Description |
|---|---|---|---|
| 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". |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-faostat
claude mcp add pipeworx-io-faostat -- npx -y @pipeworx/mcp-faostat
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.