eyeot ERP
REMOTE · ERP.EYEOT.FR
ERP français avec serveur MCP natif : plus de 1 800 actions métier auto-générées via OpenAPI.
Available components
Last scanned (1 hour ago)
Scores higher than 79% of remote servers
Unreachable for 2 days in a row. Last reached 3 Nov 2026.
Category CRM and Sales
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 Security14
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Authorization: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 28 Sept 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
- 25 Sept 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
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
- 31 Jul 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
- 30 Jul 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 5 Nov 2026 · Probed https://erp.eyeot.fr/api/v1/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of erp.eyeot.fr. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fr. | present | 65381 | 13 | Verified |
| eyeot.fr. | present | 2774 | 8 | Verified |
| erp.eyeot.fr. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://erp.eyeot.fr/api/v1/mcp | Unreachable | ||
| http (plaintext) | http://erp.eyeot.fr/api/v1/mcp | HTTPS enforced |
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 →
accept_quote ~29
Marquer un devis accepté (par le client)
| Name | Type | Req | Description |
|---|---|---|---|
| quote_id | string | yes | (path parameter) |
No output schema declared.
No examples provided.
convert_opportunity_to_quote ~30
Convertir une opportunité en devis
| Name | Type | Req | Description |
|---|---|---|---|
| opportunity_id | string | yes | (path parameter) |
No output schema declared.
No examples provided.
create_client ~22
Créer un client
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | Request body |
No output schema declared.
No examples provided.
create_employee ~14
Créer un employé
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_invoice ~13
Créer une facture
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_opportunity ~24
Créer une opportunité
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | Request body |
No output schema declared.
No examples provided.
create_order ~24
Créer un bon de commande
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | Request body |
No output schema declared.
No examples provided.
create_product ~26
Créer un produit (catalogue stock)
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | Request body |
No output schema declared.
No examples provided.
create_quote ~22
Créer un devis
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | Request body |
No output schema declared.
No examples provided.
create_ticket ~23
Créer un ticket IT
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | Request body |
No output schema declared.
No examples provided.
dashboard_alerts ~14
Alertes du dashboard
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
dashboard_kpis ~15
KPIs du dashboard principal
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
eyeot_call ~153
Exécute une action eyeot ERP par son nom canonique. Format action : `<module>.<resource>.<verb>` (ex: 'clients.list', 'rh.employes.create', 'quotes.send'). Toujours utiliser eyeot_help d'abord pour connaître l'action + les params attendus. Les params path (ex: id) et le body JSON sont passés dans `params`.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Nom canonique de l'action (ex: 'rh.employes.create'). |
| params | object | – | Tous les paramètres mélangés : path params (id, ...), query params (limit, cursor, ...) et body fields. Le serveur route automatiquement selon la spec OpenAPI. |
No output schema declared.
No examples provided.
eyeot_help ~192
Catalog des actions disponibles sur eyeot ERP. Sans argument : liste les modules et compteur d'actions. Avec `module='rh'` : liste toutes les actions RH (employes, conges, paie, formations…). Avec `action='rh.employes.create'` : retourne le détail (path, méthode, params, schema body). Avec `search='facture'` : recherche les actions matchant. Toujours appeler eyeot_help AVANT eyeot_call pour découvrir l'action exacte.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Action exacte au format `<module>.<resource>.<verb>` (ex: 'rh.employes.create'). Retourne le schéma complet. |
| module | string | – | Nom du module (ex: 'rh', 'finance', 'clients'). Optionnel. |
| search | string | – | Recherche textuelle dans les noms d'action et descriptions. Optionnel. |
No output schema declared.
No examples provided.
get_client ~28
Récupérer un client par id
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | yes | (path parameter) |
No output schema declared.
No examples provided.
invoice_from_quote ~30
Créer une facture à partir d'un devis
| Name | Type | Req | Description |
|---|---|---|---|
| quote_id | string | yes | (path parameter) |
No output schema declared.
No examples provided.
list_clients ~15
Lister les clients (CRM)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_employees ~14
Lister les employés
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_invoices ~15
Lister les factures
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_leaves ~17
Lister les demandes de congés
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_opportunities ~16
Lister les opportunités commerciales
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_orders ~15
Lister les bons de commande
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_products ~15
Lister les produits / catalogue
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_quotes ~13
Lister les devis
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_stock_alerts ~17
Alertes stock bas / rupture
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_suppliers ~14
Lister les fournisseurs
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_tickets ~15
Lister les tickets IT
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
quote_pdf ~29
Récupérer le PDF d'un devis
| Name | Type | Req | Description |
|---|---|---|---|
| quote_id | string | yes | (path parameter) |
No output schema declared.
No examples provided.
request_leave ~23
Demander un congé
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | Request body |
No output schema declared.
No examples provided.
search ~12
Recherche globale cross-module
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
stock_dashboard ~14
Dashboard stock (KPIs)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
update_client ~35
Mettre à jour un client
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | Request body |
| client_id | string | yes | (path parameter) |
No output schema declared.
No examples provided.
whoami ~41
Récupérer l'utilisateur authentifié + organisation active + permissions. À APPELER AVANT toute réponse mentionnant l'org/user/plan/role.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the eyeot ERP MCP server?
eyeot ERP is a hosted endpoint at https://erp.eyeot.fr/api/v1/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 · erp.eyeot.fr
claude mcp add --transport http termi24-eyeot-erp 'https://erp.eyeot.fr/api/v1/mcp'
What is the eyeot ERP MCP server?
eyeot ERP is an MCP server listed in the public MCP registry as io.github.Termi24/eyeot-erp. ERP français avec serveur MCP natif : plus de 1 800 actions métier auto-générées via OpenAPI. This page covers its hosted endpoint (https://erp.eyeot.fr/api/v1/mcp).
Is the eyeot ERP MCP server safe to use?
eyeot ERP scores 79 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 eyeot ERP MCP server expose?
eyeot ERP exposes 33 tools: whoami, list_clients, create_client, get_client, update_client, and 28 more. Their descriptions and schemas cost roughly 979 tokens of context every time the server is loaded.
Does the eyeot ERP MCP server require authentication?
Its publisher declares no required credentials for eyeot ERP. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the eyeot ERP MCP server still maintained?
eyeot ERP is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.