All servers · Government & law · Payments & accounting

SwiftProbate

com.swiftprobate/probate · v1.0.0

Measured by MCP Station

Instruction-like text was found in update_estate. This is a pattern match, not a verdict. What we look for

Description written by the publisher, not verified

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

Connect

claude mcp add --transport http probate https://www.swiftprobate.com/api/mcp/estate

{
  "mcpServers": {
    "probate": {
      "url": "https://www.swiftprobate.com/api/mcp/estate"
    }
  }
}

Tools as reported by the server

• list_my_estates
  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.
• complete_onboarding write/delete
  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 tha
• lookup_county_guide
  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
• lookup_institution_guide
  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.
• find_probate_forms
  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 co
• get_state_overview
  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.
• search
  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.
• fetch
  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).
• get_estate_summary
  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.
• get_tasks
  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).
• get_task_detail
  Get full details of a specific task by ID, including its description, status, priority, deadline, notes, and linked documents.
• get_assets
  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.
• get_asset_detail
  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.
• get_heirs
  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.
• get_transactions
  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
• get_documents
  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.
• get_activity_log
  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.
• create_task
  Create a new task in the estate. Use this when the user identifies a new requirement or action item that should be tracked.
• edit_task write/delete
  Edit an existing task's title, description, priority, deadline, category, or helpful links. Use when the user wants to modify task details.
• update_task_status write/delete
  Update a task's status. Use this when the user asks to mark a task as completed, in progress, etc.
• update_task_notes write/delete
  Set or update the user notes on a task. Use this when the user wants to add notes to a task.
• update_task_deadline write/delete
  Set or clear a task's deadline. Use this when the user wants to set a due date.
• assign_task write/delete
  Assign a task to a specific estate member or the owner. Use get_estate_summary first to see available members and their user IDs.
• create_asset
  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 mo
• update_asset write/delete
  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.
• mark_assets_complete write/delete
  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
• log_transaction
  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 head
• update_transaction write/delete
  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; eve
• create_heir
  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.
• update_heir write/delete
  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.
• mark_heirs_complete write/delete
  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 provide
• update_estate write/delete
  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 —

Tool changes

• 2026-10-17: list_my_estates, complete_onboarding, lookup_county_guide, lookup_institution_guide, find_probate_forms, get_state_overview, search, fetch, get_estate_summary, get_tasks, get_task_detail, get_assets
• 2026-10-16: list_my_estates, complete_onboarding, lookup_county_guide, lookup_institution_guide, find_probate_forms, get_state_overview, search, fetch, get_estate_summary, get_tasks, get_task_detail, get_assets

Website · JSON · Text for agents · Registry updated 2026-10-11