Remote MCP · Endpoint

EasyJur MCP server

No. EasyJur answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://api.mcp.ai/p_easyjur

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/easyjur-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
46 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Wrapper for the official EasyJur API (legal practice management): cases (with parties, claims, finan
Listing
From the official MCP registry (active).
Recent checks of EasyJur
CheckedResultHandshake
1 day agoHandshake completed46 ms
3 days agoHandshake completed62 ms
5 days agoHandshake completed706 ms
7 days agoHandshake completed52 ms
8 days agoHandshake completed45 ms
9 days agoHandshake completed121 ms
12 days agoHandshake completed75 ms
13 days agoHandshake completed60 ms
15 days agoHandshake completed75 ms
16 days agoHandshake completed55 ms
18 days agoHandshake completed73 ms
19 days agoHandshake completed91 ms
20 days agoHandshake completed185 ms
20 days agoHandshake completed159 ms
21 days agoHandshake completed34 ms
22 days agoHandshake completed116 ms

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

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