FinalPeace

warnings

mcp.finalpeace.co

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

https://mcp.finalpeace.co/mcp?src=registryWebsiteOAuthMCP 2025-06-18v2.0.0last checked 24 Aug 2026spoke MCP on 2 of 2 checks (30 days)initialize in 411 ms

How to authenticate

Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	OAuth
Issuer	https://app.finalpeace.co
Dynamic client registration	✓Advertised (RFC 7591)
Client ID Metadata Document	✕Not advertised
PKCE	✓S256
Grant types	authorization_code, refresh_token
Scopes	vault.read, vault.write, subscription.read
Protected-resource metadata	✓Published (RFC 9728)
Anonymous access	Handshake succeeds; 4 tools listable
Credentials demanded in prose	✕find_state_document_requirements These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.
Documentation	https://finalpeace.co/docs/mcp

What the probe found

warningTools needing credentials are listed without a challenge

1 of the 4 tools listed anonymously say in their own descriptions that they need an account or a key (find_state_document_requirements), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

No CORS headers for browser-based clients

A cross-origin preflight came back without Access-Control-Allow-Origin, so the endpoint is reachable from native clients only — code running in a web page is stopped by the browser before a request is ever sent.

4 tools usable without signing in

The server exposes a public surface before authorization: find_state_document_requirements, get_after_loss_first_steps, assess_estate_planning_gaps, connect_finalpeace_account.

Tools

find_state_document_requirementsget_after_loss_first_stepsassess_estate_planning_gapsconnect_finalpeace_account

Contract history

No contract recorded yet — the server has not answered an anonymous connection.

Run this server? A verified owner can publish snapshots with their own credentials, and the contract history starts here, marked owner-reported.

mcpi-cli publish https://mcp.finalpeace.co/mcp?src=registry

Get alerted when this contract changes

Depend on this server? Leave an email. No contract is on record here yet, so alerts can only start once one is published — and alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/finalpeace/badge.svg)](https://mcpi.app/servers/finalpeace)