Remote MCP · Endpoint

Sapien Solutions MCP server

No. Sapien Solutions answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://sapiensolutions.com/mcp

The last check completed an MCP handshake.

Registry name
com.sapiensolutions/site
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
162 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Sapien Solutions, Cleveland: what we build, our work, where we work, and inquiries.
Listing
From the official MCP registry (active).
Recent checks of Sapien Solutions
CheckedResultHandshake
5 hours agoHandshake completed162 ms
9 days agoHandshake completed238 ms
10 days agoHandshake completed199 ms
11 days agoHandshake completed323 ms
12 days agoHandshake completed134 ms
14 days agoHandshake completed163 ms
14 days agoHandshake completed157 ms
15 days agoHandshake completed152 ms
17 days agoHandshake completed301 ms
19 days agoHandshake completed353 ms
21 days agoHandshake completed254 ms
24 days agoHandshake completed225 ms
26 days agoHandshake completed344 ms
28 days agoHandshake completed190 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 Sapien Solutions and makes no claim about it beyond what these checks measured.