Marketing
intakra.com
Scores business-account fit and buying-signal evidence, and prepares why-now reviews from caller-supplied criteria.
ENDPOINT 1
https://intakra.com/mcp
MCP server metadata
- Name
- intakra-public-signals
- Version
- 1.0.0
Use only caller-supplied, non-confidential business evidence. Every score and why-now result is an unverified draft for human review. This server cannot access Intakra workspaces, research sources, draft outreach, spend money, persist data, or send anything.
Known tools 2
score_buying_signal_evidenceDeterministically score caller-supplied business-account fit and buying-signal evidence.
Inferred read-onlyprepare_why_now_reviewTurn caller-supplied fit criteria and business signals into reviewable why-now and fit guidance.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.intakra-public-signals]
url = "https://intakra.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"intakra-public-signals": {
"type": "http",
"url": "https://intakra.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: intakra-public-signals
Remote MCP URL: https://intakra.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"intakra-public-signals": {
"url": "https://intakra.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"intakra-public-signals": {
"type": "http",
"url": "https://intakra.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "intakra-public-signals",
"transport": "streamable-http",
"url": "https://intakra.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.