EstimateGuard
ClaudecommunityChecks contractor estimates for arithmetic errors and compares prices against regional cost data. No language model, no external API.
Joseph Yuschak
Contractor estimates are hard to check by eye across a dozen line items. EstimateGuard recomputes every figure from the quantities and unit prices on the page, flags any line where the stated total doesn't match, and returns a full calculation trail so every number can be checked. A second tool looks up published cost ranges by trade and region, covering twelve US metros. These are reference figures compiled from published cost guides, labeled as such on every response. Where there is no coverage, the tool says so plainly instead of guessing. Two tools, both read-only: nothing is booked, purchased, sent, or changed on your behalf. Estimate text is processed in memory and discarded, never stored. What is kept are PII-stripped line-item figures used to build regional cost benchmarks. Parsing and arithmetic run entirely inside the server using pattern matching and exact decimal calculation. No language model, no external API: estimate text is never sent to any external service.
Anthropic’s own published signals, snapshot of September 20, 2026; units undocumented — treat as ordinal.
Over time
History builds as daily snapshots accrue — check back tomorrow.
Details
Tools(2)
- evaluate_estimate
- get_cost_range
Data from Claude’s public directory API, snapshotted daily by the MCP App Tracker. A listing describes what the directory publishes — not an endorsement.