# Worthune Verified Financial Models (remote · worthune.com)

61 verified financial models and a household planning engine: 20 MCP tools, 6 keyless, specs cited.

- Trust score: 80/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

> **Recent critical change**: Authorization (2026-09-07). See the changelog below before you install this server.

## Components

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

## Channel facts

- Endpoint: `https://worthune.com/api/mcp/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.8.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-09-24.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (archive_household).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3031 tokens (~151/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 71% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Worthune Verified Financial Models MCP server?

Worthune Verified Financial Models is a hosted endpoint at https://worthune.com/api/mcp/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-worthune-models 'https://worthune.com/api/mcp/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-worthune-models": {
      "url": "https://worthune.com/api/mcp/mcp"
    }
  }
}
```

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-worthune-models:
    url: "https://worthune.com/api/mcp/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-worthune-models": {
      "type": "http",
      "url": "https://worthune.com/api/mcp/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-09-13 (score 80, +1)

- [security] Stability: 0.97 → pass

### 2026-09-11 (score 79, +1)

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

### 2026-09-09 (score 78, +1)

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

### 2026-09-07 (score 77, −6)

- [critical regression] Authorization: partial → fail
- [security] New tool “archive_household”, which the server declares destructive
- [functional regression] Schema quality: 2404 → 3031
- [functional] Server version: 1.7.0 → 1.8.0
- [functional] New tool “get_decision”
- [functional] New tool “get_household_picture”
- [functional] New tool “list_decisions”
- [functional] New tool “list_households”
- [cosmetic] “create_household” added an optional parameter “importKey”
- [cosmetic] “project_household” added an optional parameter “policy”
- [cosmetic] “get_model_contract” reworded the description of “api_key”

### 2026-09-06 (score 83, +1)

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

### 2026-09-04 (score 82, +1)

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

### 2026-09-02 (score 81, 0)

- [functional regression] Schema quality: 2004 → 2404
- [functional] New tool “list_example_households”
- [functional] New tool “try_household_projection”

### 2026-09-01 (score 81, +1)

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

## MCP tools (20)

### `list_models` (~50 tokens)

List Worthune's Concordance-tested financial calculation models (an independent second implementation must agree with the engine, per the published spec). Returns model names and spec versions. Call get_model_contract before running a model.

### `get_model_contract` (~154 tokens)

Get a model's machine-readable contract: required inputs with types and valid domains, cross-field constraints, sentinel-value meanings, and the government constants (with sources) the model uses. Set include_spec to also receive the full specification markdown (exact formulas, assumptions, exclusions, known issues).

Input parameters:

- `api_key` (string): Worthune API key (wk_…) — required for include_spec on non-sample models; or send it once as an Authorization: Bearer header.
- `include_spec` (boolean): Also return the full spec markdown (default false). Public for the free-sample models; other models need api_key.
- `model` (string, required): Model name from list_models, e.g. 'relocation'

### `run_model` (~154 tokens)

Run a Concordance-tested calculation model. Inputs must satisfy the contract from get_model_contract (all fields required, values inside their domains — out-of-domain requests are rejected, never clamped). The response echoes inputs, spec version, assumptions, triggered sentinels, and sourced constants; outputs are exactly what the engine computed, untouched. Share the matching interactive calculator with users: https://worthune.com/scenarios/<model> for scenario models.

Input parameters:

- `api_key` (string): Worthune Pro API key (wk_…). Required for models outside the free sample; the free models run without one.
- `inputs` (object, required): Model inputs per the contract's domains
- `model` (string, required): Model name from list_models

### `verify_claim` (~192 tokens)

Verify claims about a model's outputs against the engine before presenting them to a user. Pass the model inputs plus one or more claims ({path, op, value}); each claim comes back verified, violated, or out-of-scope, with the engine's computed value as proof and a decision-record hash tying the verdict to this spec version and these inputs. Out-of-scope means the model does not compute the claimed quantity — this tool never guesses. Use it to check a number you are about to state; use run_model when you want the full output envelope.

Input parameters:

- `api_key` (string): Worthune Pro API key (wk_…). Required for models outside the free sample; the free models verify without one.
- `claims` (array, required): Claims to check (max 50)
- `inputs` (object, required): Model inputs per the contract's domains
- `model` (string, required): Model name from list_models

### `create_household` (~153 tokens)

Create a persistent household resource from a household-schema document (docs/household-schema-spec.md: members, accounts by tax wrapper, liabilities, income and expense streams). Validation rejects with JSON-path errors — fix the payload in one pass. Returns the household id to use with get/replace/project_household.

Input parameters:

- `api_key` (string): Worthune API key (wk_…)
- `household` (object, required): Household-schema document
- `importKey` (string): Your own stable id for this household: a retry with the same importKey returns the household already created, never a twin (same contract as POST /api/v1/households).
- `label` (string): Your own name for the household

### `get_household` (~49 tokens)

Fetch a stored household document and its metadata by id.

Input parameters:

- `api_key` (string): Worthune API key (wk_…)
- `id` (integer, required): Household id from create_household

### `list_households` (~102 tokens)

List the organization's stored households — id, label, advisorRef, version, status, when it was last computed — without the documents (get_household returns one in full). Defaults to active households; GET /api/v1/households returns every status — pass status: "all" for the same listing.

Input parameters:

- `api_key` (string): Worthune API key (wk_…)
- `status` (string): Filter by status (default: active)

### `archive_household` (~74 tokens)

Archive a stored household (never deleted: the row stays readable, leaves the active-household meter, and stops accepting writes or projections). The same operation as DELETE /api/v1/households/{id}.

Input parameters:

- `api_key` (string): Worthune API key (wk_…)
- `id` (integer, required)

### `list_decisions` (~92 tokens)

The append-only history of coordination strategies run on a stored household, newest first — id, strategy, spec version, household version, record hash, when. Metadata only; get_decision returns one in full. Same as GET /api/v1/households/{id}/decisions.

Input parameters:

- `api_key` (string): Worthune API key (wk_…)
- `id` (integer, required): Household id

### `get_decision` (~114 tokens)

One stored decision in full: the decision object as it was produced, the household version it ran against, and its evidence record with the hashed inputs — enough to re-verify it with /api/v1/records/verify or the SDKs' verifyRecord. Decisions stored before their inputs were retained are returned hash-only and say so. Same as GET /api/v1/decisions/{id}.

Input parameters:

- `api_key` (string): Worthune API key (wk_…)
- `decision_id` (integer, required)

### `get_household_picture` (~158 tokens)

One household, one picture: the balance sheet by wrapper and owner, income and spending this year, how current the last computation is against the engine's spec (the same drift reasons the weekly scan delivers), the newest decisions, and a data-quality report naming what is missing and what supplying it would unlock. Sums only — no new number of consequence; nothing is stored. Same as GET /api/v1/households/{id}/picture. Pass as_of (YYYY-MM-DD) to pin the date; it is echoed back.

Input parameters:

- `api_key` (string): Worthune API key (wk_…)
- `as_of` (string): YYYY-MM-DD or ISO timestamp; default now
- `id` (integer, required)

### `replace_household` (~93 tokens)

Full-document replace with optimistic concurrency: pass expectedVersion (from get_household) and a stale write loses cleanly with the current version instead of clobbering a concurrent change.

Input parameters:

- `api_key` (string): Worthune API key (wk_…)
- `expectedVersion` (integer)
- `household` (object, required): Replacement household-schema document
- `id` (integer, required)
- `label`

### `patch_household` (~177 tokens)

Apply a collection-level delta to a stored household without resending the whole document: set scalars (filingStatus, state), upsert entries by id (replace or append), remove entries by id. expectedVersion (from get_household) is REQUIRED — a delta is only meaningful against a version you have read. The merged result is validated in full; a delta can never produce an invalid household.

Input parameters:

- `api_key` (string): Worthune API key (wk_…)
- `expectedVersion` (integer, required)
- `id` (integer, required)
- `remove` (object): Collection → ids to remove
- `set` (object): Scalar fields: { filingStatus?, state? } (state: null clears it)
- `upsert` (object): Collection → entries with ids: replace matching ids, append new ones

### `project_household` (~193 tokens)

Run the deterministic multi-year projection on a stored household — income, RMDs, federal + covered state tax, expenses, amortization, cash flow, net worth per year — optionally with seeded Monte Carlo (same seed, same result). Assumptions: pass your own, pin a profile by id+version, or omit both for the labeled illustrative default; the response always names its assumptionsSource. Every simplification that fired is listed in projection.assumptionsApplied — show your work.

Input parameters:

- `api_key` (string): Worthune API key (wk_…)
- `assumptions` (object)
- `horizon` (object, required)
- `id` (integer, required)
- `monteCarlo` (object)
- `policy` (object): Same shape as try_household_projection; applies to the deterministic run and every Monte Carlo path, and is hashed into the record.
- `profile` (object)

### `list_example_households` (~121 tokens)

Twelve FICTIONAL households, each built to exercise a different part of the planning engine — accumulation, a Roth conversion window, drawdown on a low-basis portfolio, spousal Social Security coordination, running out of money, negative amortization, and more. Use one as a starting point for try_household_projection, or as a worked shape when helping someone describe their own household. Pass an id to get the full document back. No API key required.

Input parameters:

- `id` (string): An example id; omit to list all twelve with their summaries.

### `try_household_projection` (~279 tokens)

Run the deterministic multi-year household projection on a document you pass in — income, RMDs, Roth conversions, federal and covered-state tax, expenses, amortization, the tax-grossed-up deficit draw, and net worth per year — optionally with a seeded Monte Carlo. NO API KEY, and NOTHING IS STORED: no household is created, no id issued, no record kept. The response carries every simplification that fired in projection.assumptionsApplied and an evidence record whose hash reproduces on an identical document, so you can show your work. Use list_example_households for a starting shape. For a household that persists — with an id, bulk import, webhooks and drift detection — see create_household, which takes a key.

Input parameters:

- `assumptions` (object, required): Required here: this surface has no org profile to fall back on.
- `horizon` (object, required)
- `household` (object, required): A household document: { schemaVersion, filingStatus, state?, members[], accounts[], liabilities[], incomes[], expenses[] }. It has no name field and no account numbers by design. Any expense `label`…
- `monteCarlo` (object): Simulations are clamped to 500 on this keyless surface, and the clamp is reported back.
- `policy` (object)

### `import_households` (~229 tokens)

Migrate a book (WS3.5): import up to 200 households in one call, with dryRun: true validating everything and writing NOTHING — iterate until the per-row, per-field report is clean, then run for real. Two shapes: households[] of { importKey, label?, household } documents, or template + records — a declarative mapping template (docs/data-migration.md) executed deterministically over raw exported records, so YOU draft the small reviewable template and the engine does the transcription. importKey is the caller's stable id: re-runs are idempotent (already-imported keys skip and report their householdId); imports never overwrite.

Input parameters:

- `api_key` (string): Worthune API key (wk_…)
- `dryRun` (boolean): Validate everything, write nothing
- `households` (array): Direct rows: { importKey, label?, household }
- `records` (array): Raw exported records, column → string cell
- `template` (object): Mapping template (templateVersion 0.1.0) for the records path

### `draft_import_mapping` (~191 tokens)

WS3.5c: AI drafts the mapping; determinism executes it. Send up to 10 sample records from an export (column → string cell) and get back a DRAFT mapping template for import_households' template + records path. Three deterministic gates run before anything returns: strict JSON, the transcription guard (a numeric const anywhere in the draft is rejected — numbers bind to columns, never to values a model wrote), and the real import dry-run over your sample. Nothing is written. Review the template and the unmappedColumns honesty list, then run import_households yourself with dryRun: true over the full export.

Input parameters:

- `api_key` (string): Worthune API key (wk_…)
- `notes` (string): Context for the draft (what the export is, quirks)
- `sampleRecords` (array, required): 1-10 sample records, column → string cell

### `narrate_decision` (~156 tokens)

The Verified Narrative: client- or advisor-ready prose for a stored decision (decision_id) or an inline decision object. A model drafts the narrative FROM the decision; a deterministic gate then extracts every number in the draft and verifies each against the decision's own values — correctly-rounded restatements pass, invented numbers reject the draft whole (one retry, then refusal; a narrative is never patched). The response reports how many claims were checked.

Input parameters:

- `api_key` (string): Worthune API key (wk_…)
- `audience` (string): Default "client"
- `decision` (object): An inline decision object (validated first)
- `decision_id` (integer): A stored decision's id (from decide_household)

### `decide_household` (~300 tokens)

Run a Household Coordination Engine strategy on a stored household and get back a ranked decision object with evidence records. Strategies: withdrawal-sequencing (no params); roth-ladder (params.candidates: [{annualAmountUsd, years}]); ss-claiming (params.candidateAges?: {memberId: [ages 62-70]}); asset-location (params.taxRates: {marginalOrdinary, qualifiedAndLtcg} plus params.characteristics or params.illustrativeCharacteristics: true — the illustrative set is labeled not-a-recommendation and is never applied silently); tax-loss-harvesting (params.ordinaryMarginalRatePct, optional longTermRatePct and realizedGains); annual-gifting (params.doneeCount, params.years); pension-election (params.ownerId, startAge, discountRatePct, options — EPVs from the NCHS life table; adults need sex). Alternatives are ranked best-first by a checkable score under a named objective; deltas name their baseline; every projection-backed candidate links its own verifiable record; exclusions are stated in the notes.

Input parameters:

- `api_key` (string): Worthune API key (wk_…)
- `assumptions` (object)
- `horizon` (object, required)
- `id` (integer, required)
- `params` (object): Strategy-specific parameters (see the tool description)
- `profile` (object)
- `strategy` (string, required)

## Diagnostics

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

## Score history

- 2026-09-24: 80
- 2026-09-23: 80
- 2026-09-22: 80
- 2026-09-21: 80
- 2026-09-20: 80
- 2026-09-19: 80
- 2026-09-18: 80
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 80
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 78
- 2026-09-09: 78
- 2026-09-08: 77
- 2026-09-07: 77
- 2026-09-06: 83
- 2026-09-05: 82
- 2026-09-04: 82
- 2026-09-03: 81
- 2026-09-02: 81
- 2026-09-01: 81
- 2026-08-31: 80
- 2026-08-30: 80
- 2026-08-29: 79
- 2026-08-28: 79
- 2026-08-27: 81
- 2026-08-26: 81

## Common questions

### What is the Worthune Verified Financial Models MCP server?

Worthune Verified Financial Models is an MCP server listed in the public MCP registry as com.worthune/models. 61 verified financial models and a household planning engine: 20 MCP tools, 6 keyless, specs cited. This page covers its hosted endpoint (https://worthune.com/api/mcp/mcp).

### Is the Worthune Verified Financial Models MCP server safe to use?

Worthune Verified Financial Models scores 80 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 Worthune Verified Financial Models MCP server expose?

Worthune Verified Financial Models exposes 20 tools: list_models, get_model_contract, run_model, verify_claim, create_household, and 15 more. Their descriptions and schemas cost roughly 3,031 tokens of context every time the server is loaded.

### Does the Worthune Verified Financial Models MCP server require authentication?

No. We connected to Worthune Verified Financial Models without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Worthune Verified Financial Models MCP server still maintained?

Worthune Verified Financial Models is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://worthune.com/api/mcp/mcp
- Website: https://worthune.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-worthune-models/api-mcp-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-worthune-models/api-mcp-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-worthune-models/api-mcp-mcp