Agro GPS
NPM · AGRO-GPS-MCP
Plant protection product registers of 30 countries, free; plus your farm notebook and finances
Available components
Last scanned (7 hours ago)
Scores higher than 45% of npm servers
Category Health and Science
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 36 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1683 tokens (~105/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 93% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 −2
- Stability: pass → 0.87 functional
- 3 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 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 5 Nov 2026 · Analysed npm/agro-gps-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
advisor_pending Advisor pending queue ~38
Entries of a farm that still need review or lack mandatory fields, with the list of missing fields.
| Name | Type | Req | Description |
|---|---|---|---|
| farm_id | string | yes | Farm id |
No output schema declared.
No examples provided.
advisor_portfolio Advisor portfolio ~38
For advisors and owners: every farm they can review, with entries, missing compliance fields, pending, flagged and approved counts and a traffic light.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bank_movements Bank movements ~93
Imported bank accounts with their last balance and movements, what each one was matched to and, for the unmatched ones, the best candidates with a score.
| Name | Type | Req | Description |
|---|---|---|---|
| farm_id | string | – | Farm id (from list_farms). Omit to use group_id |
| group_id | string | – | Group id (from list_groups) for figures consolidated across its farms |
| only_open | boolean | – | Only unmatched movements |
No output schema declared.
No examples provided.
budget_variance Budget vs actual ~117
Budget lines (campaign x farm x crop x category) with actual spend, remaining, used percentage and status ok / warning (90%+) / over. Amounts in euro cents.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign | string | – | Campaign as its starting year (a campaign runs from 1 September to 31 August). Default: current |
| farm_id | string | – | Farm id (from list_farms). Omit to use group_id |
| group_id | string | – | Group id (from list_groups) for figures consolidated across its farms |
No output schema declared.
No examples provided.
campaign_forecast Campaign close forecast ~111
ESTIMATE of how the campaign closes per crop: expected yield x price minus costs already imputed and the budget still pending, as a low / mid / high range, total and per hectare. Says whether each assumption was saved by the farm, taken from last campaign or is missing. Always present it as an estimate.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign | string | – | Campaign as its starting year (a campaign runs from 1 September to 31 August). Default: current |
| farm_id | string | yes | Farm id |
No output schema declared.
No examples provided.
cash_flow Cash-flow forecast ~102
Expected cash in and out by week or month from open receivables and payables, starting from the last imported bank balance, with overdue amounts apart.
| Name | Type | Req | Description |
|---|---|---|---|
| farm_id | string | – | Farm id (from list_farms). Omit to use group_id |
| granularity | string | – | – |
| group_id | string | – | Group id (from list_groups) for figures consolidated across its farms |
| horizon | integer | – | Number of weeks or months |
No output schema declared.
No examples provided.
check_plant_protection_product Check a plant protection product ~175
Free, no API key. Looks up one product by its official registration number in a country's register: authorisation state (authorised / withdrawn / expired), expiry date, formulation, active substances and authorised uses. With crop_eppo it also says whether the product is authorised on that crop. Includes a link to the product page.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country whose official register to use, e.g. ES, FR, DE, IT, PT, PL |
| crop_eppo | string | – | EPPO code of the crop to check the product against, e.g. VITVI (grapevine), OLVEU (olive) |
| registration | string | yes | Official registration number, e.g. ES-00725, 7400057 |
No output schema declared.
No examples provided.
entry_history Entry history ~37
Who created, edited or deleted a notebook entry and when, field by field (audit trail).
| Name | Type | Req | Description |
|---|---|---|---|
| entry_id | string | yes | Entry id |
No output schema declared.
No examples provided.
finance_dashboard Manager dashboard ~169
Money of a farm or a whole group for one campaign: month-by-month cost and income, cost by category (phyto, fertiliser, fuel, labour, machinery, seed, insurance, other), cost per hour per worker and per machine, margin per hectare per parcel and per crop, per-farm totals and KPIs of the last three campaigns. Amounts are integer euro cents.
| Name | Type | Req | Description |
|---|---|---|---|
| campaign | string | – | Campaign as its starting year (a campaign runs from 1 September to 31 August). Default: current |
| crop | string | – | Only this crop code |
| farm_id | string | – | Farm id (from list_farms). Omit to use group_id |
| group_id | string | – | Group id (from list_groups) for figures consolidated across its farms |
No output schema declared.
No examples provided.
group_overview Group overview ~63
Consolidated panel of a group: per farm, entries, cost, income, margin, treated hectares, compliance light (green/amber/red), pending review counts and a breakdown by crop; plus totals.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | Group id from list_groups |
No output schema declared.
No examples provided.
list_entries List notebook entries ~105
Field notebook entries (labores) of a farm: treatments, fertilising, irrigation, sowing, harvest, expenses… with the compliance fields (Anexo II). Paginated: pass `since` = the `next` cursor of the previous page. Deleted entries come back with deleted=true so a mirror can stay in sync.
| Name | Type | Req | Description |
|---|---|---|---|
| farm_id | string | yes | Farm id from list_farms |
| since | integer | – | Change cursor; 0 for the full notebook |
No output schema declared.
No examples provided.
list_farms List farms ~51
Farms (explotaciones) the API key can see, with the key owner's role in each, the plan and whether the holder data required for official submissions is complete. Call this first to get farm ids.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_groups List farm groups ~28
Groups (a company or cooperative holding several farms) the key owner belongs to, with their role.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
record_entry Record a notebook entry ~307
Register a task in the farm's field notebook (needs a key with write scope). The entry is attributed to the key owner and marked as written by API in the audit trail; the server stores when it arrived and rejects future dates. It only adds new entries: it never edits or deletes existing ones. Confirm the farm, parcel, product and date with the user before calling it. Official submission to the administration is never done here: it needs a person's session in the app.
| Name | Type | Req | Description |
|---|---|---|---|
| cost_cents | integer | – | Cost in euro cents |
| crop_code | string | – | EPPO crop code, e.g. OLVEU |
| entry_type | string | yes | Kind of task |
| event_at | string | yes | When it happened (ISO 8601 with offset) |
| farm_id | string | yes | Farm id from list_farms |
| parcel_refcat | string | yes | Cadastral reference of the parcel |
| product_name | string | – | Product or input used |
| quantity | number | – | Quantity applied |
| registration_number | string | – | Official registration number of the product (fito) |
| safety_days | integer | – | Pre-harvest interval in days |
| title | string | yes | Short title, e.g. 'Tratamiento · Azufre mojable' |
| treated_area_ha | number | – | Treated area in hectares |
| unit | string | – | Unit, e.g. 'L/ha', 'kg', 'mm' |
No output schema declared.
No examples provided.
search_plant_protection_products Search plant protection products ~144
Free, no API key. Searches the official register of plant protection products (pesticides, fungicides, herbicides) of a European country by commercial product name and says whether each one is still authorised. Returns up to 15 matches with registration number, holder, status and a link to its page. Search by trade name (e.g. 'Roundup'), not by active substance.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country whose official register to use, e.g. ES, FR, DE, IT, PT, PL |
| q | string | yes | At least three letters of the commercial product name |
No output schema declared.
No examples provided.
treasury_dues Receivables and payables ~105
Money to collect (receivable) and to pay (payable) with issue date, due date, paid date, status (open / overdue / paid) and days overdue, plus totals.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | – |
| farm_id | string | – | Farm id (from list_farms). Omit to use group_id |
| group_id | string | – | Group id (from list_groups) for figures consolidated across its farms |
| status | string | – | – |
No output schema declared.
No examples provided.
How do I install the Agro GPS MCP server?
Agro GPS runs locally as an npm package, launched with npx -y agro-gps-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · agro-gps-mcp
claude mcp add eu-agrogps-agro-gps -- npx -y agro-gps-mcp
What is the Agro GPS MCP server?
Agro GPS is an MCP server listed in the public MCP registry as eu.agrogps/agro-gps. Plant protection product registers of 30 countries, free; plus your farm notebook and finances. This page covers its npm package (agro-gps-mcp).
Is the Agro GPS MCP server safe to use?
Agro GPS scores 73 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 Agro GPS MCP server expose?
Agro GPS exposes 16 tools: search_plant_protection_products, check_plant_protection_product, list_farms, list_entries, entry_history, and 11 more. Their descriptions and schemas cost roughly 1,683 tokens of context every time the server is loaded.
Is the Agro GPS MCP server still maintained?
Agro GPS is still listed as active in the MCP registry. We last reached this channel on 5 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 Agro GPS MCP server under?
Agro GPS declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.