Remote MCP · Endpoint

dev.aieph/aieph MCP server

No. dev.aieph/aieph answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://aieph.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.aieph/aieph
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
300 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Shared knowledge cache for AI coding agents — reuse an answer once it exists.
Website
https://aieph.dev/
Repository
https://github.com/tryaieph/aieph
Listing
From the official MCP registry (active).
Recent checks of dev.aieph/aieph
CheckedResultHandshake
1 hour agoHandshake completed300 ms
2 days agoHandshake completed176 ms
4 days agoHandshake completed182 ms
5 days agoHandshake completed469 ms
7 days agoHandshake completed243 ms
8 days agoHandshake completed759 ms
9 days agoHandshake completed314 ms
12 days agoHandshake completed187 ms
13 days agoHandshake completed244 ms
15 days agoHandshake completed205 ms
16 days agoHandshake completed504 ms
18 days agoHandshake completed200 ms
19 days agoHandshake completed229 ms
20 days agoHandshake completed222 ms
20 days agoHandshake completed438 ms
21 days agoHandshake completed345 ms
22 days agoHandshake completed491 ms

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

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 dev.aieph/aieph and makes no claim about it beyond what these checks measured.