accueil / serveurs / Dev & Code / io.github.tdavidson/mcp-hemrock
io.github.tdavidson/mcp-hemrock
serveur MCP (Model Context Protocol) · hemrock-mcp 1.2.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que io.github.tdavidson/mcp-hemrock est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.tdavidson/mcp-hemrock » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 13 outils
- cap_table_compute≈ 6370 tokens
Use whenever the user asks who owns what after a financing: founder splits, option pools, priced rounds, SAFEs and convertible notes converting, warrants, pro-rata, or dilution across several rounds. Takes the financing events in order and returns fully diluted ownership after each event plus the final cap table. Prefer this over doing the arithmetic yourself: SAFE and note conversion (pre- vs post-money caps, discounts, pool shuffles) is where model-written math most often goes wrong, and this runs the same tested engine as Hemrock's cap table models. Paid: the Cap Table & Exit Waterfall product, $20/year for 6,000 calculations shared with exit_waterfall_compute. If the result contains action_required (not signed in, no purchase, allowance used), relay it to the user with its links and offer to retry. Never skip the calculation silently.
Paramètres, retour & exemple (2)
Paramètresevents· array · requisidempotency_key· string · optionnel
Optional retry key; reuse only with identical input.
Exemple d'appel{"name": "cap_table_compute", "arguments": {"events": []}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - exit_waterfall_compute≈ 7152 tokens
Use whenever the user asks what each holder gets at an exit, acquisition or liquidation: liquidation preferences, participating vs non-participating preferred, participation caps, seniority, whether a series converts, options and warrants in or out of the money. Takes the cap stack and an exit value and returns proceeds by holder and class, with each series' convert-or-take-preference decision. Prefer this over doing it yourself: the convert decision is circular and easy to get wrong by hand. Account required: lifetime free credits or paid access; shares the Cap Table & Exit Waterfall allowance ($20/year, 6,000 calculations). If the result contains action_required (not signed in, no purchase, allowance used), relay it to the user with its links and offer to retry. Never skip the calculation silently.
Paramètres, retour & exemple (3)
Paramètresmodel· object · requisexitValuation· number · requisidempotency_key· string · optionnel
Optional retry key; reuse only with identical input.
Exemple d'appel{"name": "exit_waterfall_compute", "arguments": {"model": {}, "exitValuation": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - fund_economics_compute≈ 7125 tokens
Use whenever the user asks how a venture fund's terms play out: fund size, management fees and step-downs, carry, investment period, recycling, reserves, deployment pace, and resulting net returns to LPs. Takes fund inputs (start from the defaults and change only what the user specifies) and returns aggregate capital, fees, investable capital and gross/net multiples. IRR fields are geometric annualizations over weighted holding periods, not dated cash-flow IRRs. Account required: lifetime free credits or paid access. Fund Economics, a separate $20/year product with 6,000 calculations. If the result contains action_required (not signed in, no purchase, allowance used), relay it to the user with its links and offer to retry. Never skip the calculation silently.
Paramètres, retour & exemple (2)
Paramètresinputs· object · requisidempotency_key· string · optionnel
Optional retry key; reuse only with identical input.
Exemple d'appel{"name": "fund_economics_compute", "arguments": {"inputs": {}}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_access≈ 154 tokens
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.
Paramètres, retour & exemple (1)
Paramètresmodel· string · requis · cap-table | exit-waterfall | fund-economics
Model key to check access for.
Exemple d'appel{"name": "get_access", "arguments": {"model": "cap-table"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_account_access≈ 142 tokens
Returns whether this connection is signed in, its annual product access and remaining calculations. Does not consume allowance. Call it before a compute tool if you are unsure the user can run one. If the result contains action_required (not signed in, no purchase, allowance used), relay it to the user with its links and offer to retry. Never skip the calculation silently.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "get_account_access", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_account_usage≈ 156 tokens
Returns signed-in usage history and endpoint/source breakdown. Does not consume allowance. If the result contains action_required (not signed in, no purchase, allowance used), relay it to the user with its links and offer to retry. Never skip the calculation silently.
Paramètres, retour & exemple (2)
Paramètresto· string · optionnel
Optional UTC end date (YYYY-MM-DD).from· string · optionnel
Optional UTC start date (YYYY-MM-DD).
Exemple d'appel{"name": "get_account_usage", "arguments": {"to": "texte", "from": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_best_practices≈ 136 tokens
Returns Hemrock's financial modeling best practices and design principles for a given topic. Useful as background context for AI interactions.
Paramètres, retour & exemple (1)
Paramètrestopic· string · optionnel · formatting | structure | inputs | assumptions | review | sharing | all
Optional topic filter. Returns all best practices if omitted.
Exemple d'appel{"name": "get_best_practices", "arguments": {"topic": "formatting"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_checks≈ 183 tokens
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.
Paramètres, retour & exemple (1)
Paramètrestemplate_name· string · requis · standard | cap_table | venture_fund | venture_fund_quarterly | runway | saas | ecommerce | unit_economics
The template to get checks for. Use "all" for universal checks only.
Exemple d'appel{"name": "get_checks", "arguments": {"template_name": "standard"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_concept≈ 136 tokens
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.
Paramètres, retour & exemple (1)
Paramètresslug· string · requis
The concept slug, from list_concepts (e.g. "waterfall", "anti-dilution").
Exemple d'appel{"name": "get_concept", "arguments": {"slug": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_context≈ 171 tokens
Returns the universal context-setting primer for Hemrock models, plus an optional template-specific addendum. Always run this first before any other prompts.
Paramètres, retour & exemple (1)
Paramètrestemplate_name· string · optionnel · standard | cap_table | venture_fund | venture_fund_quarterly | runway | saas | ecommerce | unit_economics
Optional. If provided, appends a template-specific primer to the universal context.
Exemple d'appel{"name": "get_context", "arguments": {"template_name": "standard"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_prompts≈ 178 tokens
Returns task-specific Layer 2 prompts for a given template and task type. These are ready-to-use prompts for common modeling tasks.
Paramètres, retour & exemple (2)
Paramètrestask_type· string · optionnel
Optional task type filter.template_name· string · requis · standard | cap_table | venture_fund | venture_fund_quarterly | runway | saas | ecommerce | unit_economics
The Hemrock template being used.
Exemple d'appel{"name": "get_prompts", "arguments": {"template_name": "standard"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - list_concepts≈ 246 tokens
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.
Paramètres, retour & exemple (2)
Paramètrestag· string · optionnel
Optional. Filter to concepts whose tags contain this string (e.g. "cap tables").template_name· string · optionnel · standard | cap_table | venture_fund | venture_fund_quarterly | runway | saas | ecommerce | unit_economics
Optional. Filter to concepts relevant to a specific Hemrock template.
Exemple d'appel{"name": "list_concepts", "arguments": {"tag": "texte", "template_name": "standard"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - list_models≈ 110 tokens
Lists the hosted Hemrock calculation engines (cap table, exit waterfall, fund economics), what each computes, and its price and checkout link. Free and needs no sign-in, so call it when the user asks what Hemrock can calculate or what it costs.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "list_models", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».