mcpbeat

Hemrock MCP Server

io.github.tdavidson/mcp-hemrock
not responding

Hemrock MCP is listed as active in the registry but did not answer our last check. It exposes 11 tools.

Hemrock financial modeling prompts: context primers, task prompts, checks, and best practices.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 43 hours of history · worst hour 0%
43 hours agonow
0.0%
Uptime 24h
0 of 91 checks
11
Tools
read from the server
208 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

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

Available tools 11

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

access
get_access
Returns how to get access to a model engine: whether it is free, the price, and a checkout URL to purchase. Use when a compute tool returns a payment-required error, or to check access before running.
best
get_best_practices
Returns Hemrock's financial modeling best practices and design principles for a given topic. Useful as background context for AI interactions.
cap
cap_table_compute
Computes a cap table from a list of events (founders, priced rounds, SAFEs/notes, option pools, warrants). Returns per-round snapshots and the final ownership/dilution state. Requires a Hemrock API key with the Cap Table & Exit Waterfall product; without it you get a checkout URL. Call list_concepts/get_concept for the event structure.
checks
get_checks
Returns Layer 3 sanity-check and validation prompts — the 'where AI gets financial modeling wrong' guidance. Use these to audit AI-generated work or catch common modeling errors.
concept
get_concept
Returns the full text of a single Hemrock concept doc by slug. Use this to learn how a financial-modeling calculation actually works before building or auditing it. Get valid slugs from list_concepts.
concepts
list_concepts
Lists Hemrock financial-modeling concept docs — the methodology behind the math (exit waterfalls, anti-dilution, convertibles, cohorts, circular references, unit economics, and more). Returns a compact index of slugs, titles, and descriptions. Optionally filter by template_name or tag. Call get_concept to read the full text of any entry.
context
get_context
Returns the universal context-setting primer for Hemrock models, plus an optional template-specific addendum. Always run this first before any other prompts.
exit
exit_waterfall_compute
Computes an exit waterfall: distributes an exit valuation across the cap stack (preferences, participation, conversions, options, warrants). Requires a Hemrock API key with the Cap Table & Exit Waterfall product. Pass a "model" object and a numeric "exitValuation".
fund
fund_economics_compute
Computes venture fund economics from a set of inputs (committed capital, fees, deployment, carry tiers): returns capital calls, fees, NAV, and gross/net returns. Free — any valid Hemrock API key works. Pass an "inputs" object.
models
list_models
Lists the Hemrock financial-model engines callable over the API, with pricing and (for paid ones) a checkout URL. No API key needed — use this to discover what you can run and what it costs before authenticating.
prompts
get_prompts
Returns task-specific Layer 2 prompts for a given template and task type. These are ready-to-use prompts for common modeling tasks.

Endpoints

URLTransportStateLatencyChecked
https://mcp.hemrock.com/mcp streamable-http answering 208 ms 2 min ago

Hemrock MCP — questions

Answers built from our own checks of this server.

What can Hemrock MCP do?
It exposes 11 tools, read directly from the server on our last check. Among them: cap_table_compute, exit_waterfall_compute, fund_economics_compute, get_access, get_best_practices, get_checks and 5 more. 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 Hemrock MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 208 ms. The bar chart above shows every period we have measured.
Is Hemrock MCP still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists Hemrock MCP 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 Hemrock MCP?
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 Hemrock MCP need an API key?
No. Hemrock MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.