updated 2026-11-10 04:07 UTC

FAOSTAT MCP

Repository

MCP server that exposes the full FAOSTAT API as tools for AI assistants — query UNFAO Food & Agriculture Statistics in natural language via Claude, Cursor, or any MCP-compatible client.

MCP Servers Python Listed MIT

Is FAOSTAT MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.2 / 10
Provenance Attested
Signed commits 30%
Last push 39d ago
Advisories None known
Compare FAOSTAT MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: FAOSTAT MCP scores 64.6/100 (Grade C), ranked #548 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 4.2/10; 30% of recent commits are signed; no published advisory affects its latest release (faostat-mcp); last pushed 2026-10-02. Every point is earned from checkable signals — never paid placement. How scoring works →

How FAOSTAT MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships FAOSTAT MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/berba-q/faostat-mcp, MIT, last pushed 2026-10-02. 30% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.2/10 (scanned Nov 8, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 5
    CI-Tests 2
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 6
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages Linked and attested

    • PyPI faostat-mcp Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: faostat-mcp 1.3.0. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-09-02 OSSF Scorecard: 4.4/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues FAOSTAT MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How FAOSTAT MCP compares in MCP Servers

  1. #310 Webcomponents MCP Server 64.7 +0.1
  2. #311 Anythingmcp 64.6 ±0
  3. #312 FAOSTAT MCP 64.6 this agent
  4. #313 MCP Proxmox 64.6 ±0
  5. #314 MCP Server for WinDbg Crash Analysis 64.5 −0.1

Bars show each HVTrust score; the tick marks FAOSTAT MCP’s 64.6.

Where the 64.6 comes from

HVTrust dimensions vs the MCP Servers average

64.6 / 100 · 100.0% confidence

FAOSTAT MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
14.2 / 25
3.4 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
12.1 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
9.4 / 20
2.8 below avg 12.2
AdoptionLog-scaled stars · package downloads
6.2 / 20
1.4 below avg 7.6

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-11-01
Grade Changed
Trust grade B → C
2026-11-01
Rank Moved
Rank dropped 123 spots (#413 → #536)
2026-11-01
HVTrust Changed
HVTrust down 3.9pts (68.4 → 64.5)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.2/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 39 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
31.2
Activity sub-score · out of 100
#312
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 39 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
20
Forks
5
Last Push
2026-10-02
39 days ago
Commits (4 wk)
0
Downloads (7d)
179
pypi
HN mentions (30d)
—
Open Issues
0
Rank Change
▼4
was #544

Analysis

Activity Inputs

31.2 / 100
StarsRepository reach
7.9 / 30
FreshnessLast push recency
19.6 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
3.6 / 20

Common questions about FAOSTAT MCP

FAOSTAT MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does FAOSTAT MCP publish package provenance?
Yes. FAOSTAT MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does FAOSTAT MCP have an OpenSSF Scorecard?
FAOSTAT MCP has an OpenSSF Scorecard score of 4.2/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is FAOSTAT MCP actively maintained?
Slowing down. Last push was 39 days ago — keep an eye on whether activity resumes.
What license does FAOSTAT MCP use?
FAOSTAT MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are FAOSTAT MCP's commits signed?
29% of the last 100 commits to FAOSTAT MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
FAOSTAT MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
1 tags
Broad capability areas detected.
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to FAOSTAT MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-10-02
Activity Resumed
Activity resumed
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain FAOSTAT MCP?

For maintainers

HVTrust scores FAOSTAT MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 28HVTrust 4Grade 4Score 2Scorecard 1Delisted 1Listed 1Provenance 1MCP 1Surface 1Fresh 1
2026-11-01
Grade Changed
Trust grade B → C
2026-11-01
Rank Moved
Rank dropped 123 spots (#413 → #536)
2026-11-01
HVTrust Changed
HVTrust down 3.9pts (68.4 → 64.5)
2026-11-01
Activity Score Changed
Activity score down 12pts (44 → 32)
2026-10-27
Rank Moved
Rank dropped 12 spots (#386 → #398)
2026-10-24
Rank Moved
Rank rose 22 spots (#403 → #381)
2026-10-20
Rank Moved
Rank dropped 10 spots (#381 → #391)
2026-10-11
Rank Moved
Rank rose 46 spots (#388 → #342)
2026-10-09
Rank Moved
Rank dropped 15 spots (#366 → #381)
2026-10-03
Rank Moved
Rank dropped 36 spots (#320 → #356)
2026-10-02
Activity Resumed
Activity resumed
2026-10-02
Grade Changed
Trust grade C → B
2026-10-02
Rank Moved
Rank rose 464 spots (#784 → #320)
2026-10-02
HVTrust Changed
HVTrust up 15.2pts (55.3 → 70.5)
2026-10-02
Activity Score Changed
Activity score up 36pts (13 → 48)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 470 spots (#1240 → #770)
2026-09-23
HVTrust Changed
HVTrust up 39.2pts (16.2 → 55.4)
2026-09-22
Newly Listed
First tracked at rank #1240
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Rank Moved
Rank dropped 37 spots (#715 → #752)
2026-09-07
Rank Moved
Rank dropped 45 spots (#618 → #663)
2026-09-06
Rank Moved
Rank dropped 20 spots (#598 → #618)
2026-09-05
Rank Moved
Rank dropped 71 spots (#527 → #598)
2026-09-04
Rank Moved
Rank dropped 22 spots (#505 → #527)
2026-09-03
Rank Moved
Rank dropped 32 spots (#473 → #505)
2026-09-02
Scorecard Added
OSSF Scorecard: 4.4/10
2026-09-02
Grade Changed
Trust grade D → C
2026-09-02
Rank Moved
Rank rose 227 spots (#700 → #473)
2026-09-02
HVTrust Changed
HVTrust up 9.2pts (49.0 → 58.2)
2026-09-01
Rank Moved
Rank dropped 30 spots (#670 → #700)
2026-08-31
Rank Moved
Rank dropped 38 spots (#632 → #670)
2026-08-30
Rank Moved
Rank dropped 14 spots (#618 → #632)
2026-08-29
Rank Moved
Rank dropped 40 spots (#578 → #618)
2026-08-28
Rank Moved
Rank dropped 15 spots (#563 → #578)
2026-08-27
Rank Moved
Rank dropped 14 spots (#549 → #563)
2026-08-26
Rank Moved
Rank dropped 75 spots (#474 → #549)
2026-08-24
Rank Moved
Rank dropped 15 spots (#459 → #474)
2026-08-22
Rank Moved
Rank rose 14 spots (#469 → #455)
2026-08-19
Rank Moved
Rank dropped 11 spots (#456 → #467)
2026-08-17
Rank Moved
Rank rose 11 spots (#467 → #456)
2026-08-13
Rank Moved
Rank dropped 14 spots (#448 → #462)
GitHub → PyPI: faostat-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 64.6 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/faostat-mcp.svg)](https://hvtracker.net/agents/faostat-mcp)
HTML:
<a href="https://hvtracker.net/agents/faostat-mcp"><img src="https://hvtracker.net/badge/faostat-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON