Remote MCP · Endpoint

Buyer Signals MCP server

No. Buyer Signals answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes 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
375 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 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
44 minutes agoHandshake completed375 ms
3 days agoHandshake completed301 ms
13 days agoHandshake completed469 ms
13 days agoHandshake completed325 ms
15 days agoHandshake completed203 ms
15 days agoHandshake completed317 ms
17 days agoHandshake completed181 ms
18 days agoHandshake completed442 ms
18 days agoHandshake completed405 ms
20 days agoHandshake completed345 ms
22 days agoHandshake completed4.58 s
25 days agoHandshake completed350 ms
27 days agoHandshake completed326 ms
29 days agoHandshake completed310 ms

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

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.