Remote MCP · Endpoint

Onsa MCP server

No. Onsa answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://api.onsa.ai/api/mcp

The last check completed an MCP handshake.

Registry name
ai.onsa/onsa
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
152 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Find scored B2B leads, read campaign replies and send approved LinkedIn outreach.
Listing
From the official MCP registry (active).
Recent checks of Onsa
CheckedResultHandshake
2 hours agoHandshake completed152 ms
1 day agoHandshake completed130 ms
3 days agoHandshake completed128 ms
3 days agoHandshake completed114 ms
4 days agoHandshake completed137 ms
5 days agoHandshake completed116 ms
7 days agoHandshake completed129 ms
10 days agoHandshake completed126 ms
12 days agoHandshake completed106 ms
15 days agoHandshake completed138 ms
17 days agoHandshake completed138 ms
19 days agoHandshake completed143 ms
21 days agoHandshake completed151 ms
23 days agoHandshake completed171 ms
25 days agoHandshake completed156 ms
26 days agoHandshake completed104 ms
28 days agoHandshake completed425 ms
29 days agoHandshake completed5.62 s

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

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