eyeot ERP
REMOTE · ERP.EYEOT.FR · SCANNED SEP 20
ERP français avec serveur MCP natif : plus de 1 800 actions métier auto-générées via OpenAPI.
Available components
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 Security66
- 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 (eyeot_call). 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 1511 tokens (~39/item across 38 items; 33 tools + 5 resources), lean.Pass
- 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 33 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 35 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
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'
{
"mcpServers": {
"termi24-eyeot-erp": {
"url": "https://erp.eyeot.fr/api/v1/mcp"
}
}
} {
"servers": {
"termi24-eyeot-erp": {
"type": "http",
"url": "https://erp.eyeot.fr/api/v1/mcp"
}
}
} [mcp_servers.termi24-eyeot-erp] url = "https://erp.eyeot.fr/api/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"termi24-eyeot-erp": {
"type": "remote",
"url": "https://erp.eyeot.fr/api/v1/mcp",
"enabled": true
}
}
} openclaw mcp add termi24-eyeot-erp --url 'https://erp.eyeot.fr/api/v1/mcp' --transport streamable-http
mcp_servers:
termi24-eyeot-erp:
url: "https://erp.eyeot.fr/api/v1/mcp" {
"McpServers": {
"termi24-eyeot-erp": {
"Transport": "http",
"Url": "https://erp.eyeot.fr/api/v1/mcp"
}
}
} assistant mcp add termi24-eyeot-erp -t streamable-http -u 'https://erp.eyeot.fr/api/v1/mcp'
{
"mcpServers": {
"termi24-eyeot-erp": {
"type": "http",
"url": "https://erp.eyeot.fr/api/v1/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 +2
- 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
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 27 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
- 26 Jul 26 0
First indexed and scored.
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 20 Sept 2026 · Probed https://erp.eyeot.fr/api/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=erp.eyeot.fr | CN=YE2,O=Let's Encrypt,C=US | 18 Aug 2026 | 16 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5d447bece9def8f987889b2d659e0e1f42c |
| SANs: erp.eyeot.fr | ||||||
| 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 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 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=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'nonce-54XO6PsSzzY-Y_2UnlTWSw' 'strict-dynamic' https://eu-assets.i.posthog.com https://js.stripe.com https://www.googletagmanager.com; style-src 'self' 'unsafe-inline' 'nonce-54XO6PsSzzY-Y_2UnlTWSw' https://fonts.googleapis.com; img-src 'self' data: blob: https://eu.i.posthog.com https://www.googletagmanager.com https://www.google.com https://www.google.fr https://googleads.g.doubleclick.net; font-src 'self' data: https://fonts.gstatic.com; connect-src 'self' https://eu.i.posthog.com https://eu-assets.i.posthog.com https://api.stripe.com https://www.googletagmanager.com https://www.google.com https://www.google.fr https://googleads.g.doubleclick.net https://www.googleadservices.com https://*.analytics.google.com; frame-src 'self' https://js.stripe.com https://hooks.stripe.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(self), payment=(), usb=(), magnetometer=(), gyroscope=(), accelerometer=() |
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 | Verified | 200 | |
| http (plaintext) | http://erp.eyeot.fr/api/v1/mcp | HTTPS enforced | 301 | https://erp.eyeot.fr/api/v1/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 →
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.
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?
No. We connected to eyeot ERP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the eyeot ERP MCP server still maintained?
eyeot ERP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.