Loading...
Add the VC Deal Flow Signal MCP server to your Mistral Le Chat workspace as a Custom MCP Connector in under two minutes. Public Streamable HTTP endpoint, no authentication, six read-only tools for venture-backed startup engineering signals across 20 sectors. Once an admin installs the connector, every teammate can ask Le Chat about breakout startups directly in chat.
https://signals.gitdealflow.com/api/mcp/rpcIn Le Chat, open the side panel, expand the Intelligence menu, and click Connectors.
Top-right of the Connectors page, click + Add Connector. In the dialog, choose the Custom MCP Connector tab.
Connector name: vc-deal-flow-signal (no spaces). Connection server: https://signals.gitdealflow.com/api/mcp/rpc. Description (optional): VC Deal Flow Signal — engineering acceleration signals across 20 sectors. Authentication: No Authentication (the server is public, read-only).
Le Chat auto-detects the auth mode, validates the handshake, and lists six tools. Approve the connector and it appears in your organisation's connector list, ready for any teammate to use.
Try: 'Use vc-deal-flow-signal to show the top 10 trending AI/ML startups by engineering acceleration this week.' Le Chat picks the right tool, fetches live data, and renders the result inline.
get_trending_startupsTop 20 startups across all 20 sectors ranked by GitHub engineering acceleration.
search_startups_by_sectorEvery tracked startup in one of 20 sectors, ranked by acceleration. Sectors enumerated.
get_startup_signalFull signal profile for a single startup: velocity, contributor delta, repo expansion, classification.
get_signals_summaryDataset snapshot — current period, counts, refresh date, format URLs, citation.
get_scout_receiptsGitHub Scout Score for any user — backwards-looking proof-of-taste from validated unicorns.
get_methodologyHow signals are sourced, computed, and classified, with documented limitations.
All tools are read-only, idempotent, and closed-world (no external crawl on demand). Annotations exposed via the MCP tools/list response.
Custom MCP Connectors are available on Le Chat plans that surface the Connectors panel. Adding a custom connector is admin-gated inside an organisation, so you need workspace admin rights to install it for your team — but once installed, every teammate can use it.
Streamable HTTP, the current MCP standard. Endpoint: https://signals.gitdealflow.com/api/mcp/rpc. Protocol version 2025-06-18. Both JSON and Server-Sent Events response modes are supported via the Accept header negotiation. The server also publishes serverInfo with icons, websiteUrl, and capabilities so Le Chat can render the connector card correctly.
No. The MCP server is fully public and read-only. All six tools query a pre-computed weekly dataset of GitHub commit-velocity signals — no PII, no rate-limited downstream APIs, no credentials needed. Mistral's auto-detection picks up No Authentication and skips the OAuth flow.
Six tools backed by a 985-row dataset refreshed weekly: trending startups across 20 sectors, sector-filtered rankings, single-startup deep lookups, dataset metadata, GitHub Scout Score for any user, and the full methodology. Every record includes commit velocity (14-day window), contributor delta, repo expansion, sector, and signal classification (Engineering Acceleration / Contributor Growth / Infrastructure Buildout).
Mistral's Custom MCP Connectors statically capture the tool list at install time rather than re-discovering on every call. The VC Deal Flow Signal server publishes a stable tool surface (the same six tools shipped via npm and Smithery). When new tools land in a major server version, reconnect the connector to refresh the static list.
Three differences. (1) The Custom Connector route uses the live HTTP endpoint, so you always get the latest server version without re-running npx. (2) It works for every teammate in your Mistral workspace once an admin installs it once, not per-machine. (3) It doesn't need Node.js installed locally. The npm package (@gitdealflow/mcp-signal) is still the right choice for Claude Desktop, Cursor, Cline, and Continue — clients that prefer stdio over remote HTTP.
Yes. The same server is published three ways: (a) npm @gitdealflow/mcp-signal for stdio clients, (b) Smithery one-click install at smithery.ai/server/kindrat86/vc-deal-flow-signal (verified, 98/100 quality score), and (c) the Streamable HTTP endpoint at signals.gitdealflow.com/api/mcp/rpc for Mistral Le Chat and any other Streamable HTTP-compatible client. Pick whichever transport your client supports.
The same server ships three ways:
npx -y @gitdealflow/mcp-signal.https://signals.gitdealflow.com/api/mcp/rpc — public Streamable HTTP endpoint for Mistral Le Chat and any other Streamable HTTP-compatible client.Email signal@gitdealflow.com — replies within 24 hours, EU business time. Common gotchas (workspace admin rights, server URL trailing slash, Mistral region) are documented in the FAQ above.
Email support