Remote MCP · Endpoint

ESQ Matching Engine MCP server

No. ESQ Matching Engine answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://match.esqcopilot.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.sustany/alcbar-match
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
55 ms
Tools exposed
26 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Find, compare and price licensed U.S. lawyers from official licensing records. Not legal advice.
Listing
From the official MCP registry (deprecated).
Recent checks of ESQ Matching Engine
CheckedResultHandshake
34 minutes agoHandshake completed55 ms
9 days agoHandshake completed65 ms
10 days agoHandshake completed73 ms
11 days agoHandshake completed70 ms
12 days agoHandshake completed58 ms
14 days agoHandshake completed258 ms
14 days agoHandshake completed92 ms
15 days agoHandshake completed99 ms
17 days agoHandshake completed175 ms
19 days agoHandshake completed56 ms
21 days agoHandshake completed64 ms
24 days agoHandshake completed56 ms
26 days agoHandshake completed98 ms

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

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