Remote MCP · Endpoint

E2LLM MCP server

No. E2LLM answered an MCP handshake 1 hour ago.

Up · key neededLast checked 1 hour ago

Server URL

https://api.e2llm.com/mcp

The handshake completes, but listing its tools needs credentials.

Registry name
com.e2llm/element-to-llm
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
344 ms
Tools exposed
Behind credentials
Uptime, last 30 days
42.1% from 19 checks
Described by its publisher as
E2LLM gives your AI eyes and hands in a real browser: structured perception (SiFR) plus action.
Website
https://e2llm.com/
Repository
https://github.com/e2llm/e2llm-sifr
Listing
From the official MCP registry (active).
Recent checks of E2LLM
CheckedResultHandshake
1 hour agoHandshake completed344 ms
18 hours agoFailed - the check failed for an unclassified reason—
2 days agoHandshake completed351 ms
3 days agoHandshake completed328 ms
4 days agoHandshake completed318 ms
5 days agoHandshake completed458 ms
6 days agoFailed - the check failed for an unclassified reason—
7 days agoFailed - the check failed for an unclassified reason—
10 days agoFailed - the check failed for an unclassified reason—
13 days agoFailed - the check failed for an unclassified reason—
15 days agoFailed - the check failed for an unclassified reason—
17 days agoHandshake completed334 ms
19 days agoHandshake completed332 ms
21 days agoFailed - the check failed for an unclassified reason—
23 days agoFailed - the check failed for an unclassified reason—
25 days agoFailed - the check failed for an unclassified reason—
27 days agoFailed - the check failed for an unclassified reason—
28 days agoFailed - the check failed for an unclassified reason—
29 days agoHandshake completed321 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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