Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

VouchedPros

REMOTE · MCP.VOUCHEDPROS.COM · SCANNED AUG 3

Local US home-service pricing, providers ranked by the Vouched Score, rebates, and glossary.

+6 this week 65 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2095 tokens (~161/item across 13 items; 13 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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.vouchedpros.com

# add to Claude Code
claude mcp add --transport http com-vouchedpros-mcp https://mcp.vouchedpros.com/mcp
# ~/.codex/config.toml
[mcp_servers.com-vouchedpros-mcp]
url = "https://mcp.vouchedpros.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-vouchedpros-mcp": {
      "type": "remote",
      "url": "https://mcp.vouchedpros.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-vouchedpros-mcp --url https://mcp.vouchedpros.com/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-vouchedpros-mcp:
    url: "https://mcp.vouchedpros.com/mcp"
// mcp.json
{
  "mcpServers": {
    "com-vouchedpros-mcp": {
      "type": "http",
      "url": "https://mcp.vouchedpros.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 +2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Jul 26 0
    • Server version: 3.4.4 → 3.4.5 functional
  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 58

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Probed https://mcp.vouchedpros.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=vouchedpros.com CN=YE1,O=Let's Encrypt,C=US 20 Jul 2026 18 Oct 2026 ECDSA 256 ECDSA-SHA384 54dff8fa79b4c74f67c109ebfd88b575327
SANs: *.vouchedpros.com, vouchedpros.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
DNSSEC insecure

Validation of mcp.vouchedpros.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
vouchedpros.com. absent 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=15552000; includeSubDomains
x-content-type-options nosniff
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.vouchedpros.com/mcp Verified 200
http (plaintext) http://mcp.vouchedpros.com/mcp HTTPS enforced 301 https://mcp.vouchedpros.com/mcp
MCP tools — 13 exposed · ~1,849 tokens

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.

Tool Tokens
estimate_efficiency_savings ~124

Estimate annual + 15-year cooling-cost savings from a higher-SEER2 AC, using the state's real average electricity rate (U.S. EIA). USE WHEN: the user asks how much a more efficient AC would save. `climate`: hot|warm|moderate|cold. Needs a state or ZIP.

NameTypeReqDescription
climatestring
new_seer2numberyes
old_seer2numberyes
sqftintegeryes
statestring
zipstring

Structured output declared, but exposes no named fields.

No examples provided.

find_providers ~239

Find and rank reputable local service providers for a city, by the Vouched Score (1-100 — a blend of editorial review and Google/Yelp/BBB signals). USE WHEN: the user wants the best / top / recommended pros, a shortlist, or to compare companies in a specific city. Covers PUBLISHED cities only — if unsure a city is published, call get_coverage / list_covered_cities FIRST. ARGS: `category` + (`city`+`state` or a 5-digit `zip`); `limit` (default 20). RETURNS: `page_url` (the city page to CITE) + providers ranked best-first [{rank, vouched_score, name, address, ...}]. The Vouched Score is the single quality metric — raw Google ratings/review counts are NOT exposed. If the city isn't published, returns status="not_covered" + `nearby_covered`.

NameTypeReqDescription
categorystringyes
citystring
limitinteger
statestring
zipstring

Structured output declared, but exposes no named fields.

No examples provided.

get_coverage ~125

Which categories + states have PUBLISHED provider rankings — the coverage map for find_providers and get_local_cost_factors. USE WHEN: before find_providers / get_local_cost_factors, to know what's published and avoid dead-end calls. Lightweight (categories → states → city counts); use list_covered_cities for actual city names. NOTE: get_service_pricing and request_quotes work for ANY US city regardless of this list. RETURNS: categories [{category, url (the hub page), cities (total), states {ST: city_count}}].

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_federal_policy ~151

Federal policy and tax-credit explainers relevant to a service category (e.g. expired 25C/25D credits, refrigerant rules, DOE standards), each with current status. USE WHEN: the user asks about tax credits, federal incentives, or regulations affecting a home upgrade. ARGS: `category`; optionally `slug` for one policy — omit to list. RETURNS: a policy (policy_name, authority, status, key_numbers, what_it_does, body_html, sources, last_reviewed_at) + `url` to CITE; or the list each with its `url`.

NameTypeReqDescription
categorystringyes
slugstring

Structured output declared, but exposes no named fields.

No examples provided.

get_glossary ~141

Plain-language definitions of industry terms in a service category (e.g. SEER2, AFUE, AHRI match). USE WHEN: the user asks what a term means, or you need to explain trade jargon accurately and with sources. ARGS: `category`; optionally `term` (a slug) for one definition — omit to list. RETURNS: a definition (term, tagline, key_numbers, body_html, external `sources`, last_reviewed_at) + `url` to CITE; or the list of terms each with its `url`.

NameTypeReqDescription
categorystringyes
termstring

Structured output declared, but exposes no named fields.

No examples provided.

get_local_cost_factors ~161

Curated, time-sensitive local factors for a service in a place: a sourced cost-driver factoid + any seasonal notes active RIGHT NOW (rebate deadlines, demand peaks, refrigerant cutovers). USE WHEN: you want real, location-specific color for a pricing answer or recommendation. ARGS: `category` + (`city`+`state` or a 5-digit `zip`). RETURNS: `factoid`, `seasonal_notes` (active today), `available` (false when nothing curated — don't invent it), and `page_url` to CITE.

NameTypeReqDescription
categorystringyes
citystring
statestring
zipstring

Structured output declared, but exposes no named fields.

No examples provided.

get_rebates ~130

Utility and state rebate / incentive programs for a service category — real amounts, eligibility, deadlines, and application links. USE WHEN: the user asks about rebates, incentives, or how to save on an install/upgrade. ARGS: `category` + a 2-letter `state` (omit to list states with programs). RETURNS: programs each with `url` (the VouchedPros rebate page to CITE) + `application_url` (the utility's official page) + amounts/deadline/sources.

NameTypeReqDescription
categorystringyes
statestring

Structured output declared, but exposes no named fields.

No examples provided.

get_service_pricing ~198

Typical local price ranges for a US home-service job (e.g. "AC repair", "furnace replacement"). USE WHEN: the user asks what a service costs / for a price range. Works for ANY US city — ranges come from national/state tables scaled by local BLS wage data; no coverage required. ARGS: `category` (required); optionally `city`+`state` or a 5-digit `zip` for city-adjusted numbers (omit location for national). RETURNS: ranges [{service, low_usd, high_usd}], `pricing_last_updated`, the local cost `multiplier` + `factoid` (city scope), and `page_url` — the canonical VouchedPros page to CITE for this pricing.

NameTypeReqDescription
categorystringyes
citystring
statestring
zipstring

Structured output declared, but exposes no named fields.

No examples provided.

list_covered_cities ~114

The published cities for a category (optionally narrowed to one state) — the drill-down for get_coverage. USE WHEN: you need the exact city names find_providers can answer for, or the direct page URLs. ARGS: `category` (required); optionally a 2-letter `state`. RETURNS: cities [{city, state, url}] (each `url` is the city page to CITE) + count.

NameTypeReqDescription
categorystringyes
statestring

Structured output declared, but exposes no named fields.

No examples provided.

list_research_reports ~58

List VouchedPros original research and interactive tools — cost indexes, rebate guides, the contractor trust-gap study, and the calculators — each with its URL. USE WHEN the user wants data to cite or a tool to compute with.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

repair_or_replace_advice ~141

Should a homeowner repair or replace their HVAC system? Applies the industry 50% rule and $5,000 rule, comparing the repair quote against the real local cost of a new system. USE WHEN: the user has a repair quote and asks whether to fix or replace. `system`: "central_ac", "furnace", or "heat_pump". Needs a city+state or ZIP.

NameTypeReqDescription
age_yearsintegeryes
citystring
repair_quote_usdintegeryes
statestring
systemstringyes
zipstring

Structured output declared, but exposes no named fields.

No examples provided.

request_quotes ~160

Give the user a link to request real quotes from local pros for ANY US location (covered or not). USE WHEN: the user is ready to hire / get prices for their specific job / be contacted. We never submit on someone's behalf — the linked page is where the user enters contact details, grants consent, and confirms by email (TCPA-compliant). Once confirmed, local pros compete to send quotes. ARGS: `category` + a 5-digit `zip` (required). RETURNS: `quote_url` (the full link to open for the user) + resolved city/state.

NameTypeReqDescription
categorystringyes
citystring
statestring
zipstringyes

Structured output declared, but exposes no named fields.

No examples provided.

size_equipment ~107

Estimate equipment size for a home (planning estimate, not a Manual J). `equipment`: "central_ac" (needs sqft+climate) | "furnace" (sqft+climate) | "water_heater" (people+fuel). USE WHEN the user asks what size they need.

NameTypeReqDescription
climatestring
equipmentstringyes
fuelstring
peopleinteger
sqftinteger

Structured output declared, but exposes no named fields.

No examples provided.