# SwiftProbate Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## SwiftProbate

Probate guidance for US executors: court forms, county procedures, bank notification guides, and estate checklists.

- Record: https://musedirectory.ai/connector/swiftprobate
- Category: Legal
- Developer: SwiftProbate (https://www.swiftprobate.com/mcp)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 316ms, checked 2026-10-29T11:16:05Z
- Endpoint: https://www.swiftprobate.com/api/mcp/estate
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-28T13:41:31Z)
- Source: Found in the official MCP Registry (com.swiftprobate/probate) https://registry.modelcontextprotocol.io/v0/servers?search=com.swiftprobate%2Fprobate

Helps executors settle estates in the US by providing county-specific probate court information, approved forms, financial institution notification guides, and a personalized checklist. Tracks assets, heirs, tasks, and estate finances in one place.

Example request: "Show me the probate forms I need to file in Alameda County and tell me the courthouse address and filing fee."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use SwiftProbate to help me. It is a free service with an MCP server at https://www.swiftprobate.com/api/mcp/estate. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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: 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 chec
- 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 c
- 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 ty
- 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 
- 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 Swif
- 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 knowl
- 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 chan
- 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_det
- 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 acc
- 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 inste
- 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: 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: Update a task's status. Use this when the user asks to mark a task as completed, in progress, etc.
- update_task_notes: Set or update the user notes on a task. Use this when the user wants to add notes to a task.
- update_task_deadline: Set or clear a task's deadline. Use this when the user wants to set a due date.
- assign_task: 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
- update_asset: 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: 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 fr
- 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 c
- update_transaction: 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 fie
- 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: 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: 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 f
- update_estate: 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 wh

Screening checks:
- MCP handshake: pass (Answered in 1335ms)
- Domain against threat feeds (Cloudflare security DNS): pass (www.swiftprobate.com not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: warn (update_estate: Tool text tells the model to take extra steps)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 335 days ago)
- AI review of purpose and tool behavior: pass (No concerns)