# Worth Leaving (remote · worthleaving.com)

Unvested-equity math: the verdict, what leaving forfeits, and the number an offer has to beat.

- Trust score: 75/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- remote · `worthleaving.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-worthleaving-verdict/api-mcp.md), [page](https://verifymcp.io/servers/com-worthleaving-verdict/api-mcp)

## Channel facts

- Endpoint: `https://worthleaving.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.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-11-22.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 59/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 695 tokens (~347/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "check_market_base_pay" implies "pay" and declares readOnlyHint instead, contradicting what its own name says it does.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Worth Leaving MCP server?

Worth Leaving is a hosted endpoint at https://worthleaving.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-worthleaving-verdict 'https://worthleaving.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-worthleaving-verdict": {
      "url": "https://worthleaving.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-worthleaving-verdict": {
      "type": "http",
      "url": "https://worthleaving.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-worthleaving-verdict]
url = "https://worthleaving.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-worthleaving-verdict": {
      "type": "remote",
      "url": "https://worthleaving.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-worthleaving-verdict --url 'https://worthleaving.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-worthleaving-verdict:
    url: "https://worthleaving.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-worthleaving-verdict": {
      "Transport": "http",
      "Url": "https://worthleaving.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-worthleaving-verdict -t streamable-http -u 'https://worthleaving.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-worthleaving-verdict": {
      "type": "http",
      "url": "https://worthleaving.com/api/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-11-21 (score 75, +1)

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

### 2026-11-18 (score 74, +1)

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

### 2026-11-16 (score 73, +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-11-14 (score 72, +1)

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

### 2026-11-12 (score 71, +1)

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

### 2026-11-10 (score 70, +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-11-09 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 69)

First indexed and scored.

## MCP tools (2)

### `compute_walk_away_verdict` (~360 tokens)

Walk-away verdict

Call this instead of doing equity math. Give grant terms as written in the offer letter (shares or value, grant date, years, cliff, cadence monthly, quarterly or annual); do not pre-compute vest events. If the letter states per-year percentages, send them as yearlyPercents exactly as written. For options give shares, current price and strike. The offer is optional: with none, verdict is null, hasOffer is false, and the number to read is offerHasToBeat, what staying pays over the next year before tax. Returns the verdict, walkAwayCost (what leaving on the given date forfeits), nextVest, offerHasToBeat, leaveWindows (when leaving costs least in the two years after the leave date), levers (negotiation points the numbers support), the assumptions the engine filled in, and a shareable link that carries rounded bands only. If the person changes a price, a date or a term, call the tool again rather than scaling its numbers. For whether a base salary is at market for a role, level and metro, call check_market_base_pay.

Input parameters:

- `current` (object, required): The current role
- `filing` (string)
- `leaveDate` (string, required): The date the person would leave
- `offer`: The offer. Leave it out (or send null) when there is no offer yet; the result then gives the number an offer has to beat and no verdict.
- `privateHaircut` (number): Default discount for private grants that carry none; 0.3 if omitted
- `ratings` (object): How the offer compares to the current role on each factor, -2 (much worse) to 2 (much better)

### `check_market_base_pay` (~272 tokens)

Market base pay check

What a role and level earns in a US metro: median base salary from public US government data (H-1B filings and the BLS wage survey), with the middle half, the source and its date, and how a given base compares. Base pay only, equity and bonus excluded; an estimate, not a verdict, and it does not change compute_walk_away_verdict. Use it when the person asks whether their pay is at market, before or after the verdict.

Input parameters:

- `base` (number): Current annual base salary in dollars; with it the result says how it compares to the median
- `level` (string, required): Level id: junior (Junior), mid (Mid), senior (Senior), staff (Staff), principal (Principal or above)
- `metro` (string, required): Metro id such as "us-sfo", "us-sea", "us-nyc"; "remote-us" has no data
- `role` (string, required): Role id: swe (Software engineer), ml (ML or AI engineer), research (Research scientist), postdoc (Postdoc / academic to industry), data_sci (Data scientist), data_eng (Data engineer), sre (SRE or inf…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-worthleaving-verdict/api-mcp#diagnostics

## Score history

- 2026-11-22: 75
- 2026-11-21: 75
- 2026-11-20: 74
- 2026-11-19: 74
- 2026-11-18: 74
- 2026-11-17: 73
- 2026-11-16: 73
- 2026-11-15: 72
- 2026-11-14: 72
- 2026-11-13: 71
- 2026-11-12: 71
- 2026-11-11: 70
- 2026-11-10: 70
- 2026-11-09: 69
- 2026-11-08: 69

## Common questions

### What is the Worth Leaving MCP server?

Worth Leaving is an MCP server listed in the public MCP registry as com.worthleaving/verdict. Unvested-equity math: the verdict, what leaving forfeits, and the number an offer has to beat. This page covers its hosted endpoint (https://worthleaving.com/api/mcp).

### Is the Worth Leaving MCP server safe to use?

Worth Leaving scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Worth Leaving MCP server expose?

Worth Leaving exposes 2 tools: compute_walk_away_verdict, check_market_base_pay. Their descriptions and schemas cost roughly 632 tokens of context every time the server is loaded.

### Does the Worth Leaving MCP server require authentication?

No. We connected to Worth Leaving without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Worth Leaving MCP server still maintained?

Worth Leaving is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Worth Leaving MCP server?

VerifyMCP ran 13 checks on Worth Leaving, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://worthleaving.com/api/mcp
- Website: https://worthleaving.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-worthleaving-verdict/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-worthleaving-verdict/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-worthleaving-verdict/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-worthleaving-verdict/api-mcp
