Remote MCP · Endpoint

Menso MCP server

No. Menso answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://api.menso.io/mcp

The last check completed an MCP handshake.

Registry name
io.menso/menso
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
62 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
AI users run real tasks on your live site and show where they get stuck, with a replay of every step
Listing
From the official MCP registry (active).
Recent checks of Menso
CheckedResultHandshake
2 hours agoHandshake completed62 ms
2 days agoHandshake completed53 ms
4 days agoHandshake completed56 ms
6 days agoHandshake completed54 ms
8 days agoHandshake completed50 ms
10 days agoHandshake completed54 ms
12 days agoHandshake completed47 ms
14 days agoHandshake completed54 ms
15 days agoHandshake completed54 ms
16 days agoHandshake completed74 ms
18 days agoHandshake completed53 ms
20 days agoHandshake completed56 ms
22 days agoHandshake completed58 ms
23 days agoHandshake completed47 ms

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

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