Remote MCP · Endpoint

EINI MCP server

No. EINI answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://api.eini.app/mcp

The last check completed an MCP handshake.

Registry name
app.eini/eini
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
166 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Swiss supermarket deals at 8 chains and official 2027 health insurance premiums, from EINI.
Listing
From the official MCP registry (active).
Recent checks of EINI
CheckedResultHandshake
34 minutes agoHandshake completed166 ms
9 days agoHandshake completed190 ms
10 days agoHandshake completed200 ms
11 days agoHandshake completed240 ms
12 days agoHandshake completed158 ms
14 days agoHandshake completed177 ms
14 days agoHandshake completed166 ms
15 days agoHandshake completed179 ms
17 days agoHandshake completed347 ms
19 days agoHandshake completed430 ms
21 days agoHandshake completed1.97 s
24 days agoHandshake completed226 ms
26 days agoHandshake completed215 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with EINI and makes no claim about it beyond what these checks measured.