Remote MCP · Endpoint

Multiservicios services MCP server

No. Multiservicios services answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://mcp.multiservicios.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.multiservicios/services
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
141 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Lists Multiservicios services and leaves a request to be contacted. Does not quote, sell or issue.
Listing
From the official MCP registry (active).
Recent checks of Multiservicios services
CheckedResultHandshake
34 minutes agoHandshake completed141 ms
8 days agoHandshake completed199 ms
9 days agoHandshake completed105 ms
11 days agoHandshake completed129 ms
12 days agoHandshake completed208 ms
12 days agoHandshake completed135 ms
14 days agoHandshake completed159 ms
14 days agoHandshake completed181 ms
16 days agoHandshake completed160 ms
19 days agoHandshake completed109 ms
21 days agoHandshake completed118 ms
24 days agoHandshake completed218 ms
26 days agoHandshake completed127 ms
28 days agoHandshake completed95 ms

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

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