Remote MCP · Endpoint

One Coworking MCP server

No. One Coworking answered an MCP handshake 12 minutes ago.

UpLast checked 12 minutes ago

Server URL

https://www.onecoworking.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.onecoworking.www/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
253 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find and compare coworking spaces and offices in 300+ European cities; get office quotes.
Listing
From the official MCP registry (active).
Recent checks of One Coworking
CheckedResultHandshake
12 minutes agoHandshake completed253 ms
9 days agoHandshake completed210 ms
9 days agoHandshake completed257 ms
11 days agoHandshake completed2.76 s
12 days agoHandshake completed250 ms
13 days agoHandshake completed2.19 s
14 days agoHandshake completed223 ms
14 days agoHandshake completed256 ms
16 days agoHandshake completed487 ms
19 days agoHandshake completed468 ms
21 days agoHandshake completed244 ms
24 days agoHandshake completed150 ms
26 days agoHandshake completed1.95 s
28 days agoHandshake completed155 ms

The last 14 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 One Coworking and makes no claim about it beyond what these checks measured.