Remote MCP · Endpoint

mexsaas MCP server

No. mexsaas answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.mexsaas.com/mcp

The last check completed an MCP handshake.

Registry name
com.mexsaas/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.32 s
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Software que usan los negocios en México: busca, compara y ve alternativas, con precio en pesos.
Website
https://www.mexsaas.com/ia
Listing
From the official MCP registry (active).
Recent checks of mexsaas
CheckedResultHandshake
1 hour agoHandshake completed1.32 s
2 days agoHandshake completed1.39 s
5 days agoHandshake completed89 ms
7 days agoHandshake completed247 ms
9 days agoHandshake completed229 ms
11 days agoHandshake completed124 ms
13 days agoHandshake completed159 ms
15 days agoHandshake completed117 ms
18 days agoHandshake completed91 ms
19 days agoHandshake completed100 ms
21 days agoHandshake completed117 ms
21 days agoHandshake completed759 ms
23 days agoHandshake completed139 ms
25 days agoHandshake completed232 ms

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

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