Remote MCP · Endpoint

Cymosoft MCP server

No. Cymosoft answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://cymosoft.com/mcp

The last check completed an MCP handshake.

Registry name
com.cymosoft/cymosoft
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
54 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Cymosoft JSC profile and case studies (EN/JA) plus Japanese text utilities (文字数・全角半角・和暦)
Listing
From the official MCP registry (active).
Recent checks of Cymosoft
CheckedResultHandshake
1 hour agoHandshake completed54 ms
2 days agoHandshake completed86 ms
4 days agoHandshake completed61 ms
5 days agoHandshake completed66 ms
7 days agoHandshake completed90 ms
8 days agoHandshake completed323 ms
9 days agoHandshake completed44 ms
12 days agoHandshake completed43 ms
13 days agoHandshake completed87 ms
15 days agoHandshake completed77 ms
16 days agoHandshake completed49 ms
17 days agoHandshake completed66 ms
18 days agoHandshake completed38 ms
19 days agoHandshake completed46 ms
20 days agoHandshake completed64 ms
21 days agoHandshake completed77 ms
22 days agoHandshake completed48 ms

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

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