Remote MCP · Endpoint

Cromanion MCP server

No. Cromanion answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://cromanion.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.cromanion/cromanion
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
65 ms
Tools exposed
29 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Raise conversion on a site you manage. No API key, no human to wake — you prove the domain.
Listing
From the official MCP registry (active).
Recent checks of Cromanion
CheckedResultHandshake
1 hour agoHandshake completed65 ms
2 days agoHandshake completed63 ms
4 days agoHandshake completed57 ms
5 days agoHandshake completed74 ms
7 days agoHandshake completed76 ms
7 days agoHandshake completed76 ms
9 days agoHandshake completed91 ms
12 days agoHandshake completed81 ms
13 days agoHandshake completed55 ms
15 days agoHandshake completed83 ms
16 days agoHandshake completed144 ms
17 days agoHandshake completed63 ms
18 days agoHandshake completed55 ms
19 days agoHandshake completed56 ms
20 days agoHandshake completed73 ms
21 days agoHandshake completed65 ms
22 days agoHandshake completed68 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 Cromanion and makes no claim about it beyond what these checks measured.