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.

Worthune Verified Financial Models

REMOTE · WORTHUNE.COM

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

Available components

0 this week 79 Trust /100

Last scanned (19 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Recent critical change

Authorization (7 Sept 2026). See the changelog before you install this server.

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 Security66
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 4794 tokens (~159/item across 30 items; 30 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 59% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 30 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 30 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 12 Oct 26 0
    • Tool “decide_household” rewrote its description, which is the text the model reads security
    • Tool “try_household_projection” rewrote its description, which is the text the model reads security
    • Schema quality: 3031 → 4794 ▼ functional
    • Tool coverage: 71% → 59% ▼ functional
    • Server version: 1.8.0 → 1.10.0 functional
    • New tool “answer_question” functional
    • New tool “create_mandate” functional
    • New tool “get_ledger” functional
    • New tool “get_mandate” functional
    • New tool “list_mandates” functional
    • New tool “list_proposals” functional
    • New tool “list_questions” functional
    • New tool “manage_preferences” functional
    • New tool “review_proposal” functional
    • New tool “run_mandate” functional
    • “try_household_projection” added an optional parameter “api_key” cosmetic
    • “try_household_projection” reworded the description of “monteCarlo” cosmetic
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 13 Sept 26 0
    • Stability: 0.97 → pass security
  • 7 Sept 26 0
    • Authorization: partial → fail ▼ critical
    • New tool “archive_household”, which the server declares destructive security
    • 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” functional
    • “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” cosmetic
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 21 Nov 2026 · Probed https://worthune.com/api/mcp/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=worthune.com CN=YR2,O=Let's Encrypt,C=US 29 Sept 2026 28 Dec 2026 RSA 2048 SHA256-RSA 65c9e1f27b0f9059fe56c7c2727a87293ce
SANs: worthune.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
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 secure

Validation of worthune.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
worthune.com. DS published 37436 8 Verified
worthune.com. Verified address RRset verified with the apex keys
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; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://www.google.com https://www.gstatic.com https://www.googletagmanager.com https://www.google-analytics.com https://www.recaptcha.net; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' data: https://fonts.gstatic.com; img-src 'self' data: blob: https:; connect-src 'self' https:; frame-src 'self' https://www.google.com https://www.recaptcha.net; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'self'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), browsing-topics=(), interest-cohort=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://worthune.com/api/mcp/mcp Verified 200
http (plaintext) http://worthune.com/api/mcp/mcp HTTPS enforced 308 https://worthune.com/api/mcp/mcp
MCP tools · 30 exposed · ~4,794 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
answer_question ~140

Answer one open question. value proposes the corrected field as a data-change proposal that an approver or owner must approve before anything is written; confirm: true records that the data is right, and the same check will not ask about the field again. Send exactly one of them. Developer, approver or owner key. Refused when the household changed since the question was asked. Same as POST /api/v1/questions/{id}/answer.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
confirmboolean––
notestring––
question_idintegeryes–
value–––

No output schema declared.

No examples provided.

archive_household ~74

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}.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
idintegeryes–

No output schema declared.

No examples provided.

create_household ~153

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.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
householdobjectyesHousehold-schema document
importKeystring–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).
labelstring–Your own name for the household

No output schema declared.

No examples provided.

create_mandate ~371

Assign a standing mandate: strategy-watch (one household, the strategies you choose), tax-optimization (one household, minimize-lifetime-tax, the tax strategies) or rules-change (the whole book, Growth and above: when tax rules or your assumption profile change, finds and ranks every affected household; send no household_id). Each has an objective, pinned constraints and an approval policy. Lodestar then works it when a deadline approaches, the household changes, rules or the organization's assumption profile change, a scheduled review comes due, or on run_mandate, and files proposals for an approver. constraints needs horizonYears and exactly one of profile { id, version } or assumptions { … } (never an implicit default); optional: strategies, materialityFloorUsd (default 1000), cooldownDays (30), maxOpenProposals (3), reviewCadence (quarterly), planner ("on"/"off", default off: the organization's certified planner model chooses among gate-passed proposals), taxRates, ladderCandidates, illustrativeCharacteristics, bracketFill { fillToRatesPct?, years? }, charitableGiving { annualGivingUsd, … } (tax-optimization runs charitable-giving only when charitableGiving names the gifts). One mandate per type per household. Each cycle's sweep counts the household as active for the month. Developer or owner key. Same as POST /api/v1/mandates.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
approval_policyobject––
constraintsobjectyesSee the description; validated exactly as REST validates it.
household_idinteger–Required except for rules-change
objectiveobjectyes–
statusstring–Default active
typestring–Default strategy-watch

