Name: SwiftProbate
Author: swiftprobate

SwiftProbate MCP

Probate help for US executors: county courts, court forms, bank guides, and your estate checklist.

not scanned Remote · Streamable HTTP No auth needed 32 tools v1.0.0

No reviews yet by swiftprobate The publisher’s own endpoint — this marketplace is not in the path

tools declared

—

trust score

remote

at its publisher

—

calls last 7d

What it does

Probate help for US executors: county courts, court forms, bank guides, and your estate checklist.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http swiftprobate-mcp https://www.swiftprobate.com/api/mcp/estate

# 2 — ask your agent for something these tools do
#   list_my_estates, complete_onboarding, lookup_county_guide and 29 more

SwiftProbate costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

swiftprobate1 server

1 category

All 1 server

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

List the estates the signed-in user can work with (owned or shared with them), each with its id, a label (the deceased's name), the user's role, and whether they can edit. Call this FIRST — every other estate tool needs an estate_id from here.

No parameter schema on file.

Set up a new estate for the signed-in user and generate their personalized probate checklist. Use this when list_my_estates returns no estates (or one with no deceased details yet), or the user is just getting started. Saves estate details and placeholder assets, then starts checklist generation that may research public sources and send a completion email. Refuses an already-onboarded estate. Coll

Parameter	Type	Required	Notes
deceased_name	string	yes	Full name of the person who died.
deceased_date_of_death	string	yes	Date of death, ISO format YYYY-MM-DD.
deceased_state	string	yes	US state where the deceased lived (full name or code).
deceased_county	string	yes	County where the deceased lived.
will_status	string	yes	Whether there is a will: present, none, or unsure.
executor_name	string	yes	The user's full name (the person settling the estate).
executor_relationship	string	yes	The user's relationship to the deceased, e.g. 'child', 'spouse'.

Look up SwiftProbate's published probate guide for a specific US county: verified courthouse address/phone/website, filing fee, approved newspapers for publication, e-filing system, and county-specific probate forms. Use this before answering any question about a county court's contact info, filing fees, or publication requirements — county-level details are unreliable from model knowledge alone.

Parameter	Type	Required	Notes
county	string	yes	County name, e.g. 'Alameda' or 'Alameda County' (either works).
state	string	yes	Two-letter code ('CA'), full name ('California'), or slug ('california').

Look up SwiftProbate's estate-notification guide for a financial institution (banks, brokerages, life insurers, credit unions, and more): estate department phone/hours/fax, mailing and overnight addresses, online notification URL, required-document checklist, and which account types require probate.

Parameter	Type	Required	Notes
institution	string	yes	Institution name, e.g. 'Chase', 'Fidelity', 'Navy Federal Credit Union'.
category	string	no	Optional type hint, e.g. 'bank_accounts', 'brokerage', 'life_insurance'.

Find the probate forms for a jurisdiction: each form's name, code, description, official court source link (when known), and SwiftProbate page, plus whether it is a county-specific or statewide form. Some states (e.g. Florida) publish no statewide fill-in forms — pass the county to get the usable county-level forms.

Parameter	Type	Required	Notes
state	string	yes	Two-letter code, full name, or slug of the US state.
county	string	no	County name to surface that county's own forms first. Omit for statewide.
query	string	no	Optional keywords to narrow results, e.g. 'small estate affidavit', 'letters testamentary'.

Get high-level probate facts for a US state: small-estate threshold, filing deadline, creditor-claim period, estimated timeline, court filing fee, average attorney fee, whether it is a UPC / community-property / independent-administration state, plus a prose overview and the SwiftProbate guide URL.

Parameter	Type	Required	Notes
state	string	yes	Two-letter code ('CA'), full name ('California'), or slug ('california').

Search SwiftProbate's probate reference data (US states, counties, financial institutions, and court forms). Returns a list of results, each with an id you can pass to fetch for the full record. Use it for open-ended probate reference questions before answering from model knowledge.

Parameter	Type	Required	Notes
query	string	yes	A probate reference query, e.g. 'Alameda County California probate court' or 'Chase estate department'.

Fetch the full SwiftProbate reference record for an id returned by search (a state overview, county court guide, institution notification guide, or a jurisdiction's forms).

Parameter	Type	Required	Notes
id	string	yes	An id from a search result, e.g. 'county:california:alameda'.

Get a summary of the estate including details, assets, heirs, and task statistics. Use this when the user asks about the estate overview or general status.

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.

List tasks with optional filters. Use this to find tasks by status, category, asset, or search term. By default returns titles only; pass include_description: true to also get each task's full description (use this when reviewing tasks for jurisdiction or other content-level changes).

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.
status	string	no	Filter by task status
task_category	string	no	Filter by task category
asset_id	string	no	Filter by asset ID
search	string	no	Search term to match against task title or description
include_description	boolean	no	When true, include each task's full description in the response. Use when reviewing tasks for content changes (e.g., jurisdiction review). Default false.
limit	number	no	Max number of tasks to return (default 20)

Get full details of a specific task by ID, including its description, status, priority, deadline, notes, and linked documents.

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.
task_id	string	yes	The task ID

List every asset in the estate with its type and value. Your Estate Context already lists the assets, so call this only when you need the full set fresh (e.g. right after creating or updating one) or the context block was truncated. For one asset's linked tasks, use get_asset_detail instead.

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.

Get one asset's full details plus the tasks linked to it, by asset ID. Call this when the user asks about a specific asset's tasks or you need details beyond what the Assets context block shows. Get the asset_id from that context block.

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.
asset_id	string	yes	The asset ID

List every recorded heir with relationship and details. The Heirs context block already lists them, so call this only to refresh after adding or updating an heir, or when that block was truncated.

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.

Read the estate's financial ledger — money in (receipts), money out (disbursements), and distributions to heirs. Returns: transactions (each with paid_by already resolved to the actual payer's NAME — use it as-is, never assume the executor paid), starting_balances (bank accounts' date-of-death balances that already show in the ledger as starting-balance lines — these are NOT missing transact

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.
direction	string	no	Optional filter: 'receipt' (money in), 'disbursement' (money out / expenses), or 'distribution' (paid to heirs).
limit	number	no	Max rows to return (default 100, max 200).

List the estate's uploaded documents, optionally filtered by asset or task. Your Documents context block already lists them, so call this only to refresh after an upload or to filter to a specific asset's or task's documents. To read a document's contents, use read_document instead.

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.
asset_id	string	no	Filter by asset ID
task_id	string	no	Filter by task ID

Get the estate's recent activity-log entries (who changed what, and when). Call this when the user asks what has changed recently or who did something — not for task or asset contents, which have their own tools.

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.
limit	number	no	Max entries to return (default 20)

Create a new task in the estate. Use this when the user identifies a new requirement or action item that should be tracked.

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.
title	string	yes	Short, actionable task title
description	string	yes	Detailed description of what needs to be done
priority	number	no	Priority level: 0=none, 1=urgent, 2=high, 3=medium, 4=low (default 3)
deadline	string	no	Optional ISO date string for the deadline (e.g. 2026-03-15)
asset_id	string	no	Optional asset ID to link the task to
task_category	string	no	Category of task (default estate_admin, use asset_specific when linked to an asset)

Edit an existing task's title, description, priority, deadline, category, or helpful links. Use when the user wants to modify task details.

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.
task_id	string	yes	The task ID to edit
title	string	no	New title (omit to keep current)
description	string	no	New description (omit to keep current)
priority	number	no	New priority: 0=none, 1=urgent, 2=high, 3=medium, 4=low (omit to keep current)
deadline	string	no	New deadline as ISO date string (e.g. 2026-03-15), or null to clear (omit to keep current)
task_category	string	no	New category (omit to keep current)
helpful_links	array	no	Replace the task's full set of helpful links with this array. Each entry MUST use markdown link format "[Page or resource title](url)" so the UI can render a readable label (e.g. "[California Courts —

Update a task's status. Use this when the user asks to mark a task as completed, in progress, etc.

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.
task_id	string	yes	The task ID to update
status	string	yes	The new status

Set or update the user notes on a task. Use this when the user wants to add notes to a task.

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.
task_id	string	yes	The task ID
notes	string	yes	The notes content (empty string to clear)

Set or clear a task's deadline. Use this when the user wants to set a due date.

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.
task_id	string	yes	The task ID
deadline	string	no	ISO date string for the deadline (e.g. 2026-03-15), or null to clear

Assign a task to a specific estate member or the owner. Use get_estate_summary first to see available members and their user IDs.

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.
task_id	string	yes	The task ID to assign
assignee_user_id	string	no	The user ID to assign to, or null to unassign

Create a new asset in the estate. Use this when the user wants to add a bank account, property, vehicle, insurance policy, other asset, or a debt the estate owes. A same-named asset does NOT block creation (two accounts at the same institution are legitimate) — but if you created this exact asset moments ago, the tool returns the existing one instead of a duplicate. Use update_asset to change deta

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.
asset_name	string	yes	Name or description of the asset (e.g. 'Chase Checking Account', '123 Main St')
asset_type	string	yes	Type of asset (use plural form to match database schema). 'debts_liabilities' = money the estate OWES (mortgage, credit card, medical bill, unsecured claim on a court schedule) — record the outstandin
estimated_value	number	no	Estimated value in dollars (optional)
date_of_death_value	number	no	The asset's value at the date of death (the inventory value used for estate accounting and to compute gain/loss on sale). Set this at creation whenever you know it — for the decedent's own bank/invest
jurisdiction	string	no	State where the asset is located (optional, for real estate or vehicles)
account_number	string	no	Account or policy number (optional)
notes	string	no	Additional notes about the asset (optional)
has_beneficiary	boolean	no	Whether the asset has a named beneficiary (optional)
beneficiary_name	string	no	Name of the beneficiary if known (optional)
bypasses_probate	boolean	no	Whether this asset bypasses probate (e.g. POD/TOD accounts, joint tenancy) (optional)

Update an existing asset's details (name, value, jurisdiction, notes, etc.). Use this instead of creating a duplicate when the user wants to modify an asset.

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.
asset_id	string	yes	ID of the asset to update
asset_name	string	no	Updated name for the asset. Use this to correct a typo or add detail the user gave later (e.g. "Jeep Cherokee" → "2018 Jeep Cherokee Latitude Plus"). Renaming edits the existing row — do NOT create a
estimated_value	number	no	Updated estimated value in dollars
jurisdiction	string	no	Updated state/jurisdiction
account_number	string	no	Updated account/policy/VIN number
notes	string	no	Updated notes
has_beneficiary	boolean	no	Whether the asset has a named beneficiary
beneficiary_name	string	no	Name of the beneficiary
bypasses_probate	boolean	no	Whether this asset bypasses probate
date_of_death_value	number	no	The asset's value at the date of death (the inventory value used for estate accounting and to compute gain/loss on sale).
disposition	string	no	What has happened to the asset: 'on_hand' (still in the estate), 'sold', 'transferred', or 'distributed' (given to an heir in kind). Record the sale proceeds as a money-in transaction in the Ledger li

Record that the user has finished telling you about the estate's assets. Call this the moment they say there is nothing else — "that's everything", "that's the only asset", "nothing else to add". This is what turns "Has real property" and the estate size in your Estate Context from "Not yet provided" into a definite answer; until you call it those facts stay unknown and you will keep having to ask

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.

Record a financial transaction in the estate ledger when the user mentions money moving — an expense they paid, income the estate received, a debt payment, or a distribution to an heir. Examples: "I paid $4,200 for the funeral", "the estate got a $1,300 tax refund", "my brother covered the $800 headstone". ALWAYS confirm the amount, what it was for, and (for expenses) who paid before calling. Admi

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.
direction	string	yes	'receipt' = money into the estate; 'disbursement' = money out, including expenses and debt payments; 'distribution' = money/assets paid to an heir.
category	string	yes	For disbursement: funeral, court_fees, attorney_fees, executor_fee, property_maintenance, appraisal, insurance, taxes, debt_payment, other_expense. For receipt: opening_balance (physical cash or funds
amount	number	yes	Positive dollar amount (the direction conveys whether it's in or out).
transaction_date	string	yes	Date the money moved, as YYYY-MM-DD.
payee_or_source	string	no	Who was paid (for money out) or the source (for money in), e.g. 'Travis County Clerk' or 'Fidelity dividend'. Optional.
paid_by	string	no	Only for disbursements. 'individual' means a person paid out of pocket and is owed reimbursement (the user, unless payer_name is given). Defaults to 'estate'.
payer_name	string	no	Only when paid_by='individual' AND someone other than the user paid (e.g. a family member). The person's name. Omit if the user themselves paid.
asset_id	string	no	Optional ID of a related asset (e.g. sale proceeds from a specific account or property).
heir_id	string	no	Optional ID of the heir who received a distribution.
document_id	string	no	Optional ID of a document (e.g. a receipt or invoice the user uploaded) to attach to this transaction as its receipt. The document is treated as a ledger receipt and kept out of the Documents library.
notes	string	no	Optional free-text note.

Correct an existing ledger transaction when the user wants to fix a mistake — a wrong amount, date, category, payee, who paid, or which heir/asset it relates to. Find the transaction's ID with get_transactions first. This is a PARTIAL update: pass transaction_id plus ONLY the fields that change; everything you omit is left as-is. Use this (not a new correcting entry) whenever the user says an amou

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.
transaction_id	string	yes	ID of the transaction to update (from get_transactions).
direction	string	no	Change the direction. If you change this, also pass a matching category.
category	string	no	Change the category. Must belong to the transaction's direction (same taxonomy as log_transaction).
amount	number	no	Change the positive dollar amount.
transaction_date	string	no	Change the date, as YYYY-MM-DD.
payee_or_source	string	no	Change who was paid (money out) or the source (money in).
paid_by	string	no	Change who paid (disbursements). 'individual' means a person paid out of pocket and is owed reimbursement.
payer_name	string	no	When paid_by='individual' AND someone other than the user paid, the person's name. Omit if the user themselves paid.
asset_id	string	no	Change the related asset ID.
heir_id	string	no	Change the related heir ID (for distributions).
notes	string	no	Change the free-text note.

Add a new heir to the estate. Use when the user wants to record a person who may inherit (spouse, child, stepchild, grandchild, parent, sibling, or other relative). Call as soon as you have a name and the user's description of the relationship — any wording is accepted.

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.
name	string	yes	Full legal name of the heir
relationship	string	yes	Relationship to the deceased. Canonical values: spouse, child, stepchild, grandchild, parent, sibling, other. If the user's wording doesn't match one (e.g. 'half-brother', 'daughter-in-law', 'adult st
relationship_detail	string	no	The relationship exactly as the user described it, when it carries more than the canonical value (e.g. 'stepson', 'half-sister', 'goddaughter'). Shown on probate forms, so preserve the user's words.
is_minor	boolean	no	Whether the heir is under 18 (default false)
is_deceased	boolean	no	Whether the heir is deceased (default false). Used for per stirpes inheritance.
is_divorced	boolean	no	For a spouse only: whether they are a divorced/former spouse (default false). A divorced spouse is recorded for a complete family picture but is not a surviving spouse and does not inherit under intes
parent_heir_id	string	no	ID of the parent heir if this person inherits through a deceased parent (e.g. grandchild whose parent predeceased the decedent). Omit otherwise.
address	string	no	Mailing address (free text, multi-line OK). Used for formal probate notice.
phone	string	no	Phone number (any format)
email	string	no	Email address
notes	string	no	Free-text notes about this heir — context like whereabouts unknown, predeceased details, per-stirpes notes, disputes, or anything the user wants remembered. Multi-line OK.

Update an existing heir's details. Use when the user wants to correct or add information to a recorded heir. Get the heir_id from the pre-loaded Heirs context block.

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.
heir_id	string	yes	ID of the heir to update
name	string	no	Updated full legal name
relationship	string	no	Updated relationship to the deceased. Canonical values: spouse, child, stepchild, grandchild, parent, sibling, other. Free-text wording (e.g. 'half-brother') is accepted and normalized automatically.
relationship_detail	string	no	The relationship exactly as the user described it, when it carries more than the canonical value (empty string clears it). Shown on probate forms.
is_minor	boolean	no	Whether the heir is under 18
is_deceased	boolean	no	Whether the heir is deceased
is_divorced	boolean	no	For a spouse only: whether they are a divorced/former spouse (not a surviving spouse).
address	string	no	Updated mailing address (empty string clears it)
phone	string	no	Updated phone number (empty string clears it)
email	string	no	Updated email address (empty string clears it)
notes	string	no	Updated free-text notes about this heir (empty string clears). Use for context like whereabouts unknown, predeceased details, per-stirpes notes, disputes, or anything the user wants remembered.

Record that the user has finished telling you about the estate's heirs and family. Call this the moment they say that's everyone — "no other children", "there's no spouse", "that's all the heirs". This is what turns "Surviving spouse" and "Minor children" in your Estate Context from "Not yet provided" into a definite answer; until you call it those facts stay unknown and you will keep having to as

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.

Update high-level estate details that the user can correct after onboarding. Use this when the user mentions a fact that should be persisted (e.g. "actually there is a will", "the will is in the safe deposit box", "the case number is 2026-001234"). NOT for who the heirs are or what the estate owns — record a person with create_heir, an asset with create_asset, and when the user says the list is fi

Parameter	Type	Required	Notes
estate_id	string	yes	The estate to act on. Call list_my_estates first to get this id.
will_status	string	no	Whether the deceased left a will. Use 'present' if there IS a will (testate), 'none' if there is NO will (intestate), or 'unsure' if it hasn't been determined yet (e.g. the user is still looking for o
will_location	string	no	Where the will is stored (e.g. 'safe deposit box at Wells Fargo', 'with attorney Smith'). Empty string clears it.
deceased_marital_status	string	no	Marital status of the deceased at time of death
surviving_spouse_name	string	no	Name of the surviving spouse. Empty string clears it. To record THAT there is a surviving spouse, add them with create_heir (relationship 'spouse') — that is what makes the fact definite in your Estat
executor_name	string	no	Name of the user managing the estate (the executor / personal representative). Empty string clears it.
executor_relationship	string	no	Relationship of the user managing the estate to the deceased
deceased_date_of_birth	string	no	Date of birth as ISO date (e.g. 1945-03-12). Empty string clears it.
deceased_date_of_death	string	no	Date of death as ISO date (e.g. 2026-01-15). Empty string clears it.
deceased_state	string	no	Two-letter US state code where the deceased lived at time of death (e.g. 'CA', 'NY'). Must be a valid US state. Changing state invalidates county — you must also provide deceased_county in the same ca
deceased_county	string	no	County where the deceased lived at time of death (e.g. 'Los Angeles', 'Cook'). Must be non-empty. Use the bare county name without the word 'County'.
estate_account_institution	string	no	Where the estate's OPERATING/checking account is held (the account opened after death with the estate's EIN) — e.g. 'Quorum FCU', 'PNC Bank'. This is reference info, NOT an asset; never use create_ass
estate_account_number	string	no	The estate operating account's number, if the user provides it. Stored on the estate and masked in the UI. Empty string clears it.
estate_number	string	no	The probate case / estate number the county court (register of wills / clerk) assigns once the estate is opened (e.g. '2026-001234', 'PR-2026-5678'). Save this whenever the user says the court issued
ein	string	no	The estate's IRS Employer Identification Number (tax ID), formatted like '12-3456789'. The executor gets it from the IRS after death to open the estate bank account and file the estate's tax return (F
situation_notes	string	no	Durable, estate-level narrative context that has no structured field of its own — the will situation (e.g. 'has a handwritten will from 2017, executed in CA, validity unconfirmed'), a pending claim (e

Free

$0 forever

Every tool — any call limit is its publisher’s, not ours
No card, and mcprush charges nothing for it
Runs at its publisher’s own address — this marketplace is not in the path
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install SwiftProbate or to call it, at any volume.

Where are you running it?

Tool surface

Release history

SwiftProbate MCP

What it does

Quickstart

Where are you running it?

Tool surface

What counts against your monthly calls

Release history

See also