io.github.Vortx-AI/eudr
REMOTE · EUDR.DEV
Compile EUDR Annex II Due Diligence Statements from operator, supplier, and plot geolocation.
Available components
Last scanned (15 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
Recent critical change
Authorization (1 Oct 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (eudr_prepare_dds). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4476 tokens (~213/item across 21 items; 21 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 0
- “eudr_check_plots” added an optional parameter “area_ha” cosmetic
- “eudr_lookup_reference” added an optional parameter “hs_code” cosmetic
- “eudr_lookup_reference” reworded the description of “kind” cosmetic
3 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 16 Nov 26 0
- “eudr_check_plots” added an optional parameter “scope_evidence” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 15 Nov 26 0
- Tool “eudr_check_plots” rewrote its description, which is the text the model reads security
- Tool “eudr_export_statement” rewrote its description, which is the text the model reads security
- Tool “eudr_prepare_dds” rewrote its description, which is the text the model reads security
- “eudr_lookup_reference” added an optional parameter “cursor” cosmetic
- “eudr_lookup_reference” added an optional parameter “limit” cosmetic
- “eudr_check_plots” reworded the description of “hs_code” cosmetic
- “eudr_check_plots” reworded the description of “quantity_kg” cosmetic
- “eudr_lookup_reference” reworded the description of “country” cosmetic
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 8 Nov 26 0
- Stability: 0.97 → pass security
- 7 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 21 Nov 2026 · Probed https://eudr.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=eudr.dev | CN=YE2,O=Let's Encrypt,C=US | 13 Nov 2026 | 11 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6b60b2ab921434700933bfd05b338112a16 |
| SANs: eudr.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of eudr.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| eudr.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' https://www.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://www.google-analytics.com; font-src 'self' data:; connect-src 'self' https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com; frame-src 'self'; frame-ancestors 'none'; base-uri 'none'; form-action 'self'; object-src 'none'; report-uri /csp-report; report-to csp-endpoint |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), autoplay=(), bluetooth=(), browsing-topics=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(self), geolocation=(), gyroscope=(), hid=(), interest-cohort=(), magnetometer=(), microphone=(), midi=(), payment=(self), publickey-credentials-get=(), screen-wake-lock=(), serial=(), sync-xhr=(self), usb=(), xr-spatial-tracking=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://eudr.dev/mcp | Verified | 200 | |
| http (plaintext) | http://eudr.dev/mcp | HTTPS enforced | 308 | https://eudr.dev/mcp |
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 →
eudr_account_usage Wallet balance and what it covers ~115
Report this organisation's credit balance, how many signed statements it will cover, and what has been spent. Checking plots, looking up references, assessing supplier gaps and reading traces cost nothing and are always available — only compiling a signed statement draws the balance down. Use this before starting a batch of compiles so the user is not surprised part-way through. The first call for an organisation writes: it opens the wallet, grants the welcome credits and records that grant as the opening ledger line. Every call after that only reads.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| analyses_remaining | integer | yes | – |
| balance_credits | integer | yes | – |
| charged_unit | string | yes | – |
| credits_per_analysis | integer | yes | – |
| credits_per_extra_plot | integer | – | Added for each plot after the first, from per_plot_pricing_from. |
| credits_received | integer | – | – |
| credits_spent | integer | – | – |
| free_of_charge | array | yes | – |
| note | string | – | – |
| organisation | string | yes | – |
| per_plot_pricing_from | string | – | – |
| recent_activity | array | – | – |
| welcome_credits_granted_at | string|null | – | – |
No examples provided.
eudr_assess_evidence_gaps Find missing Article 9 information per supplier ~127
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 filing. Returns the unmet items with their article reference and what to request, separating items that block filing from items that merely leave the file incomplete. This is a checklist over the fields you supply; it reads no documents and judges no evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| suppliers | array | yes | The suppliers to weigh up, each with what is already held about them. One entry per supplier. |
| Name | Type | Req | Description |
|---|---|---|---|
| basis | string | yes | – |
| blocked_from_filing | integer | yes | – |
| checked | integer | yes | – |
| incomplete | integer | yes | – |
| scope_note | string | yes | – |
| summary | string | yes | – |
| suppliers | array | yes | One row per supplier: status, gaps with their article limb and the request to send, blocking_gaps, held limbs, evidence_references (each deforestation evidence entry and whether it counted), legality… |
No examples provided.
eudr_check_plots Check plots for forest loss after the EUDR cut-off ~659
Check up to six production plots for forest loss after 31 December 2020, the cut-off in Regulation (EU) 2023/1115. This is the tool for the question "is this plot deforestation-free". It needs only the GeoJSON boundaries, the commodity and the country of production: leave hs_code and quantity_kg out, and never make one up. Returns a per-plot verdict, the loss years observed, how much of each plot was inspected, and a handle for the underlying satellite evidence. This answers Article 3(a) only: it does not check land tenure, permits, consent, or chain of custody, and it lists those gaps on every response. This has side effects, though it writes nothing to the organisation's records and costs no credits: every call asks emem.dev to make freshly signed measurements, so repeating a check returns the same finding under new signatures, and mints a short-lived evidence handle held on this server for 24 hours, which eudr_fetch_evidence resolves and which a later check will not reproduce.
| Name | Type | Req | Description |
|---|---|---|---|
| area_ha | number | – | The plot's area in hectares, when `geojson` is a Point. Without it a clean Point reads `indeterminate`, because nothing says the plot is 4 ha or less; over 4 ha the Point is refused and the outline i… |
| commodity | string | yes | With kind=trade, return just this Annex I commodity's lanes: cocoa, coffee, rubber, soya, oil_palm, cattle or wood. |
| country | string | yes | ISO-3166-1 alpha-2 code of the country of production. It sets the benchmark risk tier. |
| geojson | object | – | One plot, as a GeoJSON Polygon, MultiPolygon or Point in WGS84 (EPSG:4326). Article 2(28) requires six decimal places. A Point is admissible only for a plot under four hectares that is not forest. Su… |
| hs_code | string | – | Optional HS code, 2 to 8 digits. Leave it out for a forest-loss check: the commodity sets the code. Give it only when you know the real code of the product; a code of another commodity, or of a produ… |
| plots | array | – | Several plots checked together, each keeping its own verdict. Use this when a consignment draws on more than one plot. Six at a time answers inside a conversation; a consignment with more plots than… |
| quantity_kg | number | – | Optional net mass of the consignment. Leave it out for a forest-loss check: it does not change the verdict. |
| scope_evidence | object | – | Optional. For an HS code on an "ex" Annex I row (live cattle, palm oil, most wood and rubber) or wider than its row: the document that shows the product is, or is not, what the row describes. Without… |
| Name | Type | Req | Description |
|---|---|---|---|
| annex_i_scope | object | – | The product's place in Annex I, decided as the statement compile decides it. needs_product_evidence means the land was checked and the product was not: the HS code meets an "ex" row or is wider than… |
| country_risk_tier | string | – | – |
| coverage | object | yes | – |
| cut_off_date | string | yes | – |
| deforestation_free | boolean|null | yes | true when the land measured clean, false when post-cut-off loss was found, and null when the question was not settled — nothing measured, or a commodity Annex I does not cover. Null is not false: it… |
| engine | string | yes | – |
| evidence | object | yes | fact_count is always present. It is a count of facts that exist, not of facts shipped: the conversational surface carries the address rather than the list. |
| finding | string | yes | – |
| next_action | string | yes | – |
| observed | object | yes | – |
| per_plot | array | yes | One row per plot, as /v1/spatial/verify returns it, except that emem's fixed texts `verdict_support.rule` (how support is graded), `verdict_support.baseline_map.note` and `tmf_cross_check.in_verdict_… |
| plots_not_checked | array | – | Plots that were not measured: they ran out of time, or they are in plots_refused. Present only when some were. When it is non-empty the verdict is indeterminate by construction, whatever the plots th… |
| plots_refused | array | – | Plots refused before anything was measured because of their outline or their place (a self-intersecting ring, longitude and latitude swapped, a plot in another country), each with its own reason. The… |
| risk_score | number|null | – | Composite risk from 0 to 1: the WORST plot's failing-cell fraction (emem's per-plot `fail_fraction`: that plot's `cells_with_post_cutoff_loss` / `cells_evaluated`, never cells pooled across plots) ×… |
| scope_note | string | yes | – |
| unresolved_checks | array | yes | – |
| verdict | string | yes | Keep only statements that reached this verdict. Leave it out for all of them. |
| why_not_checked | object | – | Why the plots in plots_not_checked that ran out of time were not measured, and the order to send them in. Present only when some did; a plot in plots_refused is not in send_next. Branch on `reason`:… |
No examples provided.
eudr_compliance_status Summarise where this organisation stands ~72
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, broken down by commodity and country, plus outstanding supplier evidence requests. Answers "where do we stand" without enumerating every record.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| by_commodity | array | yes | – |
| by_country | array | yes | – |
| next_action | string | yes | – |
| organisation | string | yes | – |
| scope_note | string | yes | – |
| supplier_requests | object | yes | – |
| totals | object | yes | – |
No examples provided.
eudr_create_farm Add a farm, with its boundary if known ~382
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 Polygon or MultiPolygon, longitude first), or as `fields`: several field outlines (for example Fields of The World parcels) that are joined into one farm by closing the bunds and tracks between neighbours (`join_m`, default 3 m each way), fields farther apart kept as separate pieces. With a boundary, what follows runs at once: the country from where the land lies when none is given, the forest record warmed, and the land check when the crop is one the EU regulation covers. With only a pin, the mapped fields around it are looked up as suggestions for a person to accept. This writes to the organisation's record.
| Name | Type | Req | Description |
|---|---|---|---|
| boundary | object | – | GeoJSON Polygon or MultiPolygon. |
| country | string | – | ISO 3166-1 alpha-2. |
| crop | string | – | What grows there, in plain words (`cocoa`, `coffee`, `oil palm`). It decides whether the EU deforestation rules apply at all. |
| fields | array | – | GeoJSON Polygons to join into one farm. |
| join_m | number | – | How far apart two field outlines may be and still be treated as one farm, in metres each way. Default 3, which closes the bunds and tracks between neighbouring parcels. |
| lat | number | – | A pin on the farm, in WGS84 degrees. Use it when no boundary is known. |
| lon | number | – | The pin's longitude, WGS84 degrees. GeoJSON order is longitude first; this field is not. |
| name | string | yes | What the farm is called, as the buyer and the farmer would say it. |
| Name | Type | Req | Description |
|---|---|---|---|
| boundary | object|null | – | – |
| farm_id | string | yes | – |
| farm_url | string | yes | – |
| next_action | string | – | – |
| then | – | – | – |
No examples provided.
eudr_decide_lot Decide whether to buy a banana lot, where to sell it, and up to what price ~270
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 / NO-GO with the chance the whole chain holds, the margin P10/P50/P90, the most the buyer can pay and keep that outcome, the deal zone against the farmer's ask, and what the farmer is told (never the walk-away price). Every default the lot needed is returned as a stated assumption. Banana only; other crops are refused by name. The run is stored as a decision the organisation can later record an outcome against. Send `lot` in the shape of `lot_example` from eudr_procurement_overview. The crop is taken from the farm's own record.
| Name | Type | Req | Description |
|---|---|---|---|
| farm_id | string | yes | A farm id from eudr_procurement_overview. |
| lot | object | yes | The lot: crop, plants, harvestable_share, bunch_kg, maturity, days_since_flowering, expected_daily_mean_c (each a {low, mid, high} range where a range), fingers, chemicals, certificates, offer {farm_… |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | array | yes | – |
| decision_id | string | yes | – |
| decisions | array | yes | – |
| farmer_view | object | – | – |
| process_version | integer | – | – |
| readouts | array | – | – |
| recommended | string|null | – | – |
| rules_in_force | array | – | – |
No examples provided.
eudr_execution_trace Show how a verdict was reached, step by step ~112
The complete derivation chain behind a compiled statement, in order: polygon to grid addresses, signed measurements, the algorithm and the registries it was pinned against, cell verdicts to a consignment verdict, citations, and which of three independent keys signed what. A stage whose evidence is absent is reported as absent with its reason. Use it when someone asks how a result was reached rather than what it was.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | The task_id of a compile that has produced a statement. |
| Name | Type | Req | Description |
|---|---|---|---|
| full_statement | string | – | – |
| generated_at | string | – | – |
| not_established | array | yes | – |
| schema | string | yes | – |
| signing_parties | object | yes | – |
| steps | array | yes | A step either ran (stage, what, consumed, produced, signed_by, reproduce) or did not, in which case it carries present:false and why_absent. An absent stage is emitted, never omitted. |
| task_id | string | yes | – |
| verdict | string|null | – | – |
| verify | string | – | – |
No examples provided.
eudr_export_statement Export a finished statement in the shape another system wants ~169
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 any authority. TRACES export is refused for a non-negligible verdict, because Article 4(4) bars placing those goods and a non-filable assessment must not be handed out as a submission document.
| Name | Type | Req | Description |
|---|---|---|---|
| activity | string | – | TRACES activity type. Defaults to the activity the statement was compiled with. |
| format | string | yes | `traces_xml` for the EUDR Information System submission shape, `annex_ii_json` for the signed statement, `plots_geojson` for the boundaries as a FeatureCollection. |
| task_id | string | yes | The task_id of a completed compile. |
| Name | Type | Req | Description |
|---|---|---|---|
| activity | string | – | – |
| dds_reference | string|null | – | – |
| document | – | yes | The exported document. A string for traces_xml, an object for the other two. |
| download_url | string | – | – |
| filed_with_any_authority | boolean | – | – |
| format | string | yes | – |
| next_action | string | – | – |
| receipt_cid | string|null | – | – |
| signer_pubkey_b32 | string | – | – |
| task_id | string | yes | – |
| verify_at | string | – | – |
No examples provided.
eudr_fetch_evidence Page the signed facts behind a check ~137
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 that resolves at emem.dev and verifies offline against the responder's key. Use this when someone needs to audit or cite the evidence, not to summarise a result.
| Name | Type | Req | Description |
|---|---|---|---|
| evidence_cid | string | yes | The handle returned by eudr_check_plots. |
| limit | integer | – | How many facts to return, up to 200. Defaults to 50. |
| offset | integer | – | Index to start from. Defaults to 0. |
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string|null | – | – |
| evidence_cid | string | yes | – |
| fact_cids | array | yes | – |
| minted_at | string | – | – |
| next_offset | integer|null | – | – |
| note | string | – | – |
| offset | integer | yes | – |
| resolve_one_at | string | – | – |
| responder_pubkey_b32 | string|null | – | – |
| returned | integer | yes | – |
| total | integer | yes | – |
| verify_at | string | – | – |
No examples provided.
eudr_get_dds Read the outcome of a statement compile ~90
Read the state of a compile started by eudr_prepare_dds. While it runs, returns the current state. Once finished, returns the verdict and the receipt's content address and signing key. The printable statement opens from the `report_url` that eudr_prepare_dds returned.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | The task_id returned by eudr_prepare_dds. |
| Name | Type | Req | Description |
|---|---|---|---|
| erased | boolean | – | – |
| error | string|null | – | – |
| next_action | string | – | – |
| note | string | – | – |
| receipt_cid | string|null | – | – |
| report_access | string | – | – |
| report_url | string | – | – |
| settled | boolean | – | – |
| signer_pubkey_b32 | string | – | – |
| state | string | yes | – |
| task_id | string | yes | – |
| verdict | string|null | – | – |
| verify_at | string | – | – |
No examples provided.
eudr_import_shipments Read shipments out of a spreadsheet or GS1 event feed ~220
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. Returns one row per shipment with supplier, commodity, country, quantity and plot boundaries, plus a warning for every row that could not be read and the reason. Nothing is stored and nothing is submitted; this only reads the document you pass.
| Name | Type | Req | Description |
|---|---|---|---|
| document | string | yes | The document itself. CSV text including its header row, or the EPCIS document as JSON text. |
| format | string | yes | `csv` for the published column set, `epcis` for a GS1 EPCIS 2.0 JSON-LD document. |
| limit | integer | – | How many shipments to return in full, including plot boundaries. Defaults to 8, which is what eudr_check_plots accepts in one call. |
| offset | integer | – | Which shipment to start detailing from. Totals always cover the whole document. |
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | yes | – |
| next_action | string | yes | – |
| next_offset | integer|null | – | – |
| note | string | yes | – |
| offset | integer | yes | – |
| rows_returned | integer | yes | – |
| rows_skipped | integer | yes | – |
| shipments | array | yes | – |
| shipments_read | integer | yes | – |
| stored | boolean | yes | – |
| warnings | array | yes | – |
No examples provided.
eudr_list_farms List this organisation's farms ~58
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 statements were made for each. Read-only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| farms | array | yes | – |
No examples provided.
eudr_list_statements List the statements this organisation has compiled ~132
List the Due Diligence Statements already in the signed-in organisation's account, newest first, with verdict, reference, commodity, country, quantity and date. Use this to answer what has been filed, what is outstanding, and what a past consignment concluded, rather than asking the user to re-enter details their account already holds.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Only statements for this country of production. |
| limit | integer | – | How many to return. Defaults to 20. |
| verdict | string | – | Keep only the statements that reached this verdict. Leave it out for all of them. |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | – |
| organisation | string | yes | – |
| returned | integer | yes | – |
| statements | array | yes | – |
No examples provided.
eudr_list_supplier_requests List outstanding supplier evidence requests ~47
List the supplier evidence requests this organisation has issued: who was asked, whether they responded, and when each request expires. Answers which suppliers still owe plot boundaries and production details.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | – |
| organisation | string | yes | – |
| pending | integer | yes | – |
| requests | array | yes | – |
| submitted | integer | yes | – |
No examples provided.
eudr_lookup_reference Look up country risk, Annex I commodities, ports and trade lanes ~397
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 seaports and airports a consignment can leave or enter through (UN/LOCODE), or which countries actually supply the Union with each commodity and in what volume (UN Comtrade 2023, with World Bank indicator prices). Returns the table this engine evaluates against, with its source and the date it was verified.
| Name | Type | Req | Description |
|---|---|---|---|
| commodity | string | – | With kind=trade, return just this Annex I commodity's import lanes instead of all seven. |
| country | string | – | A country as an ISO 3166-1 alpha-2 code (`BR`), an alpha-3 code (`BRA`) or its English name (`Brazil`). Text that is not one country is refused, with the names it was near. With kind=country_risk, re… |
| cursor | string | – | With kind=ports, the `next_cursor` of the previous page. Omit it for the first page. |
| hs_code | string | – | With kind=commodities, also return `scope` for this HS code (2 to 8 digits): in_scope, out_of_scope or needs_product_evidence, with the Annex I row it falls under and that row's clause. |
| kind | string | yes | `country_risk` for the benchmark tiers, `commodities` for the Annex I codes the engine evaluates against, `ports` for UN/LOCODE seaports and airports, `trade` for who supplies the Union with what. |
| limit | integer | – | With kind=ports, how many locations to return in one page. |
| Name | Type | Req | Description |
|---|---|---|---|
| basis | string | – | – |
| commodities | array | – | – |
| count | integer | – | – |
| country | string | – | – |
| high_risk | array | – | – |
| kind | string | yes | – |
| low_risk | array | – | – |
| next_cursor | string|null | – | – |
| note | string | – | – |
| reference | object | – | – |
| scope | object | – | – |
| simplified_due_diligence_available | boolean | – | True when the country is low risk, which is one condition of Art. 13(1). The operator must also have assessed the supply chain, the risk of circumvention and the risk of mixing with products of unkno… |
| simplified_due_diligence_condition | string | – | – |
| tier | string | – | – |
| total | integer | – | – |
| truncated | boolean | – | – |
No examples provided.
eudr_mitigation_status Article 11 mitigation: what is outstanding ~192
Report the Article 11 risk-mitigation plans this organisation has open against flagged shipments: which steps are outstanding, which article each discharges, whether a step needs a person or can be re-run automatically, and what evidence has been recorded. A non-negligible verdict creates an obligation under Article 11 to act before the product is placed on the market; this answers how far that has got. Pass a shipment id for one plan, or omit it for everything still open. Read-only — recording a decision is a deliberate human act and is done on eudr.dev, because Article 11(3) requires mitigation decisions to be documented and demonstrable; eudr.dev records each against the named person who made it, which is our choice rather than the Regulation's wording.
| Name | Type | Req | Description |
|---|---|---|---|
| shipment_id | string | – | Optional. One shipment's plan; omit for every open plan. |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | yes | – |
| open_plans | integer | yes | – |
| organisation | string | yes | – |
| outstanding_steps | integer | – | – |
| plans | array | yes | – |
No examples provided.
eudr_prepare_dds Start preparing a Due Diligence Statement ~392
Compile and sign an Annex II Due Diligence Statement. For a yes or no answer about forest loss on a plot, use eudr_check_plots instead: it needs no HS code and no quantity, and it is free. This WRITES: it stores a compile task holding the operator and supplier details you pass, and sends the plot geometry, HS code, country and quantity to emem.dev to be measured and independently signed. Operator and supplier identity are not forwarded upstream. Returns a task handle; read the outcome with eudr_get_dds. For an organisation's statement it also makes one revocable share link, valid for 7 days, so `report_url` opens in a browser that is not signed in to eudr.dev; the organisation can withdraw it from its account. Nothing is filed with any authority. Confirm the details with the user first. Costs 5 credits from the organisation's wallet (from 30 October 2026, plus 1 for each plot after the first), refunded automatically if the compile fails; every other tool here is free.
| Name | Type | Req | Description |
|---|---|---|---|
| geolocation | object | yes | Where it was produced and when it was harvested (Annex II point 3). The plot geometry, country, HS code and quantity are the only things sent to the satellite service. |
| operator | object | yes | Who places the goods on the EU market and answers for this statement (Annex II point 1). Not forwarded to the satellite service. |
| producer | object | – | The primary producer, where that is not the supplier. |
| product | object | yes | What is being placed on the market: its HS code, what it is in words, and its net mass (Annex II point 2). |
| supplier | object | yes | Who the goods were bought from, as the operator's own records name them. Not forwarded to the satellite service. |
| Name | Type | Req | Description |
|---|---|---|---|
| data_sent_upstream | string | yes | – |
| data_stored_here | string | yes | – |
| filed_with_any_authority | boolean | yes | – |
| next_action | string | yes | – |
| read_outcome_with | string | yes | – |
| report_link_expires_at | string|null | – | – |
| report_url | string|null | yes | – |
| state | string|null | – | – |
| task_id | string | yes | – |
No examples provided.
eudr_procurement_overview Buying decisions across this organisation's farms ~80
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 outcome and which were overridden. Use it to find a farm id before eudr_decide_lot, or to see how decisions have turned out. Read-only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| counts | object | yes | – |
| decisions | array | yes | – |
| farms | array | yes | – |
| lot_example | object | yes | – |
No examples provided.
eudr_request_supplier_evidence Ask a supplier for their plot evidence ~158
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 account of their own. This writes: it creates a credential that lets whoever holds the link submit data to you, and returns that link once. Send it only to the intended supplier. No email is sent by this call.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Optional, recorded so you can see where the link was meant to go. It is not verified and nothing is sent to it. | |
| supplier_name | string | yes | Your name for the counterparty, shown to them on the intake page. |
| valid_for_days | integer | – | How long the link works. Defaults to 30. |
| Name | Type | Req | Description |
|---|---|---|---|
| emailed | boolean | yes | – |
| expires_at | string | yes | – |
| intake_url | string | yes | – |
| next_action | string | yes | – |
| note | string | – | – |
| request_id | string | yes | – |
| shown_once | boolean | yes | – |
| supplier | string | yes | – |
No examples provided.
eudr_set_farm_boundary Set a farm's boundary ~307
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). It becomes the farm's confirmed boundary, recorded as set by this agent credential, and what follows runs at once: the country from where the land lies, the forest record warmed, the land check. This writes to the organisation's record, and REPLACES any boundary the farm already had: the previous outline stops being the farm's boundary, and because the boundary decides which land is checked, the compliance answers and the area derived from it change with it. The superseded outline is kept in the farm's history and can be read back, but this call does not undo on its own — confirm with the user before overwriting a boundary somebody else set.
| Name | Type | Req | Description |
|---|---|---|---|
| boundary | object | – | The outline, as a GeoJSON Polygon or MultiPolygon, longitude first. Give this or `fields`. |
| farm_id | string | yes | The farm whose boundary this is, as `eudr_create_farm` or `eudr_list_farms` returned it. |
| fields | array | – | Several field outlines to join into one farm, as GeoJSON Polygons. Give this or `boundary`. |
| join_m | number | – | How far apart two field outlines may be and still count as one farm, in metres each way. Default 3. |
| Name | Type | Req | Description |
|---|---|---|---|
| area_ha | number | yes | – |
| farm_id | string | yes | – |
| then | – | – | – |
No examples provided.
eudr_verify_receipt Verify a signed statement receipt ~100
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 you. A valid signature establishes who signed and that the bytes are unchanged; it does not establish that the claim inside is true.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | object | yes | The receipt as issued: schema, cid, payload, canonical_b64, signature_b64, signer, signed_at. |
| Name | Type | Req | Description |
|---|---|---|---|
| cid | string|null | – | – |
| note | string | yes | – |
| reason | string | – | – |
| signed_at | string|null | – | The receipt's own field, outside the signature. Not verified. |
| signed_time | string|null | – | The time inside the signed bytes. This is the time to report. |
| signer | string|null | – | – |
| valid | boolean | yes | – |
No examples provided.
How do I install the io.github.Vortx-AI/eudr MCP server?
io.github.Vortx-AI/eudr is a hosted endpoint at https://eudr.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · eudr.dev
claude mcp add --transport http vortx-ai-eudr 'https://eudr.dev/mcp'
What is the io.github.Vortx-AI/eudr MCP server?
io.github.Vortx-AI/eudr is an MCP server listed in the public MCP registry as io.github.Vortx-AI/eudr. Compile EUDR Annex II Due Diligence Statements from operator, supplier, and plot geolocation. This page covers its hosted endpoint (https://eudr.dev/mcp).
Is the io.github.Vortx-AI/eudr MCP server safe to use?
io.github.Vortx-AI/eudr scores 81 out of 100 on VerifyMCP. 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 io.github.Vortx-AI/eudr MCP server expose?
io.github.Vortx-AI/eudr exposes 21 tools: eudr_check_plots, eudr_fetch_evidence, eudr_assess_evidence_gaps, eudr_lookup_reference, eudr_verify_receipt, and 16 more. Their descriptions and schemas cost roughly 4,216 tokens of context every time the server is loaded.
Does the io.github.Vortx-AI/eudr MCP server require authentication?
No. We connected to io.github.Vortx-AI/eudr without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.Vortx-AI/eudr MCP server still maintained?
io.github.Vortx-AI/eudr is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.Vortx-AI/eudr MCP server?
VerifyMCP ran 13 checks on io.github.Vortx-AI/eudr, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.