Remote MCP · Endpoint

CIGAM MCP server

No. CIGAM answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.mcp.ai/p_cigam

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/cigam-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
69 ms
Tools exposed
28 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
CIGAM ERP (management for industry, retail and franchises) via session capture with your authorizati
Listing
From the official MCP registry (active).
Recent checks of CIGAM
CheckedResultHandshake
1 hour agoHandshake completed69 ms
2 days agoHandshake completed88 ms
4 days agoHandshake completed47 ms
5 days agoHandshake completed34 ms
7 days agoHandshake completed208 ms
8 days agoHandshake completed285 ms
9 days agoHandshake completed46 ms
12 days agoHandshake completed72 ms
14 days agoHandshake completed112 ms
15 days agoHandshake completed90 ms
17 days agoHandshake completed64 ms
18 days agoHandshake completed67 ms
19 days agoHandshake completed94 ms
20 days agoHandshake completed106 ms
20 days agoHandshake completed62 ms
21 days agoHandshake completed196 ms
23 days agoHandshake completed101 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 CIGAM and makes no claim about it beyond what these checks measured.