Hemrock MCP Server

by tdavidson Your server? Claim it

not responding

Hemrock MCP is listed as active in the registry but did not answer our last check. It exposes 13 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 51 days of history · worst day 0%

51 days agonow

2.2%

Uptime 24h

2 of 91 checks

Tools

read from the server

502 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 10

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

22 Sep 5 tool descriptions were rewritten cap_table_compute, exit_waterfall_compute, fund_economics_compute and 2 more

22 Sep 3 tools changed the parameters they ask for cap_table_compute, exit_waterfall_compute, fund_economics_compute

22 Sep 2 tools appeared get_account_access, get_account_usage

Hemrock MCP does not always answer

Over the last week it answered 0.9% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

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 13

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

account

get_account_access

Returns authenticated annual product access and remaining calculations. Does not consume allowance.

get_account_usage

Returns authenticated usage history and endpoint/source breakdown. Does not consume allowance.

access

get_access

Returns public access terms for an engine: product, annual price, billing period, annual allowance, and a customer checkout URL. This is informational and does not purchase or confirm account-specific access; use get_account_access for the authenticated account.

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 and consumes one successful calculation from the Cap Table & Exit Waterfall allowance. That product is $20/year for 6,000 calculations shared with exit waterfall. Requires an authenticated account with active access.

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 and consumes one successful calculation from the Cap Table & Exit Waterfall allowance. That $20/year product includes 6,000 calculations shared with cap table.

fund

fund_economics_compute

Computes venture fund economics and consumes one successful calculation from the Fund Economics allowance. Fund Economics compute is a separate $20/year product with 6,000 annual calculations.

models

list_models

Lists hosted Hemrock engines and their access terms. There are two independent $20/year compute products with 6,000 annual calculations each; cap table and exit waterfall share the Cap Table allowance. No authentication is required for this public catalog.

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

URL	Transport	State	Latency	Checked
https://mcp.hemrock.com/mcp	streamable-http	answering	337 ms	6 min ago

Alternatives to Hemrock MCP

same job, measured the same way

Financial Modeling Prep (fmpsdk)

by daxm

Financial Modeling Prep API as MCP tools — quotes, statements, prices, and ~240 endpoints.

182 installs/wk local only

Eqvitta MCP

by eqvitta

Eqvitta MCP: GST billing, ledgers, invoices, stock and financial reports for Claude.

303 installs/wk local only

Compute Finance Oracle

by compute-finance

Live AI compute pricing oracle — real-time LLM model prices across providers

225 installs/wk local only

Xero

by wyre-ai

MCP server for Xero accounting — contacts, invoices, payments, accounts, and financial reports.

local only

Xero

by wyre-technology

MCP server for Xero accounting — contacts, invoices, payments, accounts, and financial reports.

local only

Secapi

by secapi

SEC & financial-data MCP: filings, financials, ownership, factors, fund letters, prompts.

answering

Financial Modeling Prep MCP Server

by imbenrabi

MCP server for Financial Modeling Prep API with 250+ financial data tools

257 installs/wk local only

Xero

by mindstone

Xero MCP server for invoices, contacts, payments, quotes, and financial reports.

61 installs/wk local only

Hemrock MCP — questions

Answers built from our own checks of this server.

What can Hemrock MCP do?

It exposes 13 tools, read directly from the server on our last check. Among them: cap_table_compute, exit_waterfall_compute, fund_economics_compute, get_access, get_account_access, get_account_usage and 7 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 2 of 91 checks got a reply (2.2%), average response time 502 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 13 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Hemrock MCP?

It answers our handshake in 502 ms on average, which is faster than 31% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.