Remote MCP · Endpoint

Sohum shared work MCP server

No. Sohum shared work answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
277 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 15 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
1 hour agoHandshake completed277 ms
2 days agoHandshake completed816 ms
4 days agoHandshake completed843 ms
6 days agoHandshake completed1.27 s
8 days agoHandshake completed561 ms
10 days agoHandshake completed304 ms
11 days agoHandshake completed223 ms
13 days agoHandshake completed421 ms
14 days agoHandshake completed269 ms
15 days agoHandshake completed95 ms
18 days agoHandshake completed229 ms
19 days agoHandshake completed212 ms
21 days agoHandshake completed376 ms
22 days agoHandshake completed205 ms
23 days agoHandshake completed217 ms

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

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.