mcpbeat Sign in

Intakra Public Signal Review MCP Server

not responding

Intakra Public Signal Review is listed as active in the registry but did not answer our last check. It exposes 2 tools.

Score supplied buying-signal evidence and prepare review-only why-now briefs. Read-only, no auth.

Uptime history 14 hours of history · worst hour 0%
14 hours agonow
58.3%
Uptime 24h
28 of 48 checks
2
Tools
read from the server
815 ms
Response time
average over 24h
open, no key
Access
streamable-http

Intakra Public Signal Review does not always answer

Over the last week it answered 58.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

run in your terminal
claude mcp add buying-signal-review --transport http https://intakra.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "buying-signal-review": {
      "url": "https://intakra.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.buying-signal-review]
url = "https://intakra.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "buying-signal-review": {
      "url": "https://intakra.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "buying-signal-review": {
      "url": "https://intakra.com/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

prepare
prepare_why_now_review
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.
score
score_buying_signal_evidence
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.

Endpoints

URLTransportStateLatencyChecked
https://intakra.com/mcp streamable-http answering 68 ms 2 min ago

Alternatives to Intakra Public Signal Review

same job, measured the same way
C
AI Arena Agent Tools
by ai-arena

Read-only US public-data screening tools with free Basic and Evidence tiers.

13 tools answering
One AI Guide
by oneaiguide

Read-only approved AI tools, public stacks, guides, and evidence-aware comparisons.

7 tools answering
Riptide — public risk and event research
by beepboop2025

Read-only paper risk evidence and policy-gated committed event research. No real orders.

answering
Agenda Intelligence MD
by vassiliylakhonin

Evidence-readiness MCP server: validate, audit, and score briefs, memos, and evidence packs.

514 installs/wk 1 tools answering
Say Ur Intent
by stelis-dev

Local-first Sui DeFi evidence and review for AI clients before wallet signing.

51 installs/wk local only
I
Recipe Signal
by absharma9796

Search and compare attributed recipe records through a public read-only remote MCP endpoint.

4 tools answering
WP Update Radar
by utilityhouse-updates

WordPress plugin release signals from public support threads, with evidence and explicit unknowns.

2 tools answering
Financial Evidence
by beepboop2025

Read-only public financial evidence from LiquiLens, Undertow, Seiche and Palimpsest.

3 tools answering

Intakra Public Signal Review — questions

Answers built from our own checks of this server.

What can Intakra Public Signal Review do?
It exposes 2 tools, read directly from the server on our last check. Among them: prepare_why_now_review, score_buying_signal_evidence. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Intakra Public Signal Review working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 28 of 48 checks got a reply (58.3%), average response time 815 ms. The bar chart above shows every period we have measured.
The registry lists Intakra Public Signal Review as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Intakra Public Signal Review?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Intakra Public Signal Review need an API key?
No. Intakra Public Signal Review completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Intakra Public Signal Review?
It answers our handshake in 815 ms on average, which is faster than 15% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.