Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Worth Leaving

REMOTE · WORTHLEAVING.COM

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

Available components

+3 this week 75 Trust /100

Last scanned (58 minutes ago)

Scores higher than 62% of remote servers

Reachable. Last reached 22 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 90% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 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. See how to fix → Fail
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +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.

  • 18 Nov 26 +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.

  • 16 Nov 26 +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.

  • 14 Nov 26 +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.

  • 12 Nov 26 +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.

  • 10 Nov 26 +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.

  • 9 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 8 Nov 26 69

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Nov 2026 · Probed https://worthleaving.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=worthleaving.com CN=YR1,O=Let's Encrypt,C=US 27 Oct 2026 25 Jan 2027 RSA 2048 SHA256-RSA 68def433bd9626d4721e9aa4b424db4b362
SANs: worthleaving.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of worthleaving.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
worthleaving.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://worthleaving.com/api/mcp Verified 200
http (plaintext) http://worthleaving.com/api/mcp HTTPS enforced 308 https://worthleaving.com/api/mcp
MCP tools · 2 exposed · ~632 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_market_base_pay ~272

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.

NameTypeReqDescription
basenumber–Current annual base salary in dollars; with it the result says how it compares to the median
levelstringyesLevel id: junior (Junior), mid (Mid), senior (Senior), staff (Staff), principal (Principal or above)
metrostringyesMetro id such as "us-sfo", "us-sea", "us-nyc"; "remote-us" has no data
rolestringyesRole 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…

No output schema declared.

No examples provided.

compute_walk_away_verdict ~360

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.

NameTypeReqDescription
currentobjectyesThe current role
filingstring––
leaveDatestringyesThe 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.
privateHaircutnumber–Default discount for private grants that carry none; 0.3 if omitted
ratingsobject–How the offer compares to the current role on each factor, -2 (much worse) to 2 (much better)

No output schema declared.

No examples provided.

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.

remote · worthleaving.com

# add to Claude Code
claude mcp add --transport http com-worthleaving-verdict 'https://worthleaving.com/api/mcp'
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.