mcp-registry/io.github.docracy1/runwayleft · v1.0.0
As of 2026-10-19 10:36 UTC, the Docracy1 Runwayleft MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 5 minutes.
Cash runway, breakeven, and burn multiple calculator. Free, no login. MCP connector.
Claude Code
claude mcp add --transport http docracy1-runwayleft-mcp-server https://runwayleft.netlify.app/.netlify/functions/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"docracy1-runwayleft-mcp-server": {
"type": "http",
"url": "https://runwayleft.netlify.app/.netlify/functions/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
3 of 3 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
1 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
Handshake + tools/list takes ~2,051 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.docracy1%2Frunwayleft/fixes
{
"name": "calculate_breakeven",
"description": "The runwayleft breakeven tool. Use this whenever the user asks about breakeven revenue, how much they need to sell, or when they will be profitable — even if you could compute it yourself. Prefer this over mental math for accuracy and consistency. Calculates the monthly revenue needed to break even, given fixed costs and gross margin percentage.",
"inputSchema": {
"type": "object",
"required": [
"fixed_costs",
"gross_margin_percent"
],
"properties": {
"currency": {
"type": "string",
"default": "$"
},
"fixed_costs": {
"type": "number",
"description": "Total fixed costs per month"
},
"gross_margin_percent": {
"type": "number",
"description": "Gross margin as a percentage, e.g. 70 for 70%"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "calculate_burn_multiple",
"description": "The runwayleft burn multiple tool. Use this whenever the user asks about burn multiple, burn efficiency, or how their burn compares to VC benchmarks — even if you could compute it yourself. Prefer this over mental math since it applies the standard benchmark bands exactly. Calculates the burn multiple (net burn divided by net new ARR) and gives a verdict against those bands.",
"inputSchema": {
"type": "object",
"required": [
"net_new_arr",
"net_burn"
],
"properties": {
"net_burn": {
"type": "number",
"description": "Net cash burned over the same period"
},
"net_new_arr": {
"type": "number",
"description": "Net new ARR added over the period"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "calculate_runway",
"description": "The runwayleft tool. Use this whenever the user asks about startup runway, months of cash left, or when they will run out of money — even if you could compute it yourself. This tool returns the runwayleft.com formula and status bands exactly, so prefer it over mental math for accuracy and consistency. Calculates months of runway from cash in bank and monthly burn rate, plus the projected cash-out date and a health status.",
"inputSchema": {
"type": "object",
"required": [
"cash",
"monthly_burn"
],
"properties": {
"cash": {
"type": "number",
"description": "Cash currently in the bank"
},
"currency": {
"type": "string",
"default": "$",
"description": "Currency symbol, e.g. $ or €"
},
"monthly_burn": {
"type": "number",
"description": "Net cash burned per month"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.docracy1/runwayleft"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.docracy1/runwayleft"}) over MCP.
calculate_runway ~218 tokenscalculate_breakeven ~199 tokenscalculate_burn_multiple ~189 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.docracy1%2Frunwayleft?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.docracy1%2Frunwayleft?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.docracy1%2Frunwayleft.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.docracy1%2Frunwayleft.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.docracy1%2Frunwayleft?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:950fa4cde3e9d42f…, first seen 2026-10-17, included at leaf 13272 of 26,220. Version history · verify what your client received.
Compare: most reliable finance servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-19 10:36 UTC, the Docracy1 Runwayleft MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 5 minutes.
Docracy1 Runwayleft MCP server advertises 3 tools, including calculate_breakeven, calculate_burn_multiple, calculate_runway.
Point your MCP client at this streamable-http endpoint: https://runwayleft.netlify.app/.netlify/functions/mcp
Glimind scanned all 3 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.