MCP servers › com.swiftprobate › probate

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

com.swiftprobate/probate

Probate help for US executors: county courts, court forms, bank guides, and your estate checklist. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-23Topic: finance-and-payments · AI-classifiedversion 1.0.0streamable HTTP32 tools

Summary

com.swiftprobate/probate is a remote MCP server listed in the official MCP registry at version 1.0.0. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 32 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

met: Registry entry is active and says how to run it
not met: Source repository link opens
not applicable: Repository is not archived
not applicable: Code pushed to the repository in the 90 days before our check
not applicable: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Tools: 32
Described as changing data: 16 of 32 toolsAI-classified
Mainly works on: files and code on the machine it runs onAI-classified
Topic: finance-and-paymentsAI-classified
Last tested: 2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 15 tools whose name or declaration suggests they change data (complete_onboarding, create_task, edit_task, update_task_status, update_task_notes and 10 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.

Worth knowing before you connect it

16 tools are described as changing something (complete_onboarding, create_task, edit_task, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-10-23
Mode: read-only (no tool calls)
Latest version: 1.0.0, published 2026-10-11 (registry, as of the 2026-10-23 snapshot)
First listed version: 2026-10-11 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-23
Package and repository: checked 2026-10-22
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.0.0 (published 2026-10-11).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

32tools

0resources

0prompts

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on.

16 of 32 tools are described as changing something (creating, editing, deleting, sending or running).

list_my_estatesreads or searches
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
complete_onboardingon 3 other serverscreates or changes datadescribed as changing data
“Set up a new estate for the signed-in user and generate their personalized probate checklist.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
7 inputs, 7 required
- deceased_namestringrequired“Full name of the person who died.”
- deceased_date_of_deathstringrequired“Date of death, ISO format YYYY-MM-DD.”
- deceased_statestringrequired“US state where the deceased lived (full name or code).”
- deceased_countystringrequired“County where the deceased lived.”
- will_statusstringrequired“Whether there is a will: present, none, or unsure.”
- executor_namestringrequired“The user's full name (the person settling the estate).”
- executor_relationshipstringrequired“The user's relationship to the deceased, e.g.”
lookup_county_guidereads or searches
“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-specif…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 2 required
- countystringrequired“County name, e.g.”
- statestringrequired“Two-letter code ('CA'), full name ('California'), or slug ('california').”
lookup_institution_guidereads or searches
“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 addr…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- institutionstringrequired“Institution name, e.g.”
- categorystring“Optional type hint, e.g.”
find_probate_formsreads or searches
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
- statestringrequired“Two-letter code, full name, or slug of the US state.”
- countystring“County name to surface that county's own forms first.”
- querystring“Optional keywords to narrow results, e.g.”
get_state_overviewreads or searches
“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 / communit…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- statestringrequired“Two-letter code ('CA'), full name ('California'), or slug ('california').”
searchon 763 other serversreads or searches
“Search SwiftProbate's probate reference data (US states, counties, financial institutions, and court forms).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- querystringrequired“A probate reference query, e.g.”
fetchon 432 other serversreads or searches
“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).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- idstringrequired“An id from a `search` result, e.g.”
get_estate_summaryreads or searches
“Get a summary of the estate including details, assets, heirs, and task statistics.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- estate_idstringrequired“The estate to act on.”
get_taskson 3 other serversreads or searches
“List tasks with optional filters.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
7 inputs, 1 required
- estate_idstringrequired“The estate to act on.”
- statusstring“Filter by task status”
- task_categorystring“Filter by task category”
- asset_idstring“Filter by asset ID”
- searchstring“Search term to match against task title or description”
- include_descriptionboolean“When true, include each task's full description in the response.”
- limitnumber“Max number of tasks to return (default 20)”
get_task_detailon 1 other serverreads or searches
“Get full details of a specific task by ID, including its description, status, priority, deadline, notes, and linked documents.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 2 required
- estate_idstringrequired“The estate to act on.”
- task_idstringrequired“The task ID”
get_assetson 5 other serversreads or searches
“List every asset in the estate with its type and value.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- estate_idstringrequired“The estate to act on.”

Show 20 more tools

get_asset_detailreads or searches
“Get one asset's full details plus the tasks linked to it, by asset ID.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 2 required
- estate_idstringrequired“The estate to act on.”
- asset_idstringrequired“The asset ID”
get_heirsreads or searches
“List every recorded heir with relationship and details.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- estate_idstringrequired“The estate to act on.”
get_transactionson 19 other serversreads or searches
“Read the estate's financial ledger — money in (receipts), money out (disbursements), and distributions to heirs.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
- estate_idstringrequired“The estate to act on.”
- directionstring“Optional filter: 'receipt' (money in), 'disbursement' (money out / expenses), or 'distribution' (paid to heirs).”
- limitnumber“Max rows to return (default 100, max 200).”
get_documentson 4 other serversreads or searches
“List the estate's uploaded documents, optionally filtered by asset or task.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
- estate_idstringrequired“The estate to act on.”
- asset_idstring“Filter by asset ID”
- task_idstring“Filter by task ID”
get_activity_logon 2 other serversreads or searches
“Get the estate's recent activity-log entries (who changed what, and when).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- estate_idstringrequired“The estate to act on.”
- limitnumber“Max entries to return (default 20)”
create_taskon 47 other serverscreates or changes datadescribed as changing data
“Create a new task in the estate.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
7 inputs, 3 required
- estate_idstringrequired“The estate to act on.”
- titlestringrequired“Short, actionable task title”
- descriptionstringrequired“Detailed description of what needs to be done”
- prioritynumber“Priority level: 0=none, 1=urgent, 2=high, 3=medium, 4=low (default 3)”
- deadlinestring“Optional ISO date string for the deadline (e.g.”
- asset_idstring“Optional asset ID to link the task to”
- task_categorystring“Category of task (default estate_admin, use asset_specific when linked to an asset)”
edit_taskon 1 other servercreates or changes datadescribed as changing data
“Edit an existing task's title, description, priority, deadline, category, or helpful links.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
8 inputs, 2 required
- estate_idstringrequired“The estate to act on.”
- task_idstringrequired“The task ID to edit”
- titlestring“New title (omit to keep current)”
- descriptionstring“New description (omit to keep current)”
- prioritynumber“New priority: 0=none, 1=urgent, 2=high, 3=medium, 4=low (omit to keep current)”
- deadlinestring“New deadline as ISO date string (e.g.”
- task_categorystring“New category (omit to keep current)”
- helpful_linksarray“Replace the task's full set of helpful links with this array.”
update_task_statuson 4 other serverscreates or changes datadescribed as changing data
“Update a task's status.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
3 inputs, 3 required
- estate_idstringrequired“The estate to act on.”
- task_idstringrequired“The task ID to update”
- statusstringrequired“The new status”
update_task_notescreates or changes datadescribed as changing data
“Set or update the user notes on a task.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
3 inputs, 3 required
- estate_idstringrequired“The estate to act on.”
- task_idstringrequired“The task ID”
- notesstringrequired“The notes content (empty string to clear)”
update_task_deadlinecreates or changes datadescribed as changing data
“Set or clear a task's deadline.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
3 inputs, 2 required
- estate_idstringrequired“The estate to act on.”
- task_idstringrequired“The task ID”
- deadlinestring“ISO date string for the deadline (e.g.”
assign_taskon 4 other serverscreates or changes datadescribed as changing data
“Assign a task to a specific estate member or the owner.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
3 inputs, 2 required
- estate_idstringrequired“The estate to act on.”
- task_idstringrequired“The task ID to assign”
- assignee_user_idstring“The user ID to assign to, or null to unassign”
create_asseton 3 other serverscreates or changes datadescribed as changing data
“Create a new asset in the estate.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
11 inputs, 3 required
- estate_idstringrequired“The estate to act on.”
- asset_namestringrequired“Name or description of the asset (e.g.”
- asset_typestringrequired“Type of asset (use plural form to match database schema).”
- estimated_valuenumber“Estimated value in dollars (optional)”
- date_of_death_valuenumber“The asset's value at the date of death (the inventory value used for estate accounting and to compute gain/loss on sale).”
- jurisdictionstring“State where the asset is located (optional, for real estate or vehicles)”
- account_numberstring“Account or policy number (optional)”
- notesstring“Additional notes about the asset (optional)”
- has_beneficiaryboolean“Whether the asset has a named beneficiary (optional)”
- beneficiary_namestring“Name of the beneficiary if known (optional)”
- bypasses_probateboolean“Whether this asset bypasses probate (e.g.”
update_asseton 5 other serverscreates or changes datadescribed as changing data
“Update an existing asset's details (name, value, jurisdiction, notes, etc.).”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
12 inputs, 2 required
- estate_idstringrequired“The estate to act on.”
- asset_idstringrequired“ID of the asset to update”
- asset_namestring“Updated name for the asset.”
- estimated_valuenumber“Updated estimated value in dollars”
- jurisdictionstring“Updated state/jurisdiction”
- account_numberstring“Updated account/policy/VIN number”
- notesstring“Updated notes”
- has_beneficiaryboolean“Whether the asset has a named beneficiary”
- beneficiary_namestring“Name of the beneficiary”
- bypasses_probateboolean“Whether this asset bypasses probate”
- date_of_death_valuenumber“The asset's value at the date of death (the inventory value used for estate accounting and to compute gain/loss on sale).”
- dispositionstring“What has happened to the asset: 'on_hand' (still in the estate), 'sold', 'transferred', or 'distributed' (given to an heir in kind).”
mark_assets_completecreates or changes datadescribed as changing data
“Record that the user has finished telling you about the estate's assets.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
1 input, 1 required
- estate_idstringrequired“The estate to act on.”
log_transactionon 1 other servercreates or changes datadescribed as changing data
“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.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
12 inputs, 5 required
- estate_idstringrequired“The estate to act on.”
- directionstringrequired“'receipt' = money into the estate; 'disbursement' = money out, including expenses and debt payments; 'distribution' = money/assets paid to an heir.”
- categorystringrequired“For disbursement: funeral, court_fees, attorney_fees, executor_fee, property_maintenance, appraisal, insurance, taxes, debt_payment, other_expense.”
- amountnumberrequired“Positive dollar amount (the direction conveys whether it's in or out).”
- transaction_datestringrequired“Date the money moved, as YYYY-MM-DD.”
- payee_or_sourcestring“Who was paid (for money out) or the source (for money in), e.g.”
- paid_bystring“Only for disbursements.”
- payer_namestring“Only when paid_by='individual' AND someone other than the user paid (e.g.”
- asset_idstring“Optional ID of a related asset (e.g.”
- heir_idstring“Optional ID of the heir who received a distribution.”
- document_idstring“Optional ID of a document (e.g.”
- notesstring“Optional free-text note.”
update_transactionon 4 other serverscreates or changes datadescribed as changing data
“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.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
12 inputs, 2 required
- estate_idstringrequired“The estate to act on.”
- transaction_idstringrequired“ID of the transaction to update (from get_transactions).”
- directionstring“Change the direction.”
- categorystring“Change the category.”
- amountnumber“Change the positive dollar amount.”
- transaction_datestring“Change the date, as YYYY-MM-DD.”
- payee_or_sourcestring“Change who was paid (money out) or the source (money in).”
- paid_bystring“Change who paid (disbursements).”
- payer_namestring“When paid_by='individual' AND someone other than the user paid, the person's name.”
- asset_idstring“Change the related asset ID.”
- heir_idstring“Change the related heir ID (for distributions).”
- notesstring“Change the free-text note.”
create_heircreates or changes datadescribed as changing data
“Add a new heir to the estate.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
12 inputs, 3 required
- estate_idstringrequired“The estate to act on.”
- namestringrequired“Full legal name of the heir”
- relationshipstringrequired“Relationship to the deceased.”
- relationship_detailstring“The relationship exactly as the user described it, when it carries more than the canonical value (e.g.”
- is_minorboolean“Whether the heir is under 18.”
- is_deceasedboolean“Whether the heir is deceased (default false).”
- is_divorcedboolean“For a spouse only: whether they are a divorced/former spouse (default false).”
- parent_heir_idstring“ID of the parent heir if this person inherits through a deceased parent (e.g.”
- addressstring“Mailing address (free text, multi-line OK).”
- phonestring“Phone number (any format)”
- emailstring“Email address”
- notesstring“Free-text notes about this heir — context like whereabouts unknown, predeceased details, per-stirpes notes, disputes, or anything the user wants remembered.”
update_heircreates or changes datadescribed as changing data
“Update an existing heir's details.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
12 inputs, 2 required
- estate_idstringrequired“The estate to act on.”
- heir_idstringrequired“ID of the heir to update”
- namestring“Updated full legal name”
- relationshipstring“Updated relationship to the deceased.”
- relationship_detailstring“The relationship exactly as the user described it, when it carries more than the canonical value (empty string clears it).”
- is_minorboolean“Whether the heir is under 18”
- is_deceasedboolean“Whether the heir is deceased”
- is_divorcedboolean“For a spouse only: whether they are a divorced/former spouse (not a surviving spouse).”
- addressstring“Updated mailing address (empty string clears it)”
- phonestring“Updated phone number (empty string clears it)”
- emailstring“Updated email address (empty string clears it)”
- notesstring“Updated free-text notes about this heir (empty string clears).”
mark_heirs_completecreates or changes datadescribed as changing data
“Record that the user has finished telling you about the estate's heirs and family.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
1 input, 1 required
- estate_idstringrequired“The estate to act on.”
update_estatecreates or changes datadescribed as changing data
“Update high-level estate details that the user can correct after onboarding.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
16 inputs, 1 required
- estate_idstringrequired“The estate to act on.”
- will_statusstring“Whether the deceased left a will.”
- will_locationstring“Where the will is stored (e.g.”
- deceased_marital_statusstring“Marital status of the deceased at time of death”
- surviving_spouse_namestring“Name of the surviving spouse.”
- executor_namestring“Name of the user managing the estate (the executor / personal representative).”
- executor_relationshipstring“Relationship of the user managing the estate to the deceased”
- deceased_date_of_birthstring“Date of birth as ISO date (e.g.”
- deceased_date_of_deathstring“Date of death as ISO date (e.g.”
- deceased_statestring“Two-letter US state code where the deceased lived at time of death (e.g.”
- deceased_countystring“County where the deceased lived at time of death (e.g.”
- estate_account_institutionstring“Where the estate's OPERATING/checking account is held (the account opened after death with the estate's EIN) — e.g.”
- estate_account_numberstring“The estate operating account's number, if the user provides it.”
- estate_numberstring“The probate case / estate number the county court (register of wills / clerk) assigns once the estate is opened (e.g.”
- einstring“The estate's IRS Employer Identification Number (tax ID), formatted like '12-3456789'.”
- situation_notesstring“Durable, estate-level narrative context that has no structured field of its own — the will situation (e.g.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 32 tools
Says what it returns: 53% of 32 tools
States limits, defaults or errors: 9% of 32 tools
Says when to use it: 100% of 32 tools
Items covered per tool: 2.6 of 4 on average

Counted from the listing

Parameters with a description: 100% of 155
Tools with a description: 100% of 32
Typical description length: 353 characters

The tool set

Counted from the listing

Tools: 32
Size of the list: about 11,396 tokens for an agent to load (characters ÷ 4)
Naming: 30 of 32 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 32 of 32 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://www.swiftprobate.com/api/mcp/estate

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

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

VS Code · .vscode/mcp.json

{
  "servers": {
    "probate": {
      "type": "http",
      "url": "https://www.swiftprobate.com/api/mcp/estate"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

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

Claude Code

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

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://www.swiftprobate.com/api/mcp/estate --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint www.swiftprobate.com/api/mcp/estate	Session opened	matches	our test · 2026-10-23
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-23

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
Not metSource repository link opensThe registry entry gives no repository link.
Does not applyRepository is not archivedNo public GitHub repository to read.
Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-22. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about com.swiftprobate/probate

Answered from the data above

Is com.swiftprobate/probate safe to install?

We do not rate servers as safe or unsafe. 1 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: 16 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does com.swiftprobate/probate need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.swiftprobate/probate been security tested?

Partly. 3 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can com.swiftprobate/probate do?

It lists 32 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search and create or change data. We did not call any tool, so this describes the text, not the behaviour.

Can com.swiftprobate/probate change or delete data?

16 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.vybenetwork/solana-mcp-vybeSolana MCP by Vybealso has tools that creates or changes data, reads or searchescompare with this one
io.github.mnemox-ai/tradememory-protocolalso has tools that creates or changes data, reads or searchescompare with this one
io.github.agent-next/polymarket-paper-traderPolymarket Paper Traderalso has tools that creates or changes data, reads or searchescompare with this one
io.github.DeHor-Labs/mcp-fiscal-brasilMCP Fiscal Brasilalso has tools that creates or changes data, reads or searchescompare with this one
io.github.codespar/mcp-khipualso has tools that creates or changes data, reads or searchescompare with this one
io.github.nirholas/threews-pumpfunthree.ws pump.fun MCPalso has tools that creates or changes data, reads or searchescompare with this one

Active servers whose topic is also “finance-and-payments” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

3 exercised12 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 12

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 3

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
1,275 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 32 tools, 0 resources, 0 prompts.
5,966 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

finance-and-payments

AI-classified · 2026-10-23

Pricing modelAI-classified

no value

No value: the AI answer was held back because the quoted text did not clearly support it.

Programming language

does not apply

no existing GitHub repository (server declares no repository link, so there is nothing to fetch)

Hosting type

remote (hosted by the publisher)

registry · 2026-10-23

MCP capability

tools

our test · 2026-10-23

Transport

streamable HTTP

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

not stated

no readable GitHub owner to describe

Maintenance

does not apply

server declares no repository link, so there is nothing to fetch

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.swiftprobate/probate: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/com.swiftprobate/probate

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.swiftprobate/probate)](https://protocolprobe.com/mcp/servers/com.swiftprobate/probate)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology