Remote MCP · Endpoint

Epinu MCP server

No. Epinu answered an MCP handshake 10 hours ago.

UpLast checked 10 hours ago

Server URL

https://api.epinu.ai/api/agent/mcp

The last check completed an MCP handshake.

Registry name
ai.epinu/epinu
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
79 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Agent-first marketplace for real-world assets — agro and energy first; humans approve every write.
Listing
From the official MCP registry (active).
Recent checks of Epinu
CheckedResultHandshake
10 hours agoHandshake completed79 ms
2 days agoHandshake completed86 ms
4 days agoHandshake completed56 ms
5 days agoHandshake completed62 ms
7 days agoHandshake completed109 ms
8 days agoHandshake completed256 ms
9 days agoHandshake completed47 ms
12 days agoHandshake completed100 ms
13 days agoHandshake completed54 ms
15 days agoHandshake completed61 ms
16 days agoHandshake completed52 ms
17 days agoHandshake completed48 ms
18 days agoHandshake completed54 ms
19 days agoHandshake completed50 ms
20 days agoHandshake completed76 ms
21 days agoHandshake completed48 ms
23 days agoHandshake completed174 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.

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