No output schema declared.

No examples provided.

decide_household ~387

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); bracket-fill (params.fillToRatesPct?: [10|12|22|24|32|35], params.years? — Roth conversions sized each year to the top of the bracket); charitable-giving (params.annualGivingUsd, optional otherItemizedDeductionsUsd, bunchYears 2-5, iraDistributionsUsd — every year vs bunched vs QCD routes under the 2026 charitable rules). 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.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
assumptionsobject––
horizonobjectyes–
idintegeryes–
paramsobject–Strategy-specific parameters (see the tool description)
profileobject––
strategystringyes–

No output schema declared.

No examples provided.

draft_import_mapping ~191

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.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
notesstring–Context for the draft (what the export is, quirks)
sampleRecordsarrayyes1-10 sample records, column → string cell

No output schema declared.

No examples provided.

get_decision ~114

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}.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
decision_idintegeryes–

No output schema declared.

No examples provided.

get_household ~49

Fetch a stored household document and its metadata by id.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
idintegeryesHousehold id from create_household

No output schema declared.

No examples provided.

get_household_picture ~158

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.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
as_ofstring–YYYY-MM-DD or ISO timestamp; default now
idintegeryes–

No output schema declared.

No examples provided.

get_ledger ~140

Ledger entries written by approvals, newest first, optionally for one mandate or household, with the total. Each is an evidence record (hash over its inputs and outputs, Ed25519-signed with the key at /api/v1/records/keys) naming the stored decision it came from. Values are PROJECTED and NOMINAL against each decision's own baseline; the total is a sum of projections, not realized value. Any key role. Same as GET /api/v1/ledger.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
household_idinteger––
mandate_idinteger––

No output schema declared.

No examples provided.

get_mandate ~100

One mandate and its last 20 cycles, each with the strategies swept and the gate's reason for every candidate it did not propose (below the floor, cooldown, duplicate, max open), so 'why did nothing happen?' has an answer. Any key role. Same as GET /api/v1/mandates/{id}.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
mandate_idintegeryes–

No output schema declared.

No examples provided.

get_model_contract ~154

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).

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

No output schema declared.

No examples provided.

import_households ~229

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.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
dryRunboolean–Validate everything, write nothing
householdsarray–Direct rows: { importKey, label?, household }
recordsarray–Raw exported records, column → string cell
templateobject–Mapping template (templateVersion 0.1.0) for the records path

No output schema declared.

No examples provided.

list_decisions ~92

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.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
idintegeryesHousehold id

No output schema declared.

No examples provided.

list_example_households ~121

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.

NameTypeReqDescription
idstring–An example id; omit to list all twelve with their summaries.

No output schema declared.

No examples provided.

list_households ~102

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.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
statusstring–Filter by status (default: active)

No output schema declared.

No examples provided.

list_mandates ~82

The organization's mandates, newest first, optionally for one household or status, with an alert listing trigger events left open over an hour. Any key role. Same as GET /api/v1/mandates.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
household_idinteger––
statusstring––

No output schema declared.

No examples provided.

list_models ~50

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_proposals ~158

Proposals Lodestar filed for a person to decide, newest first, optionally filtered by status (pending, approved, rejected, expired, superseded, stale, withdrawn), mandate or household. Each carries the recommendation and its intents verbatim from the decision, the projected value (NOMINAL horizon-end dollars against the current plan, not discounted, not realized) with its basis, the alternatives considered, caveats, and the evidence (stored decision id, record hash, signature). Any key role. Same as GET /api/v1/proposals.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
household_idinteger––
mandate_idinteger––
statusstring––

No output schema declared.

No examples provided.

list_questions ~128

Lodestar's questions about one field of a household's data (a taxable account with no cost basis, a Social Security stream with no amount, living expenses of zero), asked by deterministic checks in every household cycle; at most one open per mandate. Filter by status (open, answered, confirmed, stale), mandate_id or household_id. Any key role. Same as GET /api/v1/questions.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
household_idinteger––
mandate_idinteger––
statusstring––

No output schema declared.

No examples provided.

manage_preferences ~226

