Is FAOSTAT MCP safe to use?

FAOSTAT MCP has an HVTrust score of 57.3/100 (Grade C), ranked #671 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for FAOSTAT MCP?

FAOSTAT MCP scores 57.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 16 GitHub stars and is categorized under MCP Servers.

FAOSTAT MCP

berba-q/faostat-mcp

MCP server that exposes the full FAOSTAT API as tools for AI assistants — query UNFAO Food & Agriculture Statistics in n

MCP Servers Python Grade C Listed MIT

57.3/100

Rank #671 of 1328

Compare FAOSTAT MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-04-15 · 146d ago

Recent change

Rank +9

Is FAOSTAT MCP safe? FAOSTAT MCP scores 57.3/100 (Grade C), ranked #671 of 1328 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.4/10; 29% of recent commits are signed; last pushed 2026-04-15. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#358 Rust MCP Sdk — 57.4 (C) → #359 MCP Arr — 57.3 (C) → #361 Plateau Creative MCP — 57.3 (C) → #362 Zotero MCP (kujenga) — 57.2 (C) →

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

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)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.4/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 146 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for FAOSTAT MCP View MCP Servers Report missing data

15.7

Activity sub-score · out of 100

#360

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 →

Rank Trend

2026-08-11 2026-09-08

Activity & Reach

Stars

Forks

Last Push

2026-04-15

146 days ago

Commits (4 wk)

Downloads (7d)

122

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼8

was #663

Analysis

HVTrust Dimensions vs MCP Servers

57.3 / 100 · 100.0% confidence

FAOSTAT MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

14.4 / 25

4.5 above avg 9.9

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.2 / 17

in line with avg 12.0

Maintenance60% last-push freshness · 40% commit activity

2.3 / 20

9.9 below avg 12.2

AdoptionLog-scaled stars · package downloads

5.7 / 20

1.2 below avg 6.9

Activity Inputs

15.7 / 100

StarsRepository reach

7.4 / 30

FreshnessLast push recency

4.7 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

3.6 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

4.4 / 10

OpenSSF Scorecard · scanned Sep 8, 2026

Signed Commits

29%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 5

CI-Tests 0

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 9

Vulnerabilities 10

Is FAOSTAT MCP safe?

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.4/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 146 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?

28% 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

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

Redis

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-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

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

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)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: declared → none

2026-08-12

Grade Changed

Trust grade C → D

2026-08-10

Rank Moved

Rank dropped 16 spots (#433 → #449)

2026-08-08

Newly Listed

First tracked at rank #687

GitHub → PyPI: faostat-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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.3 · Raw JSON