Remote MCP · Endpoint

Sugra API MCP server

No. Sugra API answered an MCP handshake 16 hours ago.

UpLast checked 16 hours ago

Server URL

https://app.sugra.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.sugra/api-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
32 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Gateway between LLM agents and world data through eight tools and a bundled endpoint catalog.
Listing
From the official MCP registry (active).
Recent checks of Sugra API
CheckedResultHandshake
16 hours agoHandshake completed32 ms
2 days agoHandshake completed31 ms
4 days agoHandshake completed49 ms
6 days agoHandshake completed27 ms
7 days agoHandshake completed49 ms
8 days agoHandshake completed34 ms
9 days agoHandshake completed30 ms
12 days agoHandshake completed34 ms
14 days agoHandshake completed28 ms
15 days agoHandshake completed26 ms
17 days agoHandshake completed30 ms
18 days agoHandshake completed26 ms
19 days agoHandshake completed27 ms
20 days agoHandshake completed28 ms
20 days agoHandshake completed50 ms
21 days agoHandshake completed41 ms
23 days agoHandshake completed35 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 Sugra API and makes no claim about it beyond what these checks measured.