# Vortx Ai Eudr MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.vortx-ai%2Feudr
Registry id: `mcp-registry/io.github.vortx-ai/eudr`
Status: live (checked 2026-10-27T03:38:15.329Z)

## Verdict

Vortx Ai Eudr MCP server answered 100% of Glimind's liveness checks over 30 days, better than 42% of MCP servers, with 1009 ms median handshake and 8 outages in 90 days. Its agent-readiness grade is A (97/100) across 21 tools, costing an agent about 6,578 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 100% | 42% of MCP servers |
| Median handshake latency | 1009 ms | 20% of MCP servers |
| p95 handshake latency | 3267 ms | — |
| Checks in 30 days | 4,947 | — |
| Outages, 90 days | 8 | — |
| Median recovery | 13 min | — |
| Agent-readiness score | 97/100 (A) | 91% of MCP servers |
| Tools | 21 | — |
| Tool-list size for an agent | ~6,578 tokens | 35% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "vortx-ai-eudr-mcp-server": {
      "type": "http",
      "url": "https://eudr.dev/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http vortx-ai-eudr-mcp-server https://eudr.dev/mcp
```

## Tools (21)

- `eudr_account_usage`: Report this organisation's credit balance, how many signed statements it will cover, and what has been spent. Checking plots, looking up references, assessing s
- `eudr_assess_evidence_gaps`: Check what each supplier's file is still missing against Article 9(1) of Regulation (EU) 2023/1115, the closed list of information an operator must hold before 
- `eudr_check_plots`: Check up to six production plots for forest loss after 31 December 2020, the cut-off in Regulation (EU) 2023/1115. Takes GeoJSON boundaries, the commodity, and 
- `eudr_compliance_status`: Summarise the signed-in organisation's position: how many statements are filable, how many are blocked by a non-negligible verdict, how many are unresolved, bro
- `eudr_create_farm`: Add a farm to this organisation's record. A name is enough; give the crop, country and a pin (lat, lon) when known. Give its boundary as `boundary` (a GeoJSON P
- `eudr_decide_lot`: Run the organisation's own buying process on a banana lot from one of its farms: every destination in its library gets GO / GO WITH CONDITIONS / NEEDS A PERSON 
- `eudr_execution_trace`: The complete derivation chain behind a compiled statement, in order: polygon to grid addresses, signed measurements, the algorithm and the registries it was pin
- `eudr_export_statement`: Export a compiled statement as TRACES NT submission XML, signed Annex II JSON, or plot boundaries as GeoJSON. Exporting is not filing: nothing is submitted to a
- `eudr_fetch_evidence`: Retrieve the signed satellite facts behind a completed check, a page at a time, using the `evidence_cid` that check returned. Each entry is a content address th
- `eudr_get_dds`: Read the state of a compile started by eudr_prepare_dds. While it runs, returns the current state. Once finished, returns the verdict, the receipt's content add
- `eudr_import_shipments`: Parse a consignment list into structured shipments ready to check. Accepts a CSV export (the column set eudr.dev publishes) or a GS1 EPCIS 2.0 JSON-LD document.
- `eudr_list_farms`: List the farms in this organisation's record: id, name, country, whether a boundary is confirmed and its area in hectares (geodesic, holes out), and how many EU
- `eudr_list_statements`: List the Due Diligence Statements already in the signed-in organisation's account, newest first, with verdict, reference, commodity, country, quantity and date.
- `eudr_list_supplier_requests`: List the supplier evidence requests this organisation has issued: who was asked, whether they responded, and when each request expires. Answers which suppliers 
- `eudr_lookup_reference`: Look up the country benchmark tier under Implementing Regulation (EU) 2025/1093, the Annex I commodity to HS-code mapping under Regulation (EU) 2023/1115, the s
- `eudr_mitigation_status`: Report the Article 11 risk-mitigation plans this organisation has open against flagged shipments: which steps are outstanding, which article each discharges, wh
- `eudr_prepare_dds`: Compile and sign an Annex II Due Diligence Statement. This WRITES: it stores a compile task holding the operator and supplier details you pass, and sends the pl
- `eudr_procurement_overview`: List the organisation's farms and its recent buying decisions (GO / GO WITH CONDITIONS / NEEDS A PERSON / NO-GO per destination), with which carry a recorded ou
- `eudr_request_supplier_evidence`: Create a one-time link a supplier can use to submit their plot boundaries and production details straight into this organisation's account, without needing an a
- `eudr_set_farm_boundary`: Set the boundary of a farm already in the record, as `boundary` (GeoJSON Polygon or MultiPolygon) or as `fields` to join into one farm (see eudr_create_farm). I
- `eudr_verify_receipt`: Verify a statement receipt: re-derive its content address from the canonical payload and check the ed25519 signature. Use it on a receipt a counterparty hands y

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.