Faostat (berba-q) MCP Server
faostat-mcp
PyPI
v1.2.2
Published by berba-q — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP server exposing the full FAOSTAT API to AI assistants
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 21.7 = 78. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −15.4 | Reference to a credential-exfiltration path in metadata MTC-INJ-TARGET-1 | injection |
| −6.3 | Description names a credential store the tool cannot reach MTC-INJ-SCHEMA-1 | injection |
2. Client adoption risk — 78 − 4 = 74. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 2
high Reference to a credential-exfiltration path in metadataMTC-INJ-TARGET-1
Reference to a credential-exfiltration path in metadata detected in the description of tool "faostat_setup". Instruction-like content in tool metadata is executed by the model, not the human, and is the primary tool-poisoning vector.
Evidence: ~/.config/faostat-mcp/credentials
Fix: Tool descriptions should describe behavior, not instruct the assistant. Treat imperative / secrecy / sequencing language in metadata as hostile.
Location: tool faostat_setup · description
medium Description names a credential store the tool cannot reachMTC-INJ-SCHEMA-1
Tool "faostat_setup" describes a credential store (SSH keys, cloud credentials, a keychain or an equivalent) that nothing in its input schema can address. A tool's interface is the honest statement of what it touches; prose that reaches past it is addressed to the model, not to a reader.
Evidence: keychain
Fix: Remove the reference, or expose the target as an explicit, validated parameter so the client can see and consent to what the tool reads.
Location: tool faostat_setup · description
Tools 21
Each tool and what it can reach — statically extracted from the published source.
faostat_list_bulk_downloadsingests untrusted inputfaostat_definition_typesno sensitive capabilityfaostat_get_codesno sensitive capabilityfaostat_get_datano sensitive capabilityfaostat_get_datasizeno sensitive capabilityfaostat_get_definitionsno sensitive capabilityfaostat_get_definitions_by_typeno sensitive capabilityfaostat_get_dimensionsno sensitive capabilityfaostat_get_metadatano sensitive capabilityfaostat_get_metadata_printno sensitive capability
Show 11 more tools ↓
faostat_get_rankingsno sensitive capabilityfaostat_get_report_datano sensitive capabilityfaostat_get_report_headersno sensitive capabilityfaostat_groups_and_domainsno sensitive capabilityfaostat_list_documentsno sensitive capabilityfaostat_list_domainsno sensitive capabilityfaostat_list_groupsno sensitive capabilityfaostat_pingno sensitive capabilityfaostat_refresh_tokenno sensitive capabilityfaostat_search_codesno sensitive capabilityfaostat_setupno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (21 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.2.2 latest |
C 74/100 | 2 | 1.13.0 | 2026-08-25 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan faostat-mcp --online --registry pypiOther implementations of Faostat 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Security & Testing
The Stripe Agent Toolkit enables popular agent frameworks including LangChain and Vercel's AI SDK to integrate with Stripe APIs through function calling.
MCP (Model Context Protocol) server for AgentGate. Enables Claude and other MCP-compatible AI assistants to request approvals.
Scan any website for AI agent readiness, payment protocols, and discovery endpoints
MCP server for aigently security guardrails — reads static catalog-data JSON, zero API dependency
Governed threat modeling, code threat verification, traceability & compliance, as MCP tools.
Governed threat modeling, code threat verification, traceability & compliance, as MCP tools.