mcpbeat Sign in

GitDealFlow MCP Server

not responding

GitDealFlow is listed as active in the registry but did not answer our last check. It exposes 4 tools.

Track startup engineering acceleration from public GitHub data before funding rounds

Uptime history 48 days of history · worst day 0%
48 days agonow
6.6%
Uptime 24h
6 of 91 checks
4
Tools
read from the server
314 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 100

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 8 August 2026. No other catalogue keeps this.

16 Aug 11 tools disappeared compare_signals, get_deep_signal, get_diligence_dossier and 8 more
16 Aug 3 tools appeared list_cities, list_sectors, search_startups
16 Aug a tool changed the parameters it asks for get_startup_signal
16 Aug a tool changed version
15 Aug 11 tools appeared compare_signals, get_deep_signal, get_diligence_dossier and 8 more
15 Aug 3 tools disappeared list_cities, list_sectors, search_startups
15 Aug a tool changed the parameters it asks for get_startup_signal
15 Aug a tool description was rewritten get_startup_signal
15 Aug a tool changed version
10 Aug 14 tools disappeared25 times that day compare_signals, get_deep_signal, get_diligence_dossier and 11 more
and 53 more, back to 8 August 2026

GitDealFlow does not always answer

Over the last week it answered 4.7% 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 14 min ago.

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

Available tools 4

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

cities
list_cities
List all tracked cities with startup counts.
sectors
list_sectors
List all tracked sectors with startup counts.
startup
get_startup_signal
Get engineering momentum signal for a specific startup.
startups
search_startups
Search tracked startups by sector, city, or keyword.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

compare_signals
removed 16 Aug 2026
get_deep_signal
removed 16 Aug 2026
get_diligence_dossier
removed 16 Aug 2026
get_methodology
removed 16 Aug 2026
get_scout_receipts
removed 16 Aug 2026
get_signals_summary
removed 16 Aug 2026
get_trending_startups
removed 16 Aug 2026
predict_funding
removed 16 Aug 2026
search_startups_by_sector
removed 16 Aug 2026
share_result
removed 16 Aug 2026
shortlist_signals
removed 16 Aug 2026

Endpoints

URLTransportStateLatencyChecked
https://gitdealflow.com/api/mcp streamable-http answering 97 ms 14 min ago

Alternatives to GitDealFlow

same job, measured the same way
GitDealFlow — GitHub signals for startup investors
by kindrat86

GitHub engineering acceleration signals for venture deal flow across 15 sectors.

102 installs/wk 12 tools local only
Standup from your activity
by sathvic-kollu

Generate your daily standup from real GitHub, Jira, Linear, and Slack activity.

29 installs/wk local only
StarHunt
by getstarhunt

Find engineers by what they build on GitHub. Search by technology, location and role.

answering
StarHunt
by getstarhunt

Hiring developers? Find and source software engineers by what they build on GitHub.

answering
Data-grounded sprint retro
by sathvic-kollu

Data-grounded sprint retrospectives from your Jira, GitHub, and Slack activity.

32 installs/wk local only
bounty-mcp
by weiseer

Live coding-bounty deal-flow from verified-escrow GitHub bounties for AI agents.

43 installs/wk local only
Leakguard MCP
by doazvjettu

Static analyzer flagging lookahead bias & data leakage in ML/trading code before backtest.

85 installs/wk local only
C
Developer Tools MCP Server
by thenextgennexus

Search GitHub, npm, PyPI, StackOverflow, ArXiv from one MCP — built for coding agents.

7 tools answering

GitDealFlow — questions

Answers built from our own checks of this server.

What can GitDealFlow do?
It exposes 4 tools, read directly from the server on our last check. Among them: get_startup_signal, list_cities, list_sectors, search_startups. 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 GitDealFlow working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 6 of 91 checks got a reply (6.6%), average response time 314 ms. The bar chart above shows every period we have measured.
Did GitDealFlow ever remove tools?
Yes. compare_signals, get_deep_signal, get_diligence_dossier, get_methodology and 7 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
The registry lists GitDealFlow 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 GitDealFlow?
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 GitDealFlow need an API key?
No. GitDealFlow completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is GitDealFlow?
It answers our handshake in 314 ms on average, which is faster than 49% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.