Remote MCP · Endpoint

SigmaJunction MCP server

No. SigmaJunction answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://sigmajunction.com/mcp

The last check completed an MCP handshake.

Registry name
com.sigmajunction/site
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
164 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Software engineering firm in Serbia: services, engagement models, articles - and send an inquiry.
Listing
From the official MCP registry (active).
Recent checks of SigmaJunction
CheckedResultHandshake
3 hours agoHandshake completed164 ms
10 hours agoHandshake completed167 ms
2 days agoHandshake completed528 ms
4 days agoHandshake completed160 ms
7 days agoHandshake completed199 ms
9 days agoHandshake completed190 ms
11 days agoHandshake completed440 ms
13 days agoHandshake completed432 ms
15 days agoHandshake completed2.79 s
18 days agoHandshake completed417 ms
20 days agoHandshake completed328 ms
21 days agoHandshake completed153 ms
23 days agoHandshake completed211 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.

Listing data comes from the official MCP registry. Glide is not affiliated with SigmaJunction and makes no claim about it beyond what these checks measured.