An advisor's standing preferences, which the gate enforces in every cycle: avoid-strategy (optionally until a date), min-value for a strategy, max-annual-conversion, avoid-alternative. action list (any role); add (an approver or owner key confirms it at once, a developer key only suggests it); confirm a suggestion (approver or owner); remove (a suggestion: developer and up; a confirmed preference: approver or owner). Same as /api/v1/mandates/{id}/preferences and /api/v1/preferences/{id}.

NameTypeReqDescription
actionstringyes–
alternative_idstring––
amount_usdnumber––
api_keystring–Worthune API key (wk_…)
kindstring––
mandate_idinteger–Required for list and add
notestring––
preference_idinteger–Required for confirm and remove
strategystring––
untilstring–YYYY-MM-DD, avoid-strategy only

No output schema declared.

No examples provided.

narrate_decision ~156

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.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
audiencestring–Default "client"
decisionobject–An inline decision object (validated first)
decision_idinteger–A stored decision's id (from decide_household)

No output schema declared.

No examples provided.

patch_household ~177

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.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
expectedVersionintegeryes–
idintegeryes–
removeobject–Collection → ids to remove
setobject–Scalar fields: { filingStatus?, state? } (state: null clears it)
upsertobject–Collection → entries with ids: replace matching ids, append new ones

No output schema declared.

No examples provided.

project_household ~193

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.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
assumptionsobject––
horizonobjectyes–
idintegeryes–
monteCarloobject––
policyobject–Same shape as try_household_projection; applies to the deterministic run and every Monte Carlo path, and is hashed into the record.
profileobject––

No output schema declared.

No examples provided.

replace_household ~93

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.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
expectedVersioninteger––
householdobjectyesReplacement household-schema document
idintegeryes–
label–––

No output schema declared.

No examples provided.

review_proposal ~198

Decide one pending proposal. APPROVER OR OWNER KEY ONLY: developer and viewer keys are refused, so the key that configures mandates cannot sign off their output. approve executes nothing; it writes one signed projected-value ledger entry (a re-pin proposal moves the mandate to the newer profile version instead). reject needs a reason: not-material, client-preference, timing, data-is-wrong, already-done, or other (with a note). Refused when the proposal is not pending, has expired, or the household changed since it was computed. An agent should only call this when the person it acts for has made the decision. Same as POST /api/v1/proposals/{id}/approve and /reject.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
decisionstringyes–
notestring––
proposal_idintegeryes–
reasonstring––

No output schema declared.

No examples provided.

run_mandate ~107

Record a manual trigger and run the mandate's cycle now: sweep its strategies on the household's current version, store each decision, and file proposals that clear the gate. Returns the cycle; read proposals with list_proposals and the reasons with get_mandate. Developer or owner key. Same as POST /api/v1/mandates/{id}/run.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…)
mandate_idintegeryes–

No output schema declared.

No examples provided.

run_model ~154

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.

NameTypeReqDescription
api_keystring–Worthune Pro API key (wk_…). Required for models outside the free sample; the free models run without one.
inputsobjectyesModel inputs per the contract's domains
modelstringyesModel name from list_models

No output schema declared.

No examples provided.

try_household_projection ~305

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. NOTHING IS STORED: no household is created, no id issued, no record kept. Takes any key, a free sandbox key included (worthune.com/sandbox). 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.

NameTypeReqDescription
api_keystring–Worthune API key (wk_…); a free sandbox key works
assumptionsobjectyesRequired here: this surface has no org profile to fall back on.
horizonobjectyes–
householdobjectyesA household document: { schemaVersion, filingStatus, state?, members[], accounts[], liabilities[], incomes[], expenses[] }. It has no name field and no account numbers by design. Any expense `label`…
monteCarloobject–Simulations are clamped to 500 on this surface, and the clamp is reported back.
policyobject––

No output schema declared.

No examples provided.

verify_claim ~192

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.

NameTypeReqDescription
api_keystring–Worthune Pro API key (wk_…). Required for models outside the free sample; the free models verify without one.
claimsarrayyesClaims to check (max 50)
inputsobjectyesModel inputs per the contract's domains
modelstringyesModel name from list_models

No output schema declared.

No examples provided.

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.

remote · worthune.com

# add to Claude Code
claude mcp add --transport http com-worthune-models 'https://worthune.com/api/mcp/mcp'
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 79 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 30 tools: list_models, get_model_contract, run_model, verify_claim, create_household, and 25 more. Their descriptions and schemas cost roughly 4,794 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 21 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 Worthune Verified Financial Models MCP server?

VerifyMCP ran 13 checks on Worthune Verified Financial Models, 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.