Remote MCP · Endpoint

Siigo Latam MCP server

No. Siigo Latam answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.siigolatam.com/mcp

The last check completed an MCP handshake.

Registry name
com.siigolatam/siigo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
68 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Catálogo, precios, artículos, compliance y datos de Siigo por país, en vivo para agentes de IA.
Website
https://www.siigo.com/llms.txt
Listing
From the official MCP registry (active).
Recent checks of Siigo Latam
CheckedResultHandshake
1 hour agoHandshake completed68 ms
2 days agoHandshake completed75 ms
5 days agoHandshake completed92 ms
7 days agoHandshake completed181 ms
9 days agoHandshake completed98 ms
11 days agoHandshake completed78 ms
13 days agoHandshake completed124 ms
15 days agoHandshake completed118 ms
18 days agoHandshake completed58 ms
19 days agoHandshake completed76 ms
20 days agoHandshake completed90 ms
22 days agoHandshake completed67 ms
23 days agoHandshake completed83 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.

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