Remote MCP · Endpoint

online.sigmaintelligence/agentlab-services MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://sigmaintelligence.online/mcp

The last check failed: the server returned an HTTP error.

Registry name
online.sigmaintelligence/agentlab-services
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
14 tools
Uptime, last 30 days
35.7% from 14 checks
Described by its publisher as
Signed-quality-receipt micro-services for agents; verify before you pay (x402/USDC).
Listing
From the official MCP registry (active).
Recent checks of online.sigmaintelligence/agentlab-services
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
6 days agoFailed - the server returned an HTTP error—
8 days agoFailed - the server returned an HTTP error—
10 days agoFailed - the server returned an HTTP error—
13 days agoFailed - the server returned an HTTP error—
14 days agoFailed - the server returned an HTTP error—
16 days agoHandshake completed517 ms
17 days agoFailed - the server returned an HTTP error—
18 days agoHandshake completed362 ms
21 days agoHandshake completed370 ms
22 days agoHandshake completed339 ms
24 days agoHandshake completed348 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 5 responding of 14.

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 online.sigmaintelligence/agentlab-services and makes no claim about it beyond what these checks measured.