Intakra Buying Signals and Workspace
REMOTE · INTAKRA.COM
Review supplied buying evidence or OAuth-linked accounts, opportunities and workspace settings.
Available components
Last scanned (23 hours ago)
Scores higher than 77% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
Recent critical change
Authorization (24 Oct 2026). See the changelog before you install this server.
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 Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (set_offering). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1820 tokens (~113/item across 16 items; 15 tools + 1 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 68% of tool parameters carry a description.Partial
- 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
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 17 Nov 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 127 → 113 ▲ functional
- The server now declares the “resources” capability functional
- First check of Schema quality: 100 functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- New resource “lead-card” functional
- Server version: 3.2.0 → 3.3.0 functional
- 12 Nov 26 +1
- DNSSEC: fail → pass ▲ security
- 10 Nov 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Tool “add_accounts” rewrote its description, which is the text the model reads security
- Tool “get_account” rewrote its description, which is the text the model reads security
- Tool “get_account_changes” rewrote its description, which is the text the model reads security
- Tool “get_best_contact” rewrote its description, which is the text the model reads security
- Tool “get_daily_brief” rewrote its description, which is the text the model reads security
- Tool “get_project_updates” rewrote its description, which is the text the model reads security
- Tool “list_accounts” rewrote its description, which is the text the model reads security
- Tool “list_opportunities” rewrote its description, which is the text the model reads security
- Tool “list_suggestions” rewrote its description, which is the text the model reads security
- Tool “prioritize_accounts” rewrote its description, which is the text the model reads security
- Tool “request_accounts” rewrote its description, which is the text the model reads security
- Tool “set_offering” rewrote its description, which is the text the model reads security
- Schema quality: 1688 → 1913 ▼ functional
- Tool coverage: 14% → 100% ▲ functional
- MCP protocol: fail → pass ▲ functional
- Tool “add_accounts” now declares an output schema ▲ functional
- Tool “get_account” now declares an output schema ▲ functional
- Tool “get_account_changes” now declares an output schema ▲ functional
- Tool “get_best_contact” now declares an output schema ▲ functional
- Tool “get_daily_brief” now declares an output schema ▲ functional
- Tool “get_project_updates” now declares an output schema ▲ functional
- Tool “list_accounts” now declares an output schema ▲ functional
- Tool “list_opportunities” now declares an output schema ▲ functional
- Tool “list_suggestions” now declares an output schema ▲ functional
- Tool “prioritize_accounts” now declares an output schema ▲ functional
- Tool “request_accounts” now declares an output schema ▲ functional
- Tool “set_offering” now declares an output schema ▲ functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 3.1.0 → 3.2.0 functional
- New tool “get_offering” functional
- “get_project_updates” reworded the description of “opportunity_id” cosmetic
- Tool “get_project_updates” changed its title: Read project changes → Read changes on a lead cosmetic
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Oct 26 −4
- Authorization: partial → fail ▼ critical
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: intakra-public-signals → intakra security
- New tool “set_offering”, which the server declares destructive security
- Tool coverage: 100% → 14% ▼ functional
- Schema quality: 152 → 119 ▲ functional
- Tool coverage: 20% → 65% ▲ functional
- Schema quality: fair → good functional
- Server version: 1.0.0 → 3.1.0 functional
- New tool “add_accounts” functional
- New tool “get_account” functional
- New tool “get_account_changes” functional
- New tool “get_best_contact” functional
- New tool “get_daily_brief” functional
- New tool “get_project_updates” functional
- New tool “list_accounts” functional
- New tool “list_opportunities” functional
- New tool “list_suggestions” functional
- New tool “prioritize_accounts” functional
- New tool “request_accounts” functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
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 21 Nov 2026 · Probed https://intakra.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=intakra.com | CN=WE1,O=Google Trust Services,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 48c989b0ccc01a650e1d4962327e6cb2 |
| SANs: intakra.com, soxoa-demo.intakra.com, *.soxoa-demo.intakra.com | ||||||
| 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 intakra.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| intakra.com. | DS published | 2371 | 13 | Verified |
| intakra.com. | 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 |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://intakra.com/mcp | Verified | 200 | |
| http (plaintext) | http://intakra.com/mcp | HTTPS enforced | 301 | https://intakra.com/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 →
add_accounts Add accounts ~87
Use after the user asks to add companies. Adds accounts to the list by website domain (for example ["acme.com", "globex.com"]). Domains already on the list are skipped and the plan's account limit applies. Checks of new accounts start in the normal background pass, subject to the plan; this returns no findings.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | Up to 200 company domains |
| Name | Type | Req | Description |
|---|---|---|---|
| added | integer | yes | – |
| checks_stopped | string | – | Why no checks will run (plan canceled, paused or unpaid). |
| over_plan_limit | integer | – | – |
| skipped | integer | yes | – |
No examples provided.
get_account Look up an account ~83
Use for 'what do we know about acme.com?'. Returns one tracked account: up to 12 recent dated findings with links, and its open leads with dated proof. Pass a domain (acme.com), a company name or an account id. Saved records only, no new check.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | yes | Domain, company name, or account id |
| Name | Type | Req | Description |
|---|---|---|---|
| account | object | yes | – |
| as_of | string | – | – |
| open_opportunities | array | yes | – |
| open_opportunities_truncated | boolean | – | – |
| recent_findings | array | yes | – |
| recent_findings_limit | integer | – | – |
| recent_findings_truncated | boolean | – | – |
No examples provided.
get_account_changes Review changes on your account list ~175
Use for 'anything happening on my list?' or 'what changed at these companies this week?'. Returns findings recorded since a date (default seven days ago) for the tracked accounts, each with the event date, the date Intakra recorded it and a source link. Optional domains restrict the list. A finding can describe an older event recorded recently, and no findings is not proof of no activity. Saved records only.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | – | Optional company domains to check against your tracked list, up to 200. Omit to use your tracked accounts. |
| limit | integer | – | Findings to return, default 50. Narrow since or domains if truncated. |
| since | string | – | Start date YYYY-MM-DD or ISO 8601 timestamp with timezone, not in the future. Default: seven days ago. |
| Name | Type | Req | Description |
|---|---|---|---|
| account_check_details_truncated | boolean | – | – |
| account_scan_truncated | boolean | – | – |
| accounts | array | – | – |
| accounts_scanned | integer | – | – |
| as_of | string | – | – |
| changes | array | yes | – |
| changes_truncated | boolean | – | – |
| coverage_note | string | – | – |
| date_basis | string | – | – |
| matching_tracked_accounts | integer | – | – |
| missing_domains | array | – | Requested domains that are not on the list. |
| since | string | – | – |
No examples provided.
get_best_contact Who to reach for a lead ~153
Use for 'who should I reach about this lead, and why?'. Pass a lead id (eop_... or a match of your own rule) from list_opportunities or get_daily_brief. Returns the person who most likely owns it and why: name, role, LinkedIn, and a verified work email when there is one (never for EU, EEA or UK companies), or a LinkedIn search for the right title when nobody is named. Who and why only: Intakra never writes or sends messages.
| Name | Type | Req | Description |
|---|---|---|---|
| opportunity_id | string | yes | The lead id from list_opportunities or get_daily_brief (starts with eop_, or rh_ for a match of your own rule) |
| Name | Type | Req | Description |
|---|---|---|---|
| backup | object|null | – | – |
| company | string | – | – |
| contact | object|null | yes | The person named for the lead, or null when nobody is named yet. |
| item_kind | string | – | – |
| linkedin_search | object | – | A LinkedIn people search for the likely title, when nobody is named. |
| opportunity_id | string | yes | – |
| who_to_reach | array | – | – |
| why_them | string|null | – | – |
No examples provided.
get_daily_brief Today's note ~100
Use for 'what should I look at today?' or 'who is worth a call?'. Returns the leads in today's note: for each, what we found (dated, with links), what it usually means for what you sell, who to reach and why, and roughly how much time there is. If no note went out yet today, returns what the next one would hold. Quiet days return nothing; that is normal. Saved records only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | – |
| items | array | yes | – |
| note | string | yes | – |
| status | string | yes | sent: today's note went out. next: what the next note would hold. none: nothing to send. |
No examples provided.
get_offering Read what you sell ~66
Use before set_offering, or for 'what does Intakra think we sell?'. Returns the workspace's current description of what it sells, exactly as stored, or null when none is on file. Intakra uses it to decide which findings become leads. Read only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| offering | string|null | yes | What the workspace sells, as stored; null when nothing is on file. |
No examples provided.
get_project_updates Read changes on a lead ~93
Use when the user asks what changed on one lead. Pass opportunity_id from list_opportunities or get_daily_brief (eop_...). Returns whether the lead is watched and up to 20 dated before/after changes with sources. Saved evidence only: no new research and no notification.
| Name | Type | Req | Description |
|---|---|---|---|
| opportunity_id | string | yes | The lead id (starts with eop_) from list_opportunities or get_daily_brief. |
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | yes | Whether the lead is being watched. |
| baseline | – | – | The saved snapshot changes are compared against, or null when never watched. |
| changes | array | yes | Up to 20, newest first. |
| checkedAt | string|null | – | – |
No examples provided.
list_accounts List tracked accounts ~144
Use for 'which companies am I tracking?' or 'is acme.com on my list?'. Lists the accounts (companies) on the connected workspace's list, or matches domains you pass against it, with each account's last recorded check date, the domains not on the list and pagination. Saved records only: adds nothing and runs no new check.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | – | Optional company domains to check against your tracked list, up to 200. Omit to use your tracked accounts. |
| limit | integer | – | Accounts per page, default 50. |
| offset | integer | – | Start at this offset, default 0. Follow next_offset for remaining accounts. |
| Name | Type | Req | Description |
|---|---|---|---|
| account_list_url | string | – | – |
| account_scan_truncated | boolean | – | – |
| accounts | array | yes | – |
| accounts_scanned | integer | – | – |
| as_of | string | – | – |
| coverage_note | string | – | – |
| matching_tracked_accounts | integer | – | – |
| missing_domains | array | – | Requested domains that are not on the list. |
| next_offset | integer|null | yes | Pass as offset for the next page; null on the last page. |
No examples provided.
list_opportunities List leads ~119
Use for 'which accounts have an open buying signal?'. Returns open leads (id eop_..., dated proof with links, what it usually means for what you sell, rough time frame); filter closing_soon returns the ones that usually wind down within 30 days. Use the returned id with get_best_contact, get_project_updates and mark_opportunity. Saved records only.
| Name | Type | Req | Description |
|---|---|---|---|
| filter | string | – | open (default) or closing_soon |
| limit | number | – | How many to return (default 20, max 100) |
| Name | Type | Req | Description |
|---|---|---|---|
| held | integer | – | Leads held back by the quality gate (no dated, linked proof). |
| opportunities | array | yes | Open leads, highest priority first, each with its proof. |
No examples provided.
list_suggestions Suggested accounts ~82
Use for 'which accounts did Intakra suggest?'. Returns companies Intakra suggested adding to the list (from filings, news and lookalikes of your customers), each with the reason. Suggestions do not count toward the plan until approved in Intakra.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Default 25. |
| state | string | – | Default pending. |
| Name | Type | Req | Description |
|---|---|---|---|
| suggestions | array | yes | – |
No examples provided.
prepare_why_now_review Prepare an evidence-labeled why-now review ~123
Turn caller-supplied fit criteria and business signals into reviewable why-now and fit guidance. Every fact remains labeled caller-supplied and unverified. The tool does not research, infer budget or buyer intent as fact, draft outreach, access private data, persist input, or take action.
| Name | Type | Req | Description |
|---|---|---|---|
| account | object | yes | – |
| asOfDate | string | – | Optional date for reproducible recency scoring. Defaults to the current California date. |
| fitCriteria | array | yes | – |
| signals | array | yes | – |
| vendor | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accountName | string | yes | – |
| disposition | string | yes | – |
| evidenceGaps | array | yes | – |
| fitGuidance | string | yes | – |
| headline | string | yes | – |
| prohibitedActions | array | yes | – |
| questionsForReviewer | array | yes | – |
| requiresHumanReview | boolean | yes | – |
| sourceVerificationPerformed | boolean | yes | – |
| status | string | yes | – |
| supportedFacts | array | yes | – |
| whyNow | string | yes | – |
No examples provided.
prioritize_accounts Choose accounts worth a look ~172
Use for 'who should I target from my list?' or 'are these companies showing buying signals?'. Ranks tracked accounts by their best open lead for what you sell (and by the account score for fit, timing and reach, 0 to 100, when it is on for the workspace), each with dated proof, links and a rough time frame. Optional domains restrict the ranking. Also returns domains not on the list and accounts with no open lead. A lead suggests a reason to look; it does not confirm need, budget or purchase intent. Saved records only, no new research.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | – | Optional company domains to check against your tracked list, up to 200. Omit to use your tracked accounts. |
| limit | integer | – | Ranked accounts to return, default 20. |
| Name | Type | Req | Description |
|---|---|---|---|
| account_scan_truncated | boolean | – | – |
| accounts_scanned | integer | – | – |
| accounts_without_eligible_saved_signals | array | – | – |
| accounts_without_eligible_saved_signals_count | integer|null | – | – |
| accounts_without_returned_signals | array | – | – |
| accounts_without_returned_signals_count | integer | – | – |
| as_of | string | – | – |
| coverage_note | string | – | – |
| interpretation_note | string | – | – |
| matching_tracked_accounts | integer | – | – |
| missing_domains | array | – | Requested domains that are not on the list. |
| opportunity_scan_truncated | boolean | – | – |
| ranked_account_count | integer | – | – |
| ranked_accounts | array | yes | Accounts with an open lead, best first. |
| ranking_method | string | – | – |
| unsignaled_accounts_truncated | boolean | – | – |
No examples provided.
request_accounts Find accounts for me ~170
Use when the user asks Intakra to find companies, and ask first. Requests account suggestions from a short description, an industry, a size range, a country, or up to 5 customer domains. Runs in the background; results arrive later as suggestions (list_suggestions) and never count toward the plan until approved. A few requests a day at most.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Two letter country code, for example US |
| description | string | – | For example "logistics software companies in Texas" |
| employee_max | integer | – | – |
| employee_min | integer | – | – |
| industry | string | – | – |
| lookalike_domains | array | – | Up to 5 customer domains to find lookalikes of |
| region | string | – | US state or region code |
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string|null | – | – |
| status | string | yes | queued when the request was accepted. |
No examples provided.
score_buying_signal_evidence Score caller-supplied buying-signal evidence ~125
Deterministically score caller-supplied business-account fit and buying-signal evidence. Returns a review-only scorecard, evidence gaps, and unsupported-claim flags. The tool does not fetch sources, access Intakra workspaces, store input, spend money, draft outreach, or send anything.
| Name | Type | Req | Description |
|---|---|---|---|
| account | object | yes | – |
| asOfDate | string | – | Optional date for reproducible recency scoring. Defaults to the current California date. |
| fitCriteria | array | yes | – |
| signals | array | yes | – |
| vendor | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| accountName | string | yes | – |
| admissibleSignalCount | integer | yes | – |
| asOfDate | string | yes | – |
| boundaries | object | yes | – |
| disposition | string | yes | – |
| evidence | array | yes | – |
| evidenceGaps | array | yes | – |
| fit | object | yes | – |
| nextAction | string | yes | – |
| requiresHumanReview | boolean | yes | – |
| scores | object | yes | – |
| status | string | yes | – |
| unsupportedClaims | array | yes | – |
No examples provided.
set_offering Say what you sell ~94
Use only after the user confirms the new text; call get_offering first to show what it replaces. Replaces what the workspace sells, in a sentence or two (for example "Payroll software for restaurant groups with 5 to 50 locations"). Intakra uses it to decide which findings become leads. It replaces the current description.
| Name | Type | Req | Description |
|---|---|---|---|
| offering | string | yes | What you sell, 10 to 600 characters |
| Name | Type | Req | Description |
|---|---|---|---|
| offering | string | yes | What the workspace sells, as stored. |
No examples provided.
How do I install the Intakra Buying Signals and Workspace MCP server?
Intakra Buying Signals and Workspace is a hosted endpoint at https://intakra.com/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 · intakra.com
claude mcp add --transport http com-intakra-buying-signal-review 'https://intakra.com/mcp'
What is the Intakra Buying Signals and Workspace MCP server?
Intakra Buying Signals and Workspace is an MCP server listed in the public MCP registry as com.intakra/buying-signal-review. Review supplied buying evidence or OAuth-linked accounts, opportunities and workspace settings. This page covers its hosted endpoint (https://intakra.com/mcp).
Is the Intakra Buying Signals and Workspace MCP server safe to use?
Intakra Buying Signals and Workspace scores 80 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 Intakra Buying Signals and Workspace MCP server expose?
Intakra Buying Signals and Workspace exposes 15 tools: score_buying_signal_evidence, prepare_why_now_review, list_accounts, prioritize_accounts, get_account_changes, and 10 more. Their descriptions and schemas cost roughly 1,786 tokens of context every time the server is loaded.
Does the Intakra Buying Signals and Workspace MCP server require authentication?
No. We connected to Intakra Buying Signals and Workspace without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Intakra Buying Signals and Workspace MCP server still maintained?
Intakra Buying Signals and Workspace is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Intakra Buying Signals and Workspace MCP server?
VerifyMCP ran 13 checks on Intakra Buying Signals and Workspace, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.