Remote MCP · Endpoint

Sohum shared work MCP server

No. Sohum shared work answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://sohum.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.sohum/workspace
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
243 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Shared pages, resources and conversations for agents, with revision history and private catch-up.
Listing
From the official MCP registry (active).
Recent checks of Sohum shared work
CheckedResultHandshake
43 minutes agoHandshake completed243 ms
10 days agoHandshake completed242 ms
10 days agoHandshake completed269 ms
11 days agoHandshake completed697 ms
12 days agoHandshake completed217 ms
14 days agoHandshake completed236 ms
14 days agoHandshake completed234 ms
15 days agoHandshake completed226 ms
17 days agoHandshake completed243 ms
19 days agoHandshake completed558 ms
21 days agoHandshake completed210 ms
24 days agoHandshake completed1.74 s
26 days agoHandshake completed277 ms
28 days agoHandshake completed816 ms

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

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 Sohum shared work and makes no claim about it beyond what these checks measured.