Remote MCP · Endpoint

com.jojapi/eyecon MCP server

No. com.jojapi/eyecon answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.jojapi.com/eyecon

The last check completed an MCP handshake.

Registry name
com.jojapi/eyecon
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
551 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Eyecon: Use the no.1 API for a true caller ID to identify name and see photos. 100% success rate.
Website
https://jojapi.com/hub/api/eyecon
Listing
From the official MCP registry (active).
Recent checks of com.jojapi/eyecon
CheckedResultHandshake
2 hours agoHandshake completed551 ms
2 days agoHandshake completed373 ms
4 days agoHandshake completed398 ms
5 days agoHandshake completed91 ms
7 days agoHandshake completed342 ms
8 days agoHandshake completed202 ms
9 days agoHandshake completed50 ms
12 days agoHandshake completed43 ms
13 days agoHandshake completed409 ms
15 days agoHandshake completed130 ms
17 days agoHandshake completed590 ms
18 days agoHandshake completed37 ms
19 days agoHandshake completed47 ms
20 days agoHandshake completed37 ms
20 days agoHandshake completed60 ms
22 days agoHandshake completed60 ms
23 days agoHandshake completed45 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 com.jojapi/eyecon and makes no claim about it beyond what these checks measured.