Remote MCP · Endpoint

Plexa MCP server

No. Plexa answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://api.joinplexa.com/mcp/

The last check completed an MCP handshake.

Registry name
com.joinplexa/plexa
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
66 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Agentic directory of real businesses in Mexico & LATAM. Search by vertical and city.
Listing
From the official MCP registry (active).
Recent checks of Plexa
CheckedResultHandshake
9 hours agoHandshake completed66 ms
2 days agoHandshake completed87 ms
4 days agoHandshake completed64 ms
5 days agoHandshake completed69 ms
7 days agoHandshake completed67 ms
8 days agoHandshake completed64 ms
9 days agoHandshake completed79 ms
12 days agoHandshake completed75 ms
13 days agoHandshake completed63 ms
15 days agoHandshake completed77 ms
16 days agoHandshake completed58 ms
17 days agoHandshake completed91 ms
19 days agoHandshake completed75 ms
19 days agoHandshake completed59 ms
20 days agoHandshake completed59 ms
21 days agoHandshake completed81 ms
22 days agoHandshake completed81 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 Plexa and makes no claim about it beyond what these checks measured.