Home / MCP registry index / io.github.Termi24/eyeot-erp

eyeot ERP

io.github.Termi24/eyeot-erp in the official MCP registry. Endpoint https://erp.eyeot.fr/api/v1/mcp. Source: github.com/Termi24/ERP-by-Eyeot-Software.

The registry describes it as: ERP français avec serveur MCP natif : plus de 1 800 actions métier auto-générées via OpenAPI.

We read its 33 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http eyeot-erp https://erp.eyeot.fr/api/v1/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "eyeot-erp": {
      "url": "https://erp.eyeot.fr/api/v1/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"eyeot-erp","type":"http","url":"https://erp.eyeot.fr/api/v1/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

whoami list_clients create_client get_client update_client list_opportunities create_opportunity convert_opportunity_to_quote list_quotes create_quote accept_quote quote_pdf list_invoices create_invoice invoice_from_quote list_products create_product list_stock_alerts stock_dashboard list_employees create_employee list_leaves request_leave list_tickets create_ticket list_suppliers list_orders create_order dashboard_kpis dashboard_alerts search eyeot_help eyeot_call

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-termi24-eyeot-erp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-termi24-eyeot-erp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.