Remote MCP · Endpoint

Saber MCP server

No. Saber answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://mcp.saber.app/mcp

The last check completed an MCP handshake.

Registry name
app.saber.mcp/saber
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
284 ms
Tools exposed
76 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Sales intelligence — research companies, qualify prospects, and find contacts.
Listing
From the official MCP registry (active).
Recent checks of Saber
CheckedResultHandshake
7 hours agoHandshake completed284 ms
2 days agoHandshake completed286 ms
4 days agoHandshake completed289 ms
5 days agoHandshake completed277 ms
7 days agoHandshake completed285 ms
8 days agoHandshake completed280 ms
9 days agoHandshake completed296 ms
12 days agoHandshake completed118 ms
13 days agoHandshake completed118 ms
15 days agoHandshake completed137 ms
16 days agoHandshake completed121 ms
18 days agoHandshake completed122 ms
19 days agoHandshake completed113 ms
19 days agoHandshake completed114 ms
20 days agoHandshake completed114 ms
21 days agoHandshake completed128 ms
23 days agoHandshake completed120 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 Saber and makes no claim about it beyond what these checks measured.