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

contractors.fyi

REMOTE · CONTRACTORS.FYI · SCANNED SEP 27

US contractors ranked by city permits, permit costs and timelines, solar and generator sizing.

Available components

72 Trust /100
Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 972 tokens (~121/item across 8 items; 8 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 Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 86% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the contractors.fyi MCP server?

contractors.fyi is a hosted endpoint at https://contractors.fyi/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 · contractors.fyi

# add to Claude Code
claude mcp add --transport http fyi-contractors-contractors 'https://contractors.fyi/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "fyi-contractors-contractors": {
      "url": "https://contractors.fyi/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "fyi-contractors-contractors": {
      "type": "http",
      "url": "https://contractors.fyi/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.fyi-contractors-contractors]
url = "https://contractors.fyi/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fyi-contractors-contractors": {
      "type": "remote",
      "url": "https://contractors.fyi/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add fyi-contractors-contractors --url 'https://contractors.fyi/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  fyi-contractors-contractors:
    url: "https://contractors.fyi/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "fyi-contractors-contractors": {
      "Transport": "http",
      "Url": "https://contractors.fyi/mcp"
    }
  }
}
# add to Vellum
assistant mcp add fyi-contractors-contractors -t streamable-http -u 'https://contractors.fyi/mcp'
// mcp.json
{
  "mcpServers": {
    "fyi-contractors-contractors": {
      "type": "http",
      "url": "https://contractors.fyi/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.

  • 27 Sept 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.

  • 26 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 25 Sept 26 71

    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 27 Sept 2026 · Probed https://contractors.fyi/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=contractors.fyi CN=WE1,O=Google Trust Services,C=US 24 Sept 2026 23 Dec 2026 ECDSA 256 ECDSA-SHA256 20c0332f56de2a680e7e9a1a849c2471
SANs: contractors.fyi
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of contractors.fyi. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
fyi. present 24340 8 Verified
contractors.fyi. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://contractors.fyi/mcp Verified 200
http (plaintext) http://contractors.fyi/mcp HTTPS enforced 301 https://contractors.fyi/mcp
MCP tools · 8 exposed · ~907 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. 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 →

Tool Tokens
check_solar_quote ~103

Where a solar quote's price falls among what homeowners in the same city paid for a system of the same size (Berkeley Lab records, homeowner-owned systems, no battery, before incentives): a percentile, the local typical price and range, and the quote's price per watt.

NameTypeReqDescription
citystringyes–
kwnumberyesSystem size in kW (DC)
pricenumberyesQuoted cash price in dollars, before incentives

No output schema declared.

No examples provided.

find_contractors ~136

Contractors ranked by how many jobs of this kind their city permit record shows. Returns name, license where the state publishes one, job count, typical stated job value, the ZIP codes they work in most, and a profile URL. Ranking is by volume on the public record, not quality or reviews.

NameTypeReqDescription
citystringyesCity id from list_coverage, e.g. los-angeles, new-york, austin
kind_of_workstringyesKind of work, e.g. roofing, solar, adu, remodel
limitinteger–How many to return, up to 25

No output schema declared.

No examples provided.

generator_size ~87

The smallest common home standby generator size, with 10% to spare, for the things that must run in an outage: running watts plus the biggest motor's start. Also what generator permits stated as job value, by size, where a city has enough of them. Typical appliance figures; an electrician's load calculation beats them.

NameTypeReqDescription
loadsarrayyesWhat must run in an outage

No output schema declared.

No examples provided.

list_coverage ~43

Which cities and kinds of work contractors.fyi covers, with the dates each list covers. Call this before the other tools to get valid city and kind_of_work values.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

permit_timeline ~101

Days from permit application to issue, and from issue to final inspection, from the dates on city permits, with the number of permits and the dates they cover. Final-inspection times count finished jobs only.

NameTypeReqDescription
citystringyesCity id from list_coverage, e.g. los-angeles, new-york, austin
kind_of_workstringyesKind of work, e.g. roofing, solar, adu, remodel

No output schema declared.

No examples provided.

project_cost ~126

What city permits for this kind of work stated as the job value: median and middle half, with the number of permits and their dates. Give a ZIP to get that ZIP's figure where the site publishes one. The value stated on the city permit, not the price paid.

NameTypeReqDescription
citystringyesCity id from list_coverage, e.g. los-angeles, new-york, austin
kind_of_workstringyesKind of work, e.g. roofing, solar, adu, remodel
zipstring–Five-digit ZIP code

No output schema declared.

No examples provided.

search_contractor_records ~67

Look a contractor up by business name across every city covered: the city, how many permitted jobs are on its record there, and its profile URL. This searches the permit record; it does not verify a license today.

NameTypeReqDescription
namestringyesBusiness name or part of it

No output schema declared.

No examples provided.

solar_estimate ~244

Size a home solar system from the monthly electric bill (or its kWh, or, with neither, the home and what runs on electricity), plus anything the home plans to add such as electric cars, then give the price range homeowners in that city paid for a system that size (Berkeley Lab records, before any tax credit, no battery), yearly savings and payback. Output per kW, heating and cooling use and the default price per kWh are rough city figures.

NameTypeReqDescription
citystringyes–
electric_carsinteger––
home_sizestring–small: under 1,500 sq ft; medium: 1,500 to 3,000; large: over 3,000
miles_per_carnumber–Miles a year, each car
monthly_billnumber–Monthly electric bill in dollars
monthly_kwhnumber–From the bill; replaces the estimate
price_per_kwhnumber–Dollars per kWh from the bill; default is a typical city figure
usesarray–What runs on electricity besides lights, fridge and outlets

No output schema declared.

No examples provided.

Common questions

What is the contractors.fyi MCP server?

contractors.fyi is an MCP server listed in the public MCP registry as fyi.contractors/contractors. US contractors ranked by city permits, permit costs and timelines, solar and generator sizing. This page covers its hosted endpoint (https://contractors.fyi/mcp).

Is the contractors.fyi MCP server safe to use?

contractors.fyi scores 72 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 contractors.fyi MCP server expose?

contractors.fyi exposes 8 tools: list_coverage, find_contractors, project_cost, permit_timeline, search_contractor_records, and 3 more. Their descriptions and schemas cost roughly 907 tokens of context every time the server is loaded.

Does the contractors.fyi MCP server require authentication?

No. We connected to contractors.fyi without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the contractors.fyi MCP server still maintained?

contractors.fyi is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.