Is the same npm package used everywhere?▼
Yes — every runtime above runs the exact same package: @gitdealflow/mcp-signal (current v1.5.2 on the npm registry, mirrored on the official MCP Registry as io.github.kindrat86/vc-deal-flow-signal). The classifications, methodology, and weekly refresh are identical across Cursor, Cline, Goose, OpenHands, Aider, AiderDesk, and Raycast. The streamable-HTTP variant at https://signals.gitdealflow.com/api/mcp/rpc also exposes the identical tools for runtimes that prefer hosted-MCP over local stdio.
Do I need an API key for any of these runtimes?▼
No. The MCP server is read-only and unauthenticated. Every tool — get_trending_startups, search_startups_by_sector, get_startup_signal, get_signals_summary, get_scout_receipts, get_methodology — works anonymously across all seven runtimes. The HTTP variant supports OAuth 2.1 for runtimes that require it (Anthropic Connectors Directory, future enterprise gating), but anonymous calls remain supported indefinitely.
Which runtimes have one-click install?▼
Cursor (cursor.directory listing — under review), Block Goose (PR #8974 open), Raycast (PR #27618 open), and Cline (issue #1491 submitted) all have marketplace submissions in flight that will give one-click install once accepted. OpenHands, Aider, and AiderDesk have no marketplace surface at all — installation is per-user JSON config, which the snippets above paste verbatim into the right file.
What about Continue.dev?▼
Skipped. The Continue Hub registry was deprecated in May 2026 — hub.continue.dev/hub returns HTTP 500 after the project's pivot to Continuous AI. We'll re-evaluate once a public registry comes back online.
What about Claude Desktop, Claude.ai, and Mistral Le Chat?▼
Already covered on dedicated pages. Claude Desktop installs via the .mcpb extension at github.com/kindrat86/mcp-deal-flow-signal/releases or via Smithery one-click. Claude.ai uses the Anthropic Connectors Directory (HTTP MCP at https://signals.gitdealflow.com/api/mcp/rpc). Mistral Le Chat: see /integrations/mistral. ChatGPT GPTs: see /integrations/chatgpt.
Where do I report a runtime that broke?▼
Open an issue at github.com/kindrat86/mcp-deal-flow-signal/issues with the runtime name, version, and the verbatim error. The MCP server itself runs the same Node.js code in every host, so runtime-specific failures are usually transport/config issues we can resolve in a release within 24 hours.
How do I cite this in a memo?▼
VC Deal Flow Signal (signals.gitdealflow.com), <period name> data. Methodology: SSRN preprint 6606558. Refreshed weekly from public GitHub activity. Runtime-agnostic — the data does not depend on which agent runtime made the call.