REST API and MCP server

Everything the checker does to a file, a program can do too, and so can an AI assistant.

REST API

• Files: /validate, /fix, /convert, /report (the PDF) and /forest (forest cover in 2020 and tree cover loss since). GeoJSON, KML, KMZ, GPX, CSV and shapefiles. The same rules, fixes and converter as the checker, and the same JSON as the command-line tool's --json.
• Projects: create them from files, save versions, download any version.
• Due diligence statements: file one from a project's current version through your workspace's Information System connection (S17), poll for its reference and verification numbers, withdraw it within 72 hours.
• Documented: an OpenAPI 3.1 description, rendered here, with stable error codes and rate-limit headers.

Files sent to the file endpoints are processed and not stored. The API is in the Consultant plan, with its requests a minute and its monthly allowance of distinct plots, shared with saved projects.

MCP server

The Model Context Protocol lets an assistant such as Claude, Cursor or VS Code use our tools: check a file, explain a finding, apply the fixes, convert a shapefile, measure forest cover, list your projects, prepare a statement.

• Local, free: eudr-check mcp runs on your computer and reads files from one folder you choose. They never leave your computer.
• Hosted, Consultant: the same file tools plus your saved projects and statements, with an API key.

Filing a statement stays a person's decision: an assistant can prepare it, not file it. Set it up.