MCP.Market

Buyer Signals MCP server

online · 100% uptime
by openkrill.app·app.openkrill/buyersignals·v1.2.0

Companies that may buy, and public posts asking for a service: SEC, job boards, HN, Stack Exchange.

C65/100grade C
What users say
No reviews yet
Be the first
Safety scan
C65/100

not scanned yet

Adoption
New

Little public usage data yet

Reviews

Write one

Nobody has reviewed Buyer Signals yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Buyer Signals tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Buyer Signals compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
65/100
higher than 20% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
116 ms
faster than 80% of 30,031 servers

Release history: 2 versions in the registry since 2026-10-03, latest 2026-10-21, typically one every 18 days.

Install Buyer Signals in Claude Code, Cursor or VS Code

claude mcp add --transport http buyersignals https://signals.openkrill.app/mcp
Add to Cursor

Buyer Signals: common questions

Is Buyer Signals MCP server safe?
With care: it is graded C, so read the findings first (65/100). Read the Buyer Signals safety report
How do I install Buyer Signals?
It runs remotely at signals.openkrill.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Buyer Signals need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Buyer Signals maintained?
The latest release is v1.2.0.
Is Buyer Signals up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Buyer Signals compare with other MCP servers?
safety score 65/100 (higher than 20% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 116 ms (faster than 80% of 30,031 servers). Full comparison.