Home / MCP registry index / app.eini/eini

EINI

app.eini/eini in the official MCP registry. Endpoint https://api.eini.app/mcp.

The registry describes it as: Swiss supermarket deals at 8 chains and official 2027 health insurance premiums, from EINI.

We read its 5 tools on 2026-10-22. 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.

Tools it advertises

eini_search_deals eini_compare_health_insurance eini_my_meal_plan eini_my_shopping_list eini_create_meal_plan

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/app-eini-eini/badge.svg)](https://lazaretto.dev/mcp-registry/app-eini-eini)

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.