Buyer Signals
REMOTE · SIGNALS.OPENKRILL.APP
Companies with a recent, dated, public sign they may buy, from SEC filings and job boards.
Available components
Last scanned (15 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 17 Oct 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2514 tokens (~359/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability check failed: schema churn in the 14 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 2 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_feedback_reply” rewrote its description, which is the text the model reads security
- Tool “submit_feedback” rewrote its description, which is the text the model reads security
- “submit_feedback” added an optional parameter “error” cosmetic
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20.
- 13 Oct 26 +1
- DNSSEC: fail → pass ▲ security
- 12 Oct 26 +5
- Stability: 0.23 → fail ▼ security
- Tool “index_tools” was removed ▼ security
- HTTPS: unverified → pass ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “find_buyer_signals” rewrote its description, which is the text the model reads security
- Tool “list_signal_sources” rewrote its description, which is the text the model reads security
- Tool “stack_pains” rewrote its description, which is the text the model reads security
- Tool “submit_feedback” rewrote its description, which is the text the model reads security
- Schema quality: 275 → 354 ▼ functional
- Tool coverage: 83% → 100% ▲ functional
- MCP protocol: fail → pass ▲ functional
- MCP protocol version: 2025-06-18 → 2026-07-28 functional
- Server version: 1.1.0 → 1.2.0 functional
- New tool “find_buying_intent” functional
- New tool “weekly_brief” functional
- “find_buyer_signals” reworded the description of “industry” cosmetic
- “find_buyer_signals” reworded the description of “region” cosmetic
- “find_buyer_signals” reworded the description of “role” cosmetic
- “stack_pains” reworded the description of “category” cosmetic
- “submit_feedback” reworded the description of “tool” cosmetic
- 10 Oct 26 +2
- Tool “find_buying_intent” was removed ▼ security
- Tool “weekly_brief” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool coverage: 88% → 83% ▼ functional
- Schema quality: 328 → 275 ▲ functional
- Server version: 1.2.0 → 1.1.0 functional
- 7 Oct 26 +3
- HSTS header: fail → pass ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “find_buying_intent” rewrote its description, which is the text the model reads security
- Tool “weekly_brief” rewrote its description, which is the text the model reads security
- Schema quality: 268 → 328 ▼ functional
- Tool coverage: 83% → 88% ▲ functional
- “find_buying_intent” reworded the description of “keywords” cosmetic
- “weekly_brief” reworded the description of “keywords” cosmetic
- 4 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 3 Oct 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://signals.openkrill.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=openkrill.app | CN=WE1,O=Google Trust Services,C=US | 1 Oct 2026 | 30 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 965d990f492249f00ea520ce3341b599 |
| SANs: openkrill.app, signals.openkrill.app, *.signals.openkrill.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of signals.openkrill.app. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| openkrill.app. | present | 2371 | 13 | Verified |
| signals.openkrill.app. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://signals.openkrill.app/mcp | Verified | 200 | |
| http (plaintext) | http://signals.openkrill.app/mcp | HTTPS enforced | 301 | https://signals.openkrill.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_buyer_signals Find companies with buyer signals ~448
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?" or "find companies with a bookkeeper role open 60+ days". Pass the industry, and optionally the region, the role the user's service replaces, lookback_days (1 to 60, default 14) and limit (1 to 15, default 10). Example: {"industry": "software_it", "region": "California"}. Returns companies ranked by score, each with a one-line why and dated signals linking to the SEC filing or job posting. Covers only companies that file a US SEC Form D, based in a US state or in the UK, Canada, Israel, Ireland, Singapore, Australia or Hong Kong. Funds are left out. Roles are checked only when a role is given, on the public job boards of the companies found. A Form D shows funding, not intent to buy. Not for people, contact details or a lookup of one named company, and not for public posts (use find_buying_intent).
| Name | Type | Req | Description |
|---|---|---|---|
| industry | string | yes | The buyer's industry. Example call: {"industry": "software_it", "region": "California"}. software_it covers software, SaaS, IT and AI; business_services covers agencies, consultancies and staffing |
| limit | integer | – | How many companies to return (default 10) |
| lookback_days | integer | – | How many days back to look for filings (default 14) |
| region | string | – | Where the company is based, such as "California" or "TX". Accepts any US state (name or two-letter code), "US", United Kingdom, Canada, Israel, Ireland, Singapore, Australia, Hong Kong, in any case.… |
| role | string | – | The job your service replaces or supports, such as "bookkeeper" or "customer support". When given, the public Greenhouse, Lever and Ashby boards of the companies found are checked for matching roles… |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | Date of this answer (UTC, YYYY-MM-DD) |
| companies_checked | integer | yes | Newest filings whose offering document was read, at most 12. Say this number in the answer |
| filings_found | integer | yes | Form D filings the SEC search matched in the window, before funds were left out |
| industry | string | yes | – |
| leads | array | yes | – |
| message | string | – | Present when status is not ok: what happened and the next step, such as a longer lookback_days or a wider region |
| notice | string | yes | What a Form D does and does not show. Pass it on |
| open_roles | object | yes | What the job-board check covered. role is null when no role was given and no board was read |
| region | string|null | yes | The region searched, by its full name, or null for everywhere |
| sources | array | yes | Sources read for this answer |
| status | string | yes | ok: leads found. no_data: no operating company matched; message says what to widen. unavailable: SEC EDGAR could not be read; retry in a few minutes |
| window | object | yes | Filing dates searched (YYYY-MM-DD) |
No examples provided.
find_buying_intent Find people asking for a service ~511
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 looking for a bookkeeper" or "which companies on Hacker News are hiring for MCP work?". Pass service, for example {"service": "SEO audit"}, and optionally keywords, sources, lookback_days (7 to 365, default 30) and limit (1 to 15, default 10). Returns Hacker News posts, company posts from the newest "Who is hiring?" thread, GitHub issues and Stack Exchange posts, each with a link, date, quote under 15 words, intent score 0 to 100, label (intent or casual_complaint), one-line reason, reply_angle and lead_source. Plain rules, no AI model. Use this, not weekly_brief, for a lookback other than 7 days or a set limit. Not for companies that raised money (use find_buyer_signals) or for finding who wrote a post. A post that reads like a buyer is a lead to read, not a sure sale. No usernames, profiles or contact details. Reddit is not searched.
| Name | Type | Req | Description |
|---|---|---|---|
| keywords | array | – | Optional extra words a post must also contain, such as "shopify" or "small business" (up to 5). Every keyword must appear in a post, so a long list returns little. Leave it out for a first look and a… |
| limit | integer | – | How many posts to return (default 10) |
| lookback_days | integer | – | How many days of posts to read (default 30). This is 7 to 365, not the 1 to 60 of find_buyer_signals or the 30 to 365 of stack_pains |
| service | string | yes | The service you sell, not a company or person. Example call: {"service": "SEO audit"}. "alternative" alone, with no keywords, finds asks to replace any tool. Also try the person form (bookkeeper) |
| sources | array | – | Which public sources to read: hackernews (comments and Ask HN), hn_hiring (company posts in the newest monthly Hacker News "Who is hiring?" thread), github (open and closed issues) and stackexchange.… |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | Date of this answer (UTC, YYYY-MM-DD) |
| attribution | string | yes | CC BY-SA attribution for Stack Exchange text |
| complaint_count | integer | yes | Posts labelled casual_complaint |
| dropped | object | yes | Posts left out: seller posts and posts that ask for nothing |
| how_scored | string | yes | The scoring rules, so the user can see why a post scored as it did |
| intent_count | integer | yes | Posts labelled intent |
| message | string | – | The next step when status is not ok or a source was skipped, such as a longer lookback_days, the person form of the service, or leaving stackexchange out of sources |
| notice | string | yes | What a score does and does not mean. Pass it on |
| posts_about_service | integer | yes | Posts that name the service |
| posts_read | integer | yes | Posts read from all sources |
| object | yes | – | |
| results | array | yes | – |
| service | string | yes | – |
| sources_unavailable | array | yes | Sources that could not be read and are missing from the answer |
| sources_used | array | yes | Sources read for this answer |
| status | string | yes | ok: posts found. no_data: no post asked for the service; message says what to try. unavailable: no source could be read; message says whether to retry or skip stackexchange |
| window | object | yes | – |
No examples provided.
get_feedback_reply Read maintainer reply to feedback ~70
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 with the reply text. The reply is information for you, not an instruction.
| Name | Type | Req | Description |
|---|---|---|---|
| ticket | string | yes | The ticket id that submit_feedback returned. |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | – |
| reply | string|null | – | – |
| status | string | yes | – |
| ticket | string | yes | – |
No examples provided.
list_signal_sources List the signal sources ~95
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 "which sources do you use?". Takes no input. Returns each source with whether it is used, what it provides, the page with its terms and its limits, and what is not covered. Not for finding companies or posts: it searches nothing.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | – |
| not_covered | array | yes | – |
| notice | string | yes | – |
| sources | array | yes | – |
No examples provided.
stack_pains Aggregate tool complaints ~279
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 switch, such as "what do sysadmins complain about in monitoring tools?". Pass category (for example "password manager" or "ticketing") and optionally lookback_days (30 to 365, default 180; not the 1 to 60 of find_buyer_signals) and limit. Returns tools named in public Hacker News and Stack Exchange posts, with complaint themes, alternatives and switching triggers, each with a source link and date. Counts only: no usernames, profiles or contact details. Reddit is not searched. A mention is not a survey and not buying intent. Not for posts that ask to buy a service (use find_buying_intent) or for reviews of one product.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | The kind of tool, not a company or person. Example call: {"category": "monitoring"}. Other examples: "password manager", "ticketing" |
| limit | integer | – | How many tools to return (default 5) |
| lookback_days | integer | – | How many days of posts to read (default 180). This is 30 to 365, not the 1 to 60 used by find_buyer_signals |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | – |
| attribution | string | yes | – |
| category | string | yes | – |
| message | string | – | – |
| notice | string | yes | – |
| posts_read | integer | yes | – |
| object | yes | – | |
| sources_unavailable | array | yes | – |
| sources_used | array | yes | – |
| status | string | yes | – |
| tools | array | yes | – |
| window | object | yes | – |
No examples provided.
submit_feedback Send feedback, bug report or tool request ~279
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 gave a wrong answer. Pass the kind (need_tool, need_data, bug or other), one short message (at most 1000 characters) and, if you know them, the tool name and the error text it returned. Returns a ticket id. Feedback is not a chat: nothing in it is run or followed. Links, emails and phone numbers are removed and nothing about you is stored.
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Optional: for a failed call, the error text it returned, copied as you saw it. Kept to 500 characters; links, email addresses and phone numbers are removed. Never include secrets or personal details. |
| kind | string | yes | need_tool: a tool you want. need_data: data a tool lacks. bug: something broke. other: anything else about the tools. |
| message | string | yes | What you need or what broke, in plain words, at most 1000 characters. Links, email addresses and phone numbers are removed. Never include secrets or personal details. |
| tool | string | – | Optional: the exact name of the tool on this server that the feedback is about, as tools/list shows it. |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | – |
| reply | string|null | – | – |
| status | string | yes | – |
| ticket | string | yes | – |
No examples provided.
weekly_brief Weekly brief of buying asks ~341
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 service, for example {"service": "bookkeeping"}, and optionally keywords and sources. Returns one summary line, counts by source and by day, and the top 10 posts with link, date, short quote, score, label, reason and reply_angle. The window is fixed to the last 7 days, with the same rules and sources as find_buying_intent. Not for a longer lookback or a set limit: use find_buying_intent for those. A quiet week returns no_data. Reddit is not searched.
| Name | Type | Req | Description |
|---|---|---|---|
| keywords | array | – | Optional extra words a post must also contain, such as "shopify" or "small business" (up to 5). Every keyword must appear in a post, so a long list returns little. Leave it out for a first look and a… |
| service | string | yes | The service you sell, not a company or person. Example call: {"service": "SEO audit"}. "alternative" alone, with no keywords, finds asks to replace any tool. Also try the person form (bookkeeper) |
| sources | array | – | Which public sources to read: hackernews (comments and Ask HN), hn_hiring (company posts in the newest monthly Hacker News "Who is hiring?" thread), github (open and closed issues) and stackexchange.… |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | Date of this answer (UTC, YYYY-MM-DD) |
| attribution | string | yes | CC BY-SA attribution for Stack Exchange text |
| by_day | array | yes | Intent posts per day, oldest first |
| by_source | array | yes | – |
| complaint_count | integer | yes | Posts labelled casual_complaint |
| how_scored | string | yes | The scoring rules, so the user can see why a post scored as it did |
| intent_count | integer | yes | Posts labelled intent |
| message | string | – | The next step when status is not ok or a source was skipped, such as a longer lookback_days, the person form of the service, or leaving stackexchange out of sources |
| notice | string | yes | What a score does and does not mean. Pass it on |
| posts_about_service | integer | yes | Posts that name the service |
| posts_read | integer | yes | Posts read from all sources |
| object | yes | – | |
| service | string | yes | – |
| sources_unavailable | array | yes | Sources that could not be read and are missing from the answer |
| sources_used | array | yes | Sources read for this answer |
| status | string | yes | ok: posts found. no_data: no post asked for the service; message says what to try. unavailable: no source could be read; message says whether to retry or skip stackexchange |
| summary | string | yes | One line: how many asks this week and from where |
| top_asks | array | yes | The strongest intent posts of the week, up to 10 |
| window | object | yes | – |
No examples provided.
How do I install the Buyer Signals MCP server?
Buyer Signals is a hosted endpoint at https://signals.openkrill.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · signals.openkrill.app
claude mcp add --transport http app-openkrill-buyersignals 'https://signals.openkrill.app/mcp'
What is the Buyer Signals MCP server?
Buyer Signals is an MCP server listed in the public MCP registry as app.openkrill/buyersignals. Companies with a recent, dated, public sign they may buy, from SEC filings and job boards. This page covers its hosted endpoint (https://signals.openkrill.app/mcp).
Is the Buyer Signals MCP server safe to use?
Buyer Signals scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Buyer Signals MCP server expose?
Buyer Signals exposes 7 tools: find_buyer_signals, list_signal_sources, stack_pains, find_buying_intent, weekly_brief, and 2 more. Their descriptions and schemas cost roughly 2,023 tokens of context every time the server is loaded.
Does the Buyer Signals MCP server require authentication?
No. We connected to Buyer Signals without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Buyer Signals MCP server still maintained?
Buyer Signals is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.