# io.github.docracy1/runwayleft (remote · runwayleft.netlify.app)

Cash runway, breakeven, and burn multiple calculator. Free, no login. MCP connector.

- Trust score: 64/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `runwayleft.netlify.app`: 64/100 (this document), [markdown](https://verifymcp.io/servers/docracy1-runwayleft/netlify-functions-mcp.md), [page](https://verifymcp.io/servers/docracy1-runwayleft/netlify-functions-mcp)

## Channel facts

- Endpoint: `https://runwayleft.netlify.app/.netlify/functions/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 373 tokens (~124/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 88% of tool parameters carry a description.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http docracy1-runwayleft https://runwayleft.netlify.app/.netlify/functions/mcp
```

### Codex

```toml
[mcp_servers.docracy1-runwayleft]
url = "https://runwayleft.netlify.app/.netlify/functions/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "docracy1-runwayleft": {
      "type": "remote",
      "url": "https://runwayleft.netlify.app/.netlify/functions/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add docracy1-runwayleft --url https://runwayleft.netlify.app/.netlify/functions/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  docracy1-runwayleft:
    url: "https://runwayleft.netlify.app/.netlify/functions/mcp"
```

### Other

```json
{
  "mcpServers": {
    "docracy1-runwayleft": {
      "type": "http",
      "url": "https://runwayleft.netlify.app/.netlify/functions/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 63, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 61, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 59)

First indexed and scored.

## MCP tools (3)

### `calculate_runway` (~135 tokens)

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.

Input parameters:

- `cash` (number, required): Cash currently in the bank
- `currency` (string): Currency symbol, e.g. $ or €
- `monthly_burn` (number, required): Net cash burned per month

### `calculate_breakeven` (~124 tokens)

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.

Input parameters:

- `currency` (string)
- `fixed_costs` (number, required): Total fixed costs per month
- `gross_margin_percent` (number, required): Gross margin as a percentage, e.g. 70 for 70%

### `calculate_burn_multiple` (~114 tokens)

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.

Input parameters:

- `net_burn` (number, required): Net cash burned over the same period
- `net_new_arr` (number, required): Net new ARR added over the period

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/docracy1-runwayleft/netlify-functions-mcp#diagnostics

## Score history

- 2026-08-03: 64
- 2026-08-02: 63
- 2026-08-01: 63
- 2026-07-31: 63
- 2026-07-30: 61
- 2026-07-29: 61
- 2026-07-28: 61
- 2026-07-27: 60
- 2026-07-26: 59

## Links

- Remote endpoint: https://runwayleft.netlify.app/.netlify/functions/mcp
- Repository: https://github.com/docracy1/runwayleft
- Changelog RSS feed: https://verifymcp.io/servers/docracy1-runwayleft/netlify-functions-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/docracy1-runwayleft/netlify-functions-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/docracy1-runwayleft/netlify-functions-mcp
