Add Settled Estate browser WebMCP tools - #44
Open
ereid7 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds Settled Estate to the live websites/examples list. I maintain the site.
The production integration uses Chrome's current
document.modelContextAPI. Three site-wide entry points search public guidance, compare five reviewed will makers, and open a state calculator;estimate_executor_payis registered on the 40 published state calculator pages. The tools reuse the manual UI and business rules and show results before completing. Source dates, billing conditions, editorial provenance and unknown values stay explicit.This is experimental browser WebMCP, requiring an enabled compatible browser. It is general information, not legal advice. No account, model API or purchase is needed to run the site tools.
Production checks on September 8, 2026 used Chrome 152’s real native API: all 17 browser journey checks and all 40 calculator schemas passed. Six mobile UI surfaces had zero axe WCAG A/AA violations. Inputs, page navigation, source/price conditions and agreement with the visible UI were checked. These are deterministic browser checks, not a model benchmark.