French pesticide register (Anses E-Phy): still sellable or usable, and until when.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Free sample: real output computed while a product was in its grace period. Same shape as phyto_lookup.
This tool takes no arguments.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http sentinelle-phyto https://phyto.amacunia.fr/mcp
Free sample: real output computed while a product was in its grace period. Same shape as phyto_lookup.
No arguments.
{
"type": "object",
"title": "phyto_exampleArguments",
"properties": {}
}France pesticide authorisation and grace-period deadlines. For 1 to 20 plant protection products (AMM number or trade name, optional crop filter): is it still authorised, can it still be sold, can existing stocks still be used, and until which date, use by use, from the official Anses E-Phy register (grace period, art. 46 Reg. 1107/2009). For farm suppliers, co-ops, advisers, growers, landscapers, traceability software. Price: 0.01 USDC per call (x402).
| Argument | Type | Description |
|---|---|---|
| date | string | |
| culture | string | |
| produits* | string |
{
"type": "object",
"title": "phyto_lookupArguments",
"required": [
"produits"
],
"properties": {
"date": {
"type": "string",
"title": "Date",
"default": ""
},
"culture": {
"type": "string",
"title": "Culture",
"default": ""
},
"produits": {
"type": "string",
"title": "Produits"
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 10, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.