{"id":"com.swiftprobate/probate","slug":"com-swiftprobate-probate","title":"SwiftProbate","description":"Probate help for US executors: county courts, court forms, bank guides, and your estate checklist.","version":"1.0.0","publisher":{"kind":"domain","id":"swiftprobate.com","label":"swiftprobate.com","url":"https://swiftprobate.com"},"website":"https://www.swiftprobate.com/mcp","repository":"","remotes":[{"type":"streamable-http","url":"https://www.swiftprobate.com/api/mcp/estate"}],"packages":[],"published":"2026-10-11","updated":"2026-10-11","status":"online","auth":"","latency_ms":1020,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"list_my_estates","title":"","description":"List the estates the signed-in SwiftProbate user can work with: estates they own plus estates someone has shared with them as a collaborator. SwiftProbate is probate task-management software that helps executors and families organize and track the probate process. This tool requires sign-in and only reads; it never creates or changes anything.\n\nWhen to use: before any other estate tool, because ev","read_only":true},{"name":"complete_onboarding","title":"","description":"Set up a new estate for the signed-in SwiftProbate user and start generating their personalized probate checklist. SwiftProbate is probate task-management software that helps executors and families understand and organize the steps of settling an estate; the checklist is general guidance, not legal advice, and SwiftProbate is not a law firm.\n\nWhen to use: list_my_estates returns no estates (or one","read_only":false},{"name":"show_estate_setup","title":"","description":"Show the signed-in user a short form, right in the chat, for setting up their estate in SwiftProbate. Submitting it builds their personalized probate checklist (the same as complete_onboarding, without asking the questions one by one). Use this when the user agrees to set up an estate, for example after list_my_estates shows they have none, or when they ask for help with their own situation (what ","read_only":true},{"name":"show_my_tasks","title":"","description":"Show the signed-in user's next open tasks for one estate as a card in the chat: the same Up Next list their SwiftProbate dashboard shows, up to five tasks with due dates, which ones are overdue, and which are waiting on another task. Users who can edit the estate can tick a task to mark it done, and can tap Ask about this to get help with a task. Use this when the user asks what's next, what they ","read_only":true},{"name":"lookup_county_guide","title":"","description":"Look up SwiftProbate's published probate guide for one specific US county. SwiftProbate is probate task-management software that helps people understand and organize the probate process; this tool returns general reference information, not legal advice, and SwiftProbate is not a law firm.\n\nWhen to use: the user names (or has clearly implied) a specific county and asks about that county's probate c","read_only":true},{"name":"lookup_institution_guide","title":"","description":"Look up SwiftProbate's estate-notification guide for one financial institution: banks, credit unions, brokerages, retirement-plan providers, life insurers, and similar companies. It helps an executor or family member understand how that institution handles a death notification and what paperwork it typically asks for. This is general reference information from probate task-management software, not","read_only":true},{"name":"find_probate_forms","title":"","description":"Find the probate court forms SwiftProbate has catalogued for a US state, optionally narrowed to one county and/or keywords. It helps the user see which forms exist for their jurisdiction and where to get the official versions. SwiftProbate is probate task-management software, not a law firm; this is general information, not legal advice, and it does not determine which forms a particular case requ","read_only":true},{"name":"get_state_overview","title":"","description":"Get SwiftProbate's high-level probate reference facts for one US state. It helps the user understand the shape of probate in that state (thresholds, deadlines, typical timeline) as general information from probate task-management software. It is not legal advice; SwiftProbate is not a law firm, and the figures are summaries the user should confirm against current state law or with a licensed attor","read_only":true},{"name":"search","title":"","description":"Search SwiftProbate's probate reference data (US state overviews, county probate court guides, financial-institution estate-notification guides, and court-form listings) with one free-text query. This is one half of a search/fetch pair: search returns short result items, and you pass an item's id to fetch for the full record. SwiftProbate is probate task-management software that helps people under","read_only":true},{"name":"fetch","title":"","description":"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).","read_only":true},{"name":"get_estate_summary","title":"","description":"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.","read_only":true},{"name":"get_tasks","title":"","description":"List the tasks in one estate's probate checklist, in the same order the user sees on their SwiftProbate dashboard. SwiftProbate is probate task-management software that helps executors organize and track the steps of settling an estate; tasks are general guidance, not legal advice. Requires sign-in and an estate_id from list_my_estates.\n\nWhen to use: the user asks what is on their checklist, what ","read_only":true},{"name":"get_task_detail","title":"","description":"Get full details of a specific task by ID, including its description, status, priority, deadline, notes, and linked documents.","read_only":true},{"name":"get_assets","title":"","description":"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.","read_only":true},{"name":"get_asset_detail","title":"","description":"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.","read_only":true},{"name":"get_heirs","title":"","description":"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.","read_only":true},{"name":"get_transactions","title":"","description":"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 — plus its linked `asset_id`, `heir_id`, receipt `document_id`, and `notes`), `starting_balances` (bank accounts' date-of-death balances that already s","read_only":true},{"name":"get_documents","title":"","description":"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.","read_only":true},{"name":"get_activity_log","title":"","description":"Get the estate's recent activity-log entries (who changed what, and when). Each entry has `who` (the person, and whether they're the owner or a collaborator) and `via` (the SwiftProbate app, Grace, or ChatGPT acting for them). 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. If no entry covers the change they ","read_only":true},{"name":"create_task","title":"","description":"Create a new task in the estate. Use this when the user identifies a new requirement or action item that should be tracked.","read_only":false},{"name":"edit_task","title":"","description":"Edit an existing task's title, description, priority, deadline, category, or helpful links. Use when the user wants to modify task details.","read_only":false},{"name":"update_task_status","title":"","description":"Update a task's status. Use this when the user asks to mark a task as completed, in progress, etc. Marking a task completed or not_applicable (not required) is the customer's decision: only do it when they have said so, and pass their words in customer_words. To restore a task marked not required, set it back to not_started.","read_only":false},{"name":"update_task_notes","title":"","description":"Set or update the user notes on a task. Use this when the user wants to add notes to a task.","read_only":false},{"name":"update_task_deadline","title":"","description":"Set or clear a task's deadline. Use this when the user wants to set a due date.","read_only":false},{"name":"assign_task","title":"","description":"Assign a task to the estate owner or a collaborator who has accepted their invite. Pass assignee_name with the person's name as listed in \"People on this estate\" (a first name works when it's unique); the result says who it was assigned to, or why it couldn't be (pending invite, no match, more than one match). Pass neither assignee_name nor assignee_user_id to unassign.","read_only":false},{"name":"create_asset","title":"","description":"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","read_only":false},{"name":"update_asset","title":"","description":"Update an existing asset's details (name, type, value, jurisdiction, notes, etc.). Use this instead of creating a duplicate when the user wants to modify an asset — including when it was saved under the wrong type: change asset_type here rather than deleting and recreating it, which would wipe its tasks. To empty a field, list it in clear_fields.","read_only":false},{"name":"add_household_items","title":"","description":"Add belongings (furniture, clothing, jewelry, tools, collections, household goods) to the estate's one \"Household and personal items\" list — several per call. Use this, NOT create_asset, for personal belongings: each is a row of that list, not its own asset, and the list has one short task set. An item worth more than $5,000, a firearm, or a titled vehicle/boat is moved to its own asset automatica","read_only":false},{"name":"update_household_item","title":"","description":"Change one row of the Household and personal items list: its name, value or recipient, remove it, or move it to its own asset (track_separately). Item ids come from get_asset_detail on the household list asset or get_estate_summary. Removing only takes it off the list. Edits one row of the Household and personal items list. remove takes it off the list (it is kept as removed, not deleted); track_s","read_only":false},{"name":"mark_assets_complete","title":"","description":"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","read_only":false},{"name":"log_transaction","title":"","description":"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","read_only":false},{"name":"update_transaction","title":"","description":"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","read_only":false},{"name":"create_heir","title":"","description":"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 once the customer has confirmed how the person is related to the DECEASED — any wording is accepted. \"My brother Tom\" is the customer's brother, not the deceased's: ask (e.g. \"Is Tom your mom's son?\") before saving.","read_only":false},{"name":"update_heir","title":"","description":"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.","read_only":false},{"name":"mark_heirs_complete","title":"","description":"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","read_only":false},{"name":"update_estate","title":"","description":"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","read_only":false},{"name":"set_probate_route","title":"","description":"Record what the customer told you about their probate path and their court — the same answers as the Estate page's \"Which probate route are you using?\" card and the attorney task. Use it when the customer says which path they are using (\"we're doing the small estate affidavit\", \"we're going through full probate\", \"we'll open ancillary probate in Florida for the condo\") or what the court said about","read_only":false}],"server_info":{"name":"swiftprobate-estate","version":"1.0.0"},"category":"productivity","tags":["legal","finance","cloud"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-10-11","stars":0,"badges":[],"sponsor":null,"page":"https://agentsindex.org/agents/com-swiftprobate-probate/"}