Remote MCP · Endpoint

Order Group MCP server

No. Order Group answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://ordergroup.co/mcp

The last check completed an MCP handshake.

Registry name
co.ordergroup/public
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
503 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Send a software project enquiry to Order Group and browse its case studies (fintech, energy, IoT).
Website
https://ordergroup.co/
Listing
From the official MCP registry (active).
Recent checks of Order Group
CheckedResultHandshake
7 hours agoHandshake completed503 ms
12 hours agoHandshake completed597 ms
2 days agoHandshake completed568 ms
4 days agoHandshake completed523 ms
7 days agoHandshake completed568 ms
9 days agoHandshake completed522 ms
11 days agoHandshake completed527 ms
14 days agoHandshake completed503 ms
15 days agoHandshake completed705 ms
18 days agoHandshake completed1.52 s
20 days agoHandshake completed500 ms
21 days agoHandshake completed480 ms
23 days agoHandshake completed560 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 Order Group and makes no claim about it beyond what these checks measured.