FinalPeace

co.finalpeacePublished by finalpeace.coOfficial publisherv2.0.0Updated Oct 24, 2026

State document requirements for all 50 US states, an after-a-loss checklist, and a planning gap chec

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

FinalPeace is a remote MCP server that gives an assistant US estate-planning reference material: state document requirements, an after-a-loss checklist and a

What you can do
Look up state document requirements for all 50 US states, so an assistant can tell you what estate documents a given state calls for. Work through an after-a-loss checklist covering the steps that follow a death. Run a planning gap check to see what may be missing from an existing plan. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when someone is preparing or reviewing an estate plan and wants state-specific document requirements, a checklist for what to do after a loss, or a check for gaps in an existing plan.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package, environment variables or headers are declared. The manifest declares no authentication, though the provider's documentation may specify access conditions.
Before you install
The description is truncated, so the full scope of the server is unclear. It offers general reference material, not legal advice; confirm decisions with a qualified professional. No authentication is declared, so do not send sensitive personal, financial or family details until you know how the service handles them.

Installation

In SourceWeft

  1. Open FinalPeace in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/co.finalpeace%2Festate-planning/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "finalpeace": {
      "type": "http",
      "url": "https://mcp.finalpeace.co/mcp?src=registry"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.