Remote MCP · Endpoint

Buyer Signals MCP server

No. Buyer Signals answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://signals.openkrill.app/mcp

The last check completed an MCP handshake.

Registry name
app.openkrill/buyersignals
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
4.58 s
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Companies that may buy, and public posts asking for a service: SEC, job boards, HN, Stack Exchange.
Listing
From the official MCP registry (active).
Recent checks of Buyer Signals
CheckedResultHandshake
7 hours agoHandshake completed4.58 s
2 days agoHandshake completed350 ms
5 days agoHandshake completed326 ms
7 days agoHandshake completed310 ms
9 days agoHandshake completed372 ms
11 days agoHandshake completed310 ms
13 days agoHandshake completed1.45 s
15 days agoHandshake completed844 ms
17 days agoHandshake completed35 ms
19 days agoHandshake completed337 ms
20 days agoHandshake completed894 ms
21 days agoHandshake completed390 ms
23 days agoHandshake completed288 ms

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

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