Three ways to build on top of VC Deal Flow Signal: an MCP server for AI assistants, raw JSON and CSV endpoints for automation, and an OpenAPI schema for generating typed clients. If you are here from an AI or agent workflow, this page should take you from machine-readable access into the proof and buyer pages that explain what the signal is worth.
Start with the highest-intent routes
Use this page if you want the full developer surface. But if your real question is builder fit, install path, or per-request pricing, start with the sharper entry points first.
Quote-ready takeaway
GitDealFlow is useful to developers because it exposes startup-signal data in machine-readable formats an agent can query directly without private API friction.
If you cite this page externally, use the takeaway above with the page URL and then route technical readers into the MCP or OpenAPI sections below.
The Model Context Protocol server for VC Deal Flow Signal. Works with Claude Desktop, Cursor, Windsurf, Continue, and any MCP-compatible client.
Install
Claude Desktop config
{
"mcpServers": {
"vc-deal-flow-signal": {
"command": "npx",
"args": ["-y", "@gitdealflow/mcp-signal@latest"]
}
}
}Available tools
get_trending_startupsTop breakout startups this week across all sectors, ranked by signal strength.
get_signals_summaryAggregate signal distribution by sector and signal type for the current period.
get_startup_signalDetailed engineering signal for a specific startup by name or GitHub org.
search_startups_by_sectorFilter startups by sector (AI/ML, enterprise SaaS, fintech, dev tools, etc.).
get_scout_receiptsScore a developer’s public taste: which now-validated companies they backed early, before everyone else noticed.
get_methodologyFull methodology: data sources, metric definitions, and signal classification rules.
Six read tools, free forever. The paid get_deep_signal tool (scored, memo-grade output) is separate — see agent credits below.
Public, no-auth endpoints for the current-period signal set. Cached for one hour, CORS enabled.
| Endpoint | Format | Description |
|---|---|---|
/api/signals.json | JSON | Full current-period signal set with enrichment fields. |
/api/signals.csv | CSV | Flat CSV for spreadsheets, CRM import, or BI tools. |
/api/openapi.json | OpenAPI 3.1 | OpenAPI schema — generate typed clients in any language. |
/api/changelog.json | JSON | Data changelog: periods, refresh dates, sector counts. |
/feed.xml | RSS 2.0 | Weekly signal feed with enriched content:encoded. |
/llms.txt | Text | LLM-friendly site map for AI assistants. |
Example: fetch current signals
The free MCP tools and REST endpoints listed above stay free forever. For agents that need scored, ranked, comparable-aware output — memo-grade signal — the new get_deep_signal tool is priced per-request.
Starter pack: 100 credits
€19 · €0.19/call
GITDEALFLOW_API_KEY) or straight HTTP (Authorization: Bearer …).Rate limits
Public endpoints are cached with s-maxage=3600 and served from the edge. There is no hard per-IP limit, but sustained high-frequency scraping should use the RSS feed or a cached local copy instead.
Licensing
Data is provided free for personal, research, and commercial use with attribution: link to signals.gitdealflow.com. Redistribution as a competing product or reselling the raw dataset requires written permission — contact signal@gitdealflow.com.
Attribution example
“Engineering signals from VC Deal Flow Signal”
If you are integrating VC Deal Flow Signal into an investor tool, CRM, or research workflow, the fastest way to get help is email. If you still need human-facing proof before integrating, read the research panel or the buyer's guide first.