# Openkrill Buyersignals MCP server

Source: https://glimind.com/server/mcp-registry%2Fapp.openkrill%2Fbuyersignals
Registry id: `mcp-registry/app.openkrill/buyersignals`
Status: live (checked 2026-10-27T00:27:06.898Z)

## Verdict

Openkrill Buyersignals MCP server answered 99% of Glimind's liveness checks over 30 days, better than 8% of MCP servers, with 510 ms median handshake and 20 outages in 90 days. Its agent-readiness grade is A (94/100) across 8 tools, costing an agent about 2,924 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99% | 8% of MCP servers |
| Median handshake latency | 510 ms | 49% of MCP servers |
| p95 handshake latency | 2994 ms | — |
| Checks in 30 days | 4,226 | — |
| Outages, 90 days | 20 | — |
| Median recovery | 7 min | — |
| Agent-readiness score | 94/100 (A) | 78% of MCP servers |
| Tools | 8 | — |
| Tool-list size for an agent | ~2,924 tokens | 46% of MCP servers |
| Days observed | 23 | — |

## Install

```json
{
  "mcpServers": {
    "openkrill-buyersignals-mcp-server": {
      "type": "http",
      "url": "https://signals.openkrill.app/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http openkrill-buyersignals-mcp-server https://signals.openkrill.app/mcp
```

## Tools (8)

- `find_buyer_signals`: Use this when the user wants companies that recently raised money or have long-open roles, such as "which software companies in Texas filed a Form D this month?
- `find_buying_intent`: Use this when the user sells a service and wants public posts where people ask for it, such as "who is asking for an SEO audit?", "find posts from people lookin
- `get_feedback_reply`: Read the maintainers' reply to feedback you sent with submit_feedback, given its ticket id. Returns status pending until a reply is ready, then status answered 
- `index_tools`: Search the tools on this server by task or keyword in plain words. Returns the matching tools, best match first, each with its name, title, a one-line summary a
- `list_signal_sources`: Use this when the user asks where the signals come from, which sources are allowed, or why a source such as Y Combinator or LinkedIn is not used, for example "w
- `stack_pains`: Use this when the user wants an aggregate of which tools people use for a category, what they complain about, what else they consider, and what makes them switc
- `submit_feedback`: Send feedback, a bug report or a tool request to the maintainers of the tools on this server: a missing tool, missing or stale data, or a tool that broke or gav
- `weekly_brief`: Use this when the user asks for a weekly brief or for this week only, such as "weekly brief for SEO audit" or "did anyone ask for bookkeeping this week?". Pass 

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.