SwiftProbate

com.swiftprobate/probateVersion 1.0.0

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

Status

Responds269 msNov 14, 2026, 14:17 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 14:17 UTC
Latency: 269 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://www.swiftprobate.com/api/mcp/estateResponds269 msNov 14, 2026, 14:17 UTC

No sign-in

Claude Code

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

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: probate
Remote MCP server URL: https://www.swiftprobate.com/api/mcp/estate

Cursor

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

VS Code

code --add-mcp '{"name":"probate","type":"http","url":"https://www.swiftprobate.com/api/mcp/estate"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

34 tools

Tools of SwiftProbate
	Description		Read-only	Idempotent	Open world
`assign_task`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.	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.	Yes	No	No	No
`complete_onboarding`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. When to use: list_my_estates returns no estates (or one with no deceased details yet), or the user is just getting started. Also use it when a user with no estate set up asks for help with their own situation, such as what they need to do to settle a specific person's estate, their next steps as executor, or a personal plan or checklist: offer to set one up, and proceed only if they agree. If show_estate_setup is available, use it instead of asking questions: it shows a one-screen form that submits through this tool. When not to use: general probate questions, which the reference tools answer (search, lookup_county_guide, get_state_overview, find_probate_forms, lookup_institution_guide). An estate that is already set up: this tool refuses it, so use update_estate to change details or get_tasks to see the checklist. A user who is a collaborator rather than the owner: it refuses, so use the other estate tools. How to call without the form: collect every field first, gently and one or two at a time, since the user may be grieving: the deceased's full name, date of death (YYYY-MM-DD), the state and county where they lived, whether there is a will (present, none, or unsure), the user's own full name, and their relationship to the deceased. Then call once. Partial failures are not guaranteed safe to retry. What it does: saves the estate details and placeholder assets, then starts checklist generation in the background, which may research public sources and send a completion email. If the user has not yet accepted the Terms of Service and disclaimer, it refuses and returns a link to finish setup on the website; share that link. Re	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. When to use: list_my_estates returns no estates (or one with no deceased details yet), or the user is just getting started. Also use it when a user with no estate set up asks for help with their own situation, such as what they need to do to settle a specific person's estate, their next steps as executor, or a personal plan or checklist: offer to set one up, and proceed only if they agree. If show_estate_setup is available, use it instead of asking questions: it shows a one-screen form that submits through this tool. When not to use: general probate questions, which the reference tools answer (search, lookup_county_guide, get_state_overview, find_probate_forms, lookup_institution_guide). An estate that is already set up: this tool refuses it, so use update_estate to change details or get_tasks to see the checklist. A user who is a collaborator rather than the owner: it refuses, so use the other estate tools. How to call without the form: collect every field first, gently and one or two at a time, since the user may be grieving: the deceased's full name, date of death (YYYY-MM-DD), the state and county where they lived, whether there is a will (present, none, or unsure), the user's own full name, and their relationship to the deceased. Then call once. Partial failures are not guaranteed safe to retry. What it does: saves the estate details and placeholder assets, then starts checklist generation in the background, which may research public sources and send a completion email. If the user has not yet accepted the Terms of Service and disclaimer, it refuses and returns a link to finish setup on the website; share that link. Re	Yes	No	No	Yes
`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 moments ago, the tool returns the existing one instead of a duplicate. Use update_asset to change details of an existing asset. For eligible paid estates, adding an asset may start public-source research and add asset-specific tasks. Recent same-name assets may have empty fields filled instead of a duplicate being added. Repeating after the deduplication window may create another 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 moments ago, the tool returns the existing one instead of a duplicate. Use update_asset to change details of an existing asset. For eligible paid estates, adding an asset may start public-source research and add asset-specific tasks. Recent same-name assets may have empty fields filled instead of a duplicate being added. Repeating after the deduplication window may create another asset.	No	No	No	Yes
`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 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.	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.	No	No	No	No
`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.	Create a new task in the estate. Use this when the user identifies a new requirement or action item that should be tracked.	No	No	No	No
`edit_task`Edit an existing task's title, description, priority, deadline, category, or helpful links. Use when the user wants to modify task details.	Edit an existing task's title, description, priority, deadline, category, or helpful links. Use when the user wants to modify task details.	Yes	No	No	No
`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).	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).	No	Yes	Yes	No
`find_probate_forms`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 requires. When to use: the user asks what probate forms exist in a state or county, wants a specific form by name or code (e.g. 'small estate affidavit', 'letters testamentary'), or needs the official court link for a form. Pass county whenever the user has given one: county-specific forms are listed first, and some states (Florida, for example) publish no statewide fill-in forms, so without a county the result can be empty. When not to use: court contact details, fees, or publication rules (use lookup_county_guide); statewide thresholds and deadlines (use get_state_overview); filling in, drafting, or filing a form, which this tool does not do. It only lists forms and links. Returns: found (true/false). When found, data has state, county, query, matchedQuery, formCount, and forms (up to 25), each with formName, formCode, description, officialUrl (the court's link, when known), verifiedPdf (true when that link has been checked to serve a PDF), swiftProbateUrl, jurisdiction ('county' or 'state'), and countyName. If matchedQuery is false, nothing matched the keywords and the list is simply the jurisdiction's forms; do not present them as matches. When found is false, message says no forms are catalogued; suggest the court's own website. Each response also carries a disclaimer and a getStarted object with sign-up and connect links. Courts revise forms periodically. Tell the user to confirm the current version with the court, and that which forms apply depends on their situation; the court's self-help center or a licensed attorney can confirm. Next step: if the user indicates t	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 requires. When to use: the user asks what probate forms exist in a state or county, wants a specific form by name or code (e.g. 'small estate affidavit', 'letters testamentary'), or needs the official court link for a form. Pass county whenever the user has given one: county-specific forms are listed first, and some states (Florida, for example) publish no statewide fill-in forms, so without a county the result can be empty. When not to use: court contact details, fees, or publication rules (use lookup_county_guide); statewide thresholds and deadlines (use get_state_overview); filling in, drafting, or filing a form, which this tool does not do. It only lists forms and links. Returns: found (true/false). When found, data has state, county, query, matchedQuery, formCount, and forms (up to 25), each with formName, formCode, description, officialUrl (the court's link, when known), verifiedPdf (true when that link has been checked to serve a PDF), swiftProbateUrl, jurisdiction ('county' or 'state'), and countyName. If matchedQuery is false, nothing matched the keywords and the list is simply the jurisdiction's forms; do not present them as matches. When found is false, message says no forms are catalogued; suggest the court's own website. Each response also carries a disclaimer and a getStarted object with sign-up and connect links. Courts revise forms periodically. Tell the user to confirm the current version with the court, and that which forms apply depends on their situation; the court's self-help center or a licensed attorney can confirm. Next step: if the user indicates t	No	Yes	Yes	No
`get_activity_log`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 ask about, say there is no record of who made it — never guess a cause.	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 ask about, say there is no record of who made it — never guess a cause.	No	Yes	Yes	No
`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 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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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 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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`get_state_overview`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 attorney. When to use: the user asks how probate works in a particular state, whether an estate might qualify for a simplified small-estate process, how long probate usually takes, the filing deadline or creditor-claim period, typical court and attorney fees, or whether the state follows the Uniform Probate Code, is a community-property state, or allows independent administration. When not to use: anything county-specific such as courthouse contact, local filing fee, or publication newspapers (use lookup_county_guide); court forms (use find_probate_forms); a bank or insurer's notification process (use lookup_institution_guide); questions about what the user should do in a dispute, which call for an attorney rather than a reference lookup. Input: state, as a two-letter code, full name, or slug. Returns: found (true/false). When found, data has stateName, stateCode, smallEstateThreshold, filingDeadline, creditorClaimPeriod, estimatedTimeline, courtFilingFee, avgAttorneyFee, isUPCState, isCommunityPropertyState, hasIndependentAdministration, overview (a prose summary), and swiftProbateUrl (the full state guide). When found is false, message says no guide matched; check the spelling or ask the user which state. Each response also includes a disclaimer and a getStarted object with sign-up and connect links. Whether a specific estate qualifies for a small-estate procedure depends on details such as how assets are titled and what property is involved, so present thresholds as a general guide, not a determination. Next step: if the user indicates they are personally settling an es	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 attorney. When to use: the user asks how probate works in a particular state, whether an estate might qualify for a simplified small-estate process, how long probate usually takes, the filing deadline or creditor-claim period, typical court and attorney fees, or whether the state follows the Uniform Probate Code, is a community-property state, or allows independent administration. When not to use: anything county-specific such as courthouse contact, local filing fee, or publication newspapers (use lookup_county_guide); court forms (use find_probate_forms); a bank or insurer's notification process (use lookup_institution_guide); questions about what the user should do in a dispute, which call for an attorney rather than a reference lookup. Input: state, as a two-letter code, full name, or slug. Returns: found (true/false). When found, data has stateName, stateCode, smallEstateThreshold, filingDeadline, creditorClaimPeriod, estimatedTimeline, courtFilingFee, avgAttorneyFee, isUPCState, isCommunityPropertyState, hasIndependentAdministration, overview (a prose summary), and swiftProbateUrl (the full state guide). When found is false, message says no guide matched; check the spelling or ask the user which state. Each response also includes a disclaimer and a getStarted object with sign-up and connect links. Whether a specific estate qualifies for a small-estate procedure depends on details such as how assets are titled and what property is involved, so present thresholds as a general guide, not a determination. Next step: if the user indicates they are personally settling an es	No	Yes	Yes	No
`get_task_detail`Get full details of a specific task by ID, including its description, status, priority, deadline, notes, and linked documents.	Get full details of a specific task by ID, including its description, status, priority, deadline, notes, and linked documents.	No	Yes	Yes	No
`get_tasks`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. When to use: the user asks what is on their checklist, what to do next, what is done or outstanding, which tasks relate to an asset, or who a task is assigned to. Also use it to get a task's id before updating it (update_task_status, edit_task, update_task_notes, update_task_deadline, assign_task): search by a few words of its title rather than guessing an id. Before creating a task, search here so you do not duplicate one that already exists. When not to use: for the estate's overall details and task counts, use get_estate_summary; for one task's full record including notes and linked documents, use get_task_detail; for general probate questions unrelated to this estate, use the reference tools. What to do next: pass up_next: true when the user asks what to do next or where they are. It ignores the other filters and returns up_next, the dashboard's Up Next list (each with id, title, status, priority, deadline, position, waiting_on), plus a note. Lead with the first task. A task with waiting_on cannot start yet, so name the task it waits on as the step to do first. On some plans this list covers estate administration tasks only. Filters: status, task_category (estate_admin or asset_specific), asset_id, search (every word must appear in the title or description), limit (default 20, max 50), and include_description (adds each task's description and helpful_links). Returns: a list of tasks, each with id, title, status, priority, deadline, task_category, asset_id, institution_name, completed_at, user_notes, assigned_to, assigned_to_name (null when unassigned), position (its place in the full list), and waiting_on (the unfinished tas	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. When to use: the user asks what is on their checklist, what to do next, what is done or outstanding, which tasks relate to an asset, or who a task is assigned to. Also use it to get a task's id before updating it (update_task_status, edit_task, update_task_notes, update_task_deadline, assign_task): search by a few words of its title rather than guessing an id. Before creating a task, search here so you do not duplicate one that already exists. When not to use: for the estate's overall details and task counts, use get_estate_summary; for one task's full record including notes and linked documents, use get_task_detail; for general probate questions unrelated to this estate, use the reference tools. What to do next: pass up_next: true when the user asks what to do next or where they are. It ignores the other filters and returns up_next, the dashboard's Up Next list (each with id, title, status, priority, deadline, position, waiting_on), plus a note. Lead with the first task. A task with waiting_on cannot start yet, so name the task it waits on as the step to do first. On some plans this list covers estate administration tasks only. Filters: status, task_category (estate_admin or asset_specific), asset_id, search (every word must appear in the title or description), limit (default 20, max 50), and include_description (adds each task's description and helpful_links). Returns: a list of tasks, each with id, title, status, priority, deadline, task_category, asset_id, institution_name, completed_at, user_notes, assigned_to, assigned_to_name (null when unassigned), position (its place in the full list), and waiting_on (the unfinished tas	No	Yes	Yes	No
`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 — plus its linked `asset_id`, `heir_id`, receipt `document_id`, and `notes`), `starting_balances` (bank accounts' date-of-death balances that already show in the ledger as starting-balance lines — these are NOT missing transactions; do not suggest re-adding them), and `totals` (starting_balance, money_in, money_out, pending_reimbursements). Use this before answering any spending, reimbursement, or accounting question, and treat both `transactions` and `starting_balances` as already in the ledger.	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 show in the ledger as starting-balance lines — these are NOT missing transactions; do not suggest re-adding them), and `totals` (starting_balance, money_in, money_out, pending_reimbursements). Use this before answering any spending, reimbursement, or accounting question, and treat both `transactions` and `starting_balances` as already in the ledger.	No	Yes	Yes	No
`list_my_estates`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. When to use: before any other estate tool, because every estate tool (get_estate_summary, get_tasks, create_task, update_estate, and the rest) needs an estate_id that comes from here. Also use it when the user asks which estates are in their account. When not to use: for a summary of an estate's details, assets, or progress, call get_estate_summary with the estate_id instead; this tool returns only ids and labels. General probate reference questions (county guides, state overviews, forms, institutions) do not need an estate. Returns, when the user has estates: estates, a list where each item has estateId (pass it as estate_id), label (the deceased's name, or 'Unnamed estate'), role (owner, editor, or viewer), and canEdit (whether write tools are allowed; viewers can read but not edit). If there is more than one estate and the user has not said which, ask them to choose rather than guessing. Returns, when the user has no estate yet: a plain-language message that leads the result, plus structured content with an empty estates list, setup_needed: true, setup_url, and consent_on_file. Follow the message and tell the user plainly there is no estate yet. If consent_on_file is true, offer to set one up (SwiftProbate builds a personalized probate checklist from a few questions). Only if they agree, call show_estate_setup, which shows a short setup form right in the chat; if that tool is not available, collect the details conversationally and call complete_onboarding. If consent_on_file is false, the user must first accept the Terms of Service and read the disclaimer on the website, so share setup_url instead. Estate data reflects	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. When to use: before any other estate tool, because every estate tool (get_estate_summary, get_tasks, create_task, update_estate, and the rest) needs an estate_id that comes from here. Also use it when the user asks which estates are in their account. When not to use: for a summary of an estate's details, assets, or progress, call get_estate_summary with the estate_id instead; this tool returns only ids and labels. General probate reference questions (county guides, state overviews, forms, institutions) do not need an estate. Returns, when the user has estates: estates, a list where each item has estateId (pass it as estate_id), label (the deceased's name, or 'Unnamed estate'), role (owner, editor, or viewer), and canEdit (whether write tools are allowed; viewers can read but not edit). If there is more than one estate and the user has not said which, ask them to choose rather than guessing. Returns, when the user has no estate yet: a plain-language message that leads the result, plus structured content with an empty estates list, setup_needed: true, setup_url, and consent_on_file. Follow the message and tell the user plainly there is no estate yet. If consent_on_file is true, offer to set one up (SwiftProbate builds a personalized probate checklist from a few questions). Only if they agree, call show_estate_setup, which shows a short setup form right in the chat; if that tool is not available, collect the details conversationally and call complete_onboarding. If consent_on_file is false, the user must first accept the Terms of Service and read the disclaimer on the website, so share setup_url instead. Estate data reflects	No	Yes	Yes	No
`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 headstone". ALWAYS confirm the amount, what it was for, and (for expenses) who paid before calling. Administration expenses are direction='disbursement'. If someone paid out of pocket, set paid_by='individual' so it's tracked as reimbursable: leave payer_name empty if the user themselves paid, or set payer_name to the person's name if someone else (e.g. a family member who isn't the estate) paid. Records a bookkeeping entry only; does not move money. Duplicate detection is time-limited, so repeating later may add another entry.	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. Administration expenses are direction='disbursement'. If someone paid out of pocket, set paid_by='individual' so it's tracked as reimbursable: leave payer_name empty if the user themselves paid, or set payer_name to the person's name if someone else (e.g. a family member who isn't the estate) paid. Records a bookkeeping entry only; does not move money. Duplicate detection is time-limited, so repeating later may add another entry.	No	No	No	No
`lookup_county_guide`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. When to use: the user names (or has clearly implied) a specific county and asks about that county's probate court: where it is, how to contact it, its website, the filing fee, which newspapers are approved for publishing a notice to creditors, what publication typically costs, whether e-filing is available and through which system, or the county's own local probate forms. County-level details like these are unreliable from model knowledge alone, so use this tool when the user's question depends on them. When not to use: statewide rules such as small-estate thresholds, deadlines, creditor-claim periods, or timelines (use get_state_overview); a full list of court forms or a specific form by name or code (use find_probate_forms); notifying a bank, brokerage, or insurer (use lookup_institution_guide). If the user has not said which county, ask rather than guess. Returns: found (true/false). When found, data has county, state, courthouseAddress, courthousePhone, courthouseWebsite, filingFee, approvedNewspapers, publicationCost, eFilingAvailable, eFilingSystem, countyForms (each with name, url, description), simplifiedPaths (for states where SwiftProbate has verified them: each statewide simplified probate procedure with where it is filed, its steps, its official forms, and anything not verified; the county forms are mostly for full probate, so a user on a simplified path should be pointed to that path's own forms and steps), and swiftProbateUrl (the full guide page). When found is false, message says no published guide exists for that county; tell the user and suggest the county court's own website. Every response also includes a disclaimer, whose meaning you should pass along, and a	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. When to use: the user names (or has clearly implied) a specific county and asks about that county's probate court: where it is, how to contact it, its website, the filing fee, which newspapers are approved for publishing a notice to creditors, what publication typically costs, whether e-filing is available and through which system, or the county's own local probate forms. County-level details like these are unreliable from model knowledge alone, so use this tool when the user's question depends on them. When not to use: statewide rules such as small-estate thresholds, deadlines, creditor-claim periods, or timelines (use get_state_overview); a full list of court forms or a specific form by name or code (use find_probate_forms); notifying a bank, brokerage, or insurer (use lookup_institution_guide). If the user has not said which county, ask rather than guess. Returns: found (true/false). When found, data has county, state, courthouseAddress, courthousePhone, courthouseWebsite, filingFee, approvedNewspapers, publicationCost, eFilingAvailable, eFilingSystem, countyForms (each with name, url, description), simplifiedPaths (for states where SwiftProbate has verified them: each statewide simplified probate procedure with where it is filed, its steps, its official forms, and anything not verified; the county forms are mostly for full probate, so a user on a simplified path should be pointed to that path's own forms and steps), and swiftProbateUrl (the full guide page). When found is false, message says no published guide exists for that county; tell the user and suggest the county court's own website. Every response also includes a disclaimer, whose meaning you should pass along, and a	No	Yes	Yes	No
`lookup_institution_guide`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 legal or financial advice; SwiftProbate is not a law firm. When to use: the user wants to notify a named institution that an account holder died, asks how to reach its estate or bereavement department, what documents it will ask for (for example a death certificate or letters testamentary), where to mail or overnight paperwork, whether it accepts online notification, or whether an account type there generally goes through probate. When not to use: the user has not named an institution (ask which one, or use search); questions about a court, county, or state rules (use lookup_county_guide or get_state_overview); questions about a specific account's balance, ownership, or beneficiaries, which this tool does not have. Inputs: institution, as the user says it (e.g. 'Chase', 'Navy Federal Credit Union'), and an optional category hint such as bank_accounts, brokerage, or life_insurance that helps pick the right guide. Returns: found (true/false). When found, data has institutionName, estateDeptPhone, estateDeptHours, estateDeptFax, mailingAddress, overnightAddress, onlineNotificationUrl, estatePageUrl, documentChecklist (each a document plus when it is required), accountTypes (each a type plus requiresProbate true/false), and swiftProbateUrl. When found is false, message says no guide matched; tell the user and suggest contacting the institution directly. Each response also carries a disclaimer and a getStarted object with sign-up and connect links. Whether a particular account needs probate depends on how it is titled (named beneficiary, payable-on-death, joint ownership),	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 legal or financial advice; SwiftProbate is not a law firm. When to use: the user wants to notify a named institution that an account holder died, asks how to reach its estate or bereavement department, what documents it will ask for (for example a death certificate or letters testamentary), where to mail or overnight paperwork, whether it accepts online notification, or whether an account type there generally goes through probate. When not to use: the user has not named an institution (ask which one, or use search); questions about a court, county, or state rules (use lookup_county_guide or get_state_overview); questions about a specific account's balance, ownership, or beneficiaries, which this tool does not have. Inputs: institution, as the user says it (e.g. 'Chase', 'Navy Federal Credit Union'), and an optional category hint such as bank_accounts, brokerage, or life_insurance that helps pick the right guide. Returns: found (true/false). When found, data has institutionName, estateDeptPhone, estateDeptHours, estateDeptFax, mailingAddress, overnightAddress, onlineNotificationUrl, estatePageUrl, documentChecklist (each a document plus when it is required), accountTypes (each a type plus requiresProbate true/false), and swiftProbateUrl. When found is false, message says no guide matched; tell the user and suggest contacting the institution directly. Each response also carries a disclaimer and a getStarted object with sign-up and connect links. Whether a particular account needs probate depends on how it is titled (named beneficiary, payable-on-death, joint ownership),	No	Yes	Yes	No
`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 from "Not yet provided" into a definite answer; until you call it those facts stay unknown and you will keep having to ask about them. BEFORE calling: make sure every asset they have named is already saved with create_asset — this tool records that the LIST is finished, it does not save assets. Call it on the SAME turn the user tells you the list is complete; do NOT ask them to confirm a second time first. For a paid estate this also starts building their asset-by-asset plan, so only call it once the list really is final. Changes the asset-collection flag and derived estate facts. For eligible paid estates, this may start public-source research, add checklist tasks, and send a completion email.	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 about them. BEFORE calling: make sure every asset they have named is already saved with create_asset — this tool records that the LIST is finished, it does not save assets. Call it on the SAME turn the user tells you the list is complete; do NOT ask them to confirm a second time first. For a paid estate this also starts building their asset-by-asset plan, so only call it once the list really is final. Changes the asset-collection flag and derived estate facts. For eligible paid estates, this may start public-source research, add checklist tasks, and send a completion email.	Yes	No	No	Yes
`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 from "Not yet provided" into a definite answer; until you call it those facts stay unknown and you will keep having to ask about them. BEFORE calling: make sure every person they have named is already saved with create_heir, including a surviving spouse. Call it on the SAME turn the user says the list is complete; do NOT ask them to confirm a second time first. Exception: if NO heirs are recorded, the user must explicitly confirm there are none before the list can be marked complete — pass confirmed_no_heirs: true only after they have. Changes the heir-collection flag and derived estate facts; does not start paid checklist generation.	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 ask about them. BEFORE calling: make sure every person they have named is already saved with create_heir, including a surviving spouse. Call it on the SAME turn the user says the list is complete; do NOT ask them to confirm a second time first. Exception: if NO heirs are recorded, the user must explicitly confirm there are none before the list can be marked complete — pass confirmed_no_heirs: true only after they have. Changes the heir-collection flag and derived estate facts; does not start paid checklist generation.	Yes	No	No	No
`search`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 understand and navigate probate; results are general reference information, not legal advice. When to use: open-ended probate reference questions where the user mentions a state, a county, or an institution but it is unclear which specific lookup fits, or where several records may be relevant (e.g. 'probate in Cook County, Illinois' can surface the state overview, the county guide, and the forms listing together). County-level details are unreliable from model knowledge alone, so searching helps for those. When not to use: when the user has clearly named one county, institution, state, or form need, the matching tool (lookup_county_guide, lookup_institution_guide, get_state_overview, find_probate_forms) is more direct. Questions about the user's own estate records need the signed-in estate tools. Not for topics unrelated to probate. How matching works: the query is matched against state names or uppercase two-letter codes ('TX'), county names (most reliable with 'County' or 'Parish' and the state), and institution names. Topic words alone, such as 'small estate affidavit', usually match nothing unless a state is named too. Returns: query; results (up to 8), each with id (e.g. 'state:texas', 'county:illinois:cook', 'forms:california', 'institution:chase'), title, url (the SwiftProbate page), and snippet; plus a disclaimer and a getStarted object with sign-up and connect links. When nothing matches, results is empty and hint explains how to rephrase: retry once with a state, a county and state, or an institution name, or ask the user. Next step: call fetch with the most relev	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 understand and navigate probate; results are general reference information, not legal advice. When to use: open-ended probate reference questions where the user mentions a state, a county, or an institution but it is unclear which specific lookup fits, or where several records may be relevant (e.g. 'probate in Cook County, Illinois' can surface the state overview, the county guide, and the forms listing together). County-level details are unreliable from model knowledge alone, so searching helps for those. When not to use: when the user has clearly named one county, institution, state, or form need, the matching tool (lookup_county_guide, lookup_institution_guide, get_state_overview, find_probate_forms) is more direct. Questions about the user's own estate records need the signed-in estate tools. Not for topics unrelated to probate. How matching works: the query is matched against state names or uppercase two-letter codes ('TX'), county names (most reliable with 'County' or 'Parish' and the state), and institution names. Topic words alone, such as 'small estate affidavit', usually match nothing unless a state is named too. Returns: query; results (up to 8), each with id (e.g. 'state:texas', 'county:illinois:cook', 'forms:california', 'institution:chase'), title, url (the SwiftProbate page), and snippet; plus a disclaimer and a getStarted object with sign-up and connect links. When nothing matches, results is empty and hint explains how to rephrase: retry once with a state, a county and state, or an institution name, or ask the user. Next step: call fetch with the most relev	No	Yes	Yes	No
`show_estate_setup`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 to do for a specific person's estate, their next steps as executor) and have no estate yet. Do not use it for general probate questions, which the reference tools answer, or when the user already has an estate set up (use get_tasks instead). The result says whether the user has agreed to SwiftProbate's Terms on the website and whether an estate is already set up; the form shows the right screen for each case. If the form can't be shown in this chat, ask the setup questions conversationally and call complete_onboarding instead. SwiftProbate is software that helps people organize the probate process; it is not a law firm and does not give legal advice.	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 to do for a specific person's estate, their next steps as executor) and have no estate yet. Do not use it for general probate questions, which the reference tools answer, or when the user already has an estate set up (use get_tasks instead). The result says whether the user has agreed to SwiftProbate's Terms on the website and whether an estate is already set up; the form shows the right screen for each case. If the form can't be shown in this chat, ask the setup questions conversationally and call complete_onboarding instead. SwiftProbate is software that helps people organize the probate process; it is not a law firm and does not give legal advice.	No	Yes	Yes	No
`show_my_tasks`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 should work on, or to see or check off their tasks, and they already have an estate set up. It needs an estate_id from list_my_estates; if they have more than one estate and haven't said which, ask. Do not use it to search tasks, filter by status or asset, or read a task's full details (use get_tasks or get_task_detail), or when the user has no estate yet (offer setup instead). The result lists the tasks shown, the total number of open tasks, and whether the user can edit. If the card can't be shown in this chat, summarize the tasks from the result instead. SwiftProbate is software that helps people organize the probate process; tasks are general guidance, not legal advice.	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 should work on, or to see or check off their tasks, and they already have an estate set up. It needs an estate_id from list_my_estates; if they have more than one estate and haven't said which, ask. Do not use it to search tasks, filter by status or asset, or read a task's full details (use get_tasks or get_task_detail), or when the user has no estate yet (offer setup instead). The result lists the tasks shown, the total number of open tasks, and whether the user can edit. If the card can't be shown in this chat, summarize the tasks from the result instead. SwiftProbate is software that helps people organize the probate process; tasks are general guidance, not legal advice.	No	Yes	Yes	No
`update_asset`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.	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.	Yes	No	No	No
`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 what the estate owns — record a person with create_heir, an asset with create_asset, and when the user says the list is finished call mark_heirs_complete / mark_assets_complete. This is ALSO where you record the estate's OPERATING/checking account (the account the executor opens after death with the estate's EIN) — use estate_account_institution / estate_account_number, NOT create_asset. The operating account is not an estate asset. It is ALSO where you save the estate's IRS EIN (tax ID) — use the `ein` field, which is distinct from the court's case number (`estate_number`). Always confirm changes before calling. When changing deceased_state or deceased_county, follow the special jurisdiction-change flow described in the system prompt: explain that tasks are based on county of residence at time of death, confirm via suggest_actions, then after the update review and revise jurisdiction-affected tasks. Replaces supplied estate details. Resolving will status may remove the will-determination task and add succession tasks from local reference data.	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 finished call mark_heirs_complete / mark_assets_complete. This is ALSO where you record the estate's OPERATING/checking account (the account the executor opens after death with the estate's EIN) — use estate_account_institution / estate_account_number, NOT create_asset. The operating account is not an estate asset. It is ALSO where you save the estate's IRS EIN (tax ID) — use the `ein` field, which is distinct from the court's case number (`estate_number`). Always confirm changes before calling. When changing deceased_state or deceased_county, follow the special jurisdiction-change flow described in the system prompt: explain that tasks are based on county of residence at time of death, confirm via suggest_actions, then after the update review and revise jurisdiction-affected tasks. Replaces supplied estate details. Resolving will status may remove the will-determination task and add succession tasks from local reference data.	Yes	No	No	No
`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.	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.	Yes	No	No	No
`update_task_deadline`Set or clear a task's deadline. Use this when the user wants to set a due date.	Set or clear a task's deadline. Use this when the user wants to set a due date.	Yes	No	No	No
`update_task_notes`Set or update the user notes on a task. Use this when the user wants to add notes to a task.	Set or update the user notes on a task. Use this when the user wants to add notes to a task.	Yes	No	No	No
`update_task_status`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.	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.	Yes	No	No	No
`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 fields that change; everything you omit is left as-is. Use this (not a new correcting entry) whenever the user says an amount or detail was wrong. Confirm the correction with the user before calling.	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 amount or detail was wrong. Confirm the correction with the user before calling.	Yes	No	No	No

Details

Registry status: Active
Published: Oct 11, 2026
Updated: Oct 11, 2026
Website: https://www.swiftprobate.com/mcp⁠ (opens in a new tab)
Repository: Not given
Categories (suggested): DocumentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing