EstatePlan.now
REMOTE · WWW.ESTATEPLAN.NOW
Find U.S. estate planning law firms: services, published prices and how to begin, with sources.
Available components
Last scanned (15 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1783 tokens (~297/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Nov 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://www.estateplan.now/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.estateplan.now | CN=YR1,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | RSA 2048 | SHA256-RSA | 52242b864aa9aea047e8ab99f8a89f83b7f |
| SANs: www.estateplan.now | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.estateplan.now. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| now. | DS published | 53572 | 8 | Verified |
| estateplan.now. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://va.vercel-scripts.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self'; connect-src 'self' https://vitals.vercel-insights.com; frame-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self' https://checkout.stripe.com; object-src 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(self), interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.estateplan.now/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.estateplan.now/api/mcp | HTTPS enforced | 308 | https://www.estateplan.now/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_firm Get one firm's record ~55
The full public record for one listed firm, by its slug (from search_firms or a profile URL /firms/<slug>).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Firm slug, e.g. "myatt-bell". |
No output schema declared.
No examples provided.
list_places List covered places ~30
States with listed firms and the metro areas that have firms within 100 miles, with counts and page URLs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_services List service filters ~44
The service filters search_firms accepts, with counts across all listings that have a sourced matching service, including later additions to homepage-screened records. Services describe scope, not quality.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recent_changes Records checked since a date ~114
Firms whose whole record or a published field was checked on or after a date, newest first by latest_checked_at. checked_at remains the whole-record date; this is not value-change history. Use it to keep a copy of the data current; fetch get_firm for the current record.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page (default 100). |
| offset | integer | – | Results to skip, for paging. |
| since | string | – | Date, YYYY-MM-DD. Omit for every record, newest first. |
No output schema declared.
No examples provided.
search_firms Search estate planning firms ~426
Find listed estate planning firms by place (location text, state, metro, or lat/lng with a radius), service, whether the first step can be completed online, and whether the firm publishes a price. Results include each firm's profile URL and the source of every fact. Place searches list labeled sponsored placements first. Name-only nationwide lookup is alphabetical, not ranked.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | – | Latitude, with lng: search around a point instead of a named place. |
| limit | integer | – | Results per page (default 20). |
| lng | number | – | Longitude, with lat. |
| location | string | – | City and state ("Portland, OR"), a state ("Oregon" or "OR"), or a 5-digit ZIP code. Maui and Hawaii island aliases use disclosed reference points and the requested radius, not island boundaries. For… |
| metro | string | – | Metro slug from list_places, e.g. portland-or. An alternative to location. |
| name | string | – | Part of the firm name. Name-only lookup works without a place and sorts alphabetically. A trailing state, e.g. Sterling Hawaii, is parsed only if the literal name has no match; explicit geography is… |
| offset | integer | – | Public results to skip, for paging (maximum 40). |
| online | boolean | – | Only firms with online intake for the requested service. General estate planning excludes package-specific routes; contact and scheduling forms do not count. Read online_start for scope. |
| priced | boolean | – | Only firms that publish a price. |
| radius_mi | number | – | Search radius in miles around a city, ZIP, metro or point (1–250, default 50). Ignored for states. |
| service | string | – | Narrow to firms that list this service on their website (see list_services). |
| state | string | – | State code or slug, e.g. OR or oregon. An alternative to location. |
No output schema declared.
No examples provided.
summarize_place Summarize a place ~282
The facts about estate planning firms in one place, in one call: how many are listed and reviewed, how many publish a price and the lowest and highest published amounts (each named with its firm, package and scope; never an average), which firms let you begin online, which services firms list, when records were checked, and ready answers to common questions such as "How much does an estate plan cost near Portland?".
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | – | Latitude, with lng: search around a point instead of a named place. |
| lng | number | – | Longitude, with lat. |
| location | string | – | City and state ("Portland, OR"), a state ("Oregon" or "OR"), or a 5-digit ZIP code. Maui and Hawaii island aliases use disclosed reference points and the requested radius, not island boundaries. For… |
| metro | string | – | Metro slug from list_places, e.g. portland-or. An alternative to location. |
| radius_mi | number | – | Search radius in miles around a city, ZIP, metro or point (1–250, default 50). Ignored for states. |
| state | string | – | State code or slug, e.g. OR or oregon. An alternative to location. |
No output schema declared.
No examples provided.
How do I install the EstatePlan.now MCP server?
EstatePlan.now is a hosted endpoint at https://www.estateplan.now/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.estateplan.now
claude mcp add --transport http now-estateplan-estateplan-now 'https://www.estateplan.now/api/mcp'
What is the EstatePlan.now MCP server?
EstatePlan.now is an MCP server listed in the public MCP registry as now.estateplan/estateplan-now. Find U.S. estate planning law firms: services, published prices and how to begin, with sources. This page covers its hosted endpoint (https://www.estateplan.now/api/mcp).
Is the EstatePlan.now MCP server safe to use?
EstatePlan.now scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the EstatePlan.now MCP server expose?
EstatePlan.now exposes 6 tools: search_firms, get_firm, summarize_place, list_places, list_services, recent_changes. Their descriptions and schemas cost roughly 951 tokens of context every time the server is loaded.
Does the EstatePlan.now MCP server require authentication?
No. We connected to EstatePlan.now without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the EstatePlan.now MCP server still maintained?
EstatePlan.now is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the EstatePlan.now MCP server?
VerifyMCP ran 13 checks on EstatePlan.now, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.