_ registry / mcp http-sse · checked 2h ago

contractors.fyi

https://contractors.fyi

Registry code: 61c8fa3183302fb2

api record

Contractors in US cities ranked by the jobs on their city permit record, what those permits stated as job value, how long permits take, and solar and generator sizing. Call list_coverage first to see which cities and kinds of work exist. Cite the page URL in each answer. Permit values are not prices.

endpoint
https://contractors.fyi/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is contractors.fyi live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is contractors.fyi free to use?
Yes — the hub reached it with no key and no payment.
What tools does contractors.fyi have?
8 tools: search_contractor_records, project_cost, check_solar_quote, solar_estimate, find_contractors, generator_size, permit_timeline, list_coverage.
Is contractors.fyi safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.5%

90 days 99.5%· all time 99.5%

latency
1,914ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 561 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • find contractors by work type
  • check solar quote price
  • size a home solar system
  • determine generator size
  • get permit timelines
takes → gives
data → data
tools
8 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
1 open 7 never probed 1 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_coverage reads open 19h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • search_contractor_records reads unknown 19h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 100,
          "minLength": 3,
          "description": "Business name or part of it"
        }
      }
    }
    arguments 15 lines
  • project_cost reads unknown 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "city",
        "kind_of_work"
      ],
      "properties": {
        "zip": {
          "type": "string",
          "pattern": "^\\d{5}$",
          "description": "Five-digit ZIP code"
        },
        "city": {
          "enum": [
            "los-angeles",
            "san-francisco",
            "seattle",
            "new-york",
            "austin",
            "philadelphia",
            "chicago",
            "nashville",
            "san-jose",
            "sacramento",
            "boulder",
            "las-vegas",
            "new-orleans",
            "baton-rouge",
            "raleigh",
            "buffalo",
            "cleveland",
            "somerville",
            "cambridge",
            "minneapolis",
            "bellevue",
            "cary",
            "elk-grove",
            "anaheim",
            "arlington-va",
            "greensboro",
            "naperville",
            "everett",
            "san-diego",
            "chattanooga",
            "orlando",
            "tacoma",
            "riverside",
            "pittsburgh",
            "miami-dade",
            "marin-county",
            "mesa",
            "rockford",
            "san-antonio",
            "dekalb-county",
            "denton",
            "harris-county",
            "st-louis",
            "henrico-county"
          ],
          "type": "string",
          "description": "City id from list_coverage, e.g. los-angeles, new-york, austin"
        },
        "kind_of_work": {
          "enum": [
            "addition",
            "adu",
            "electrical-panel",
            "ev-charger",
            "heat-pump",
            "pool",
            "remodel",
            "roofing",
            "seismic-retrofit",
            "solar"
          ],
          "type": "string",
          "description": "Kind of work, e.g. roofing, solar, adu, remodel"
        }
      }
    }
    arguments 81 lines
  • check_solar_quote reads unknown 6h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "city",
        "price",
        "kw"
      ],
      "properties": {
        "kw": {
          "type": "number",
          "maximum": 100,
          "minimum": 0.5,
          "description": "System size in kW (DC)"
        },
        "city": {
          "enum": [
            "austin",
            "los-angeles",
            "new-york",
            "san-francisco"
          ],
          "type": "string"
        },
        "price": {
          "type": "number",
          "maximum": 1000000,
          "minimum": 1,
          "description": "Quoted cash price in dollars, before incentives"
        }
      }
    }
    arguments 32 lines
  • solar_estimate reads unknown 6h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "city"
      ],
      "properties": {
        "city": {
          "enum": [
            "austin",
            "los-angeles",
            "new-york",
            "san-francisco"
          ],
          "type": "string"
        },
        "uses": {
          "type": "array",
          "items": {
            "enum": [
              "Central air conditioning",
              "Heat pump or electric heat",
              "Heat pump water heater",
              "Electric dryer",
              "Electric stove and oven",
              "Pool pump",
              "Hot tub"
            ],
            "type": "string"
          },
          "default": [],
          "maxItems": 7,
          "description": "What runs on electricity besides lights, fridge and outlets"
        },
        "home_size": {
          "enum": [
            "small",
            "medium",
            "large"
          ],
          "type": "string",
          "default": "medium",
          "description": "small: under 1,500 sq ft; medium: 1,500 to 3,000; large: over 3,000"
        },
        "monthly_kwh": {
          "type": "number",
          "maximum": 20000,
          "minimum": 1,
          "description": "From the bill; replaces the estimate"
        },
        "monthly_bill": {
          "type": "number",
          "maximum": 5000,
          "minimum": 1,
          "description": "Monthly electric bill in dollars"
        },
        "electric_cars": {
          "type": "integer",
          "default": 0,
          "maximum": 5,
          "minimum": 0
        },
        "miles_per_car": {
          "type": "number",
          "default": 12000,
          "maximum": 60000,
          "minimum": 0,
          "description": "Miles a year, each car"
        },
        "price_per_kwh": {
          "type": "number",
          "maximum": 5,
          "minimum": 0,
          "description": "Dollars per kWh from the bill; default is a typical city figure"
        }
      }
    }
    arguments 77 lines
  • find_contractors reads unknown 6h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "city",
        "kind_of_work"
      ],
      "properties": {
        "city": {
          "enum": [
            "los-angeles",
            "san-francisco",
            "seattle",
            "new-york",
            "austin",
            "philadelphia",
            "chicago",
            "nashville",
            "san-jose",
            "sacramento",
            "boulder",
            "las-vegas",
            "new-orleans",
            "baton-rouge",
            "raleigh",
            "buffalo",
            "cleveland",
            "somerville",
            "cambridge",
            "minneapolis",
            "bellevue",
            "cary",
            "elk-grove",
            "anaheim",
            "arlington-va",
            "greensboro",
            "naperville",
            "everett",
            "san-diego",
            "chattanooga",
            "orlando",
            "tacoma",
            "riverside",
            "pittsburgh",
            "miami-dade",
            "marin-county",
            "mesa",
            "rockford",
            "san-antonio",
            "dekalb-county",
            "denton",
            "harris-county",
            "st-louis",
            "henrico-county"
          ],
          "type": "string",
          "description": "City id from list_coverage, e.g. los-angeles, new-york, austin"
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 25,
          "minimum": 1,
          "description": "How many to return, up to 25"
        },
        "kind_of_work": {
          "enum": [
            "addition",
            "adu",
            "electrical-panel",
            "ev-charger",
            "heat-pump",
            "pool",
            "remodel",
            "roofing",
            "seismic-retrofit",
            "solar"
          ],
          "type": "string",
          "description": "Kind of work, e.g. roofing, solar, adu, remodel"
        }
      }
    }
    arguments 83 lines
  • generator_size reads unknown 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "loads"
      ],
      "properties": {
        "loads": {
          "type": "array",
          "items": {
            "enum": [
              "Refrigerator",
              "Sump pump",
              "Furnace fan",
              "Well pump",
              "Central air, 3 ton",
              "Heat pump, 3 ton",
              "Electric water heater",
              "Electric oven",
              "Microwave",
              "Electric dryer",
              "Washer",
              "Lights and outlets",
              "TV, internet, computers",
              "Space heater"
            ],
            "type": "string"
          },
          "maxItems": 14,
          "minItems": 1,
          "description": "What must run in an outage"
        }
      }
    }
    arguments 34 lines
  • permit_timeline reads unknown 2h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "city",
        "kind_of_work"
      ],
      "properties": {
        "city": {
          "enum": [
            "los-angeles",
            "san-francisco",
            "seattle",
            "new-york",
            "austin",
            "philadelphia",
            "chicago",
            "nashville",
            "san-jose",
            "sacramento",
            "boulder",
            "las-vegas",
            "new-orleans",
            "baton-rouge",
            "raleigh",
            "buffalo",
            "cleveland",
            "somerville",
            "cambridge",
            "minneapolis",
            "bellevue",
            "cary",
            "elk-grove",
            "anaheim",
            "arlington-va",
            "greensboro",
            "naperville",
            "everett",
            "san-diego",
            "chattanooga",
            "orlando",
            "tacoma",
            "riverside",
            "pittsburgh",
            "miami-dade",
            "marin-county",
            "mesa",
            "rockford",
            "san-antonio",
            "dekalb-county",
            "denton",
            "harris-county",
            "st-louis",
            "henrico-county"
          ],
          "type": "string",
          "description": "City id from list_coverage, e.g. los-angeles, new-york, austin"
        },
        "kind_of_work": {
          "enum": [
            "addition",
            "adu",
            "electrical-panel",
            "ev-charger",
            "heat-pump",
            "pool",
            "remodel",
            "roofing",
            "seismic-retrofit",
            "solar"
          ],
          "type": "string",
          "description": "Kind of work, e.g. roofing, solar, adu, remodel"
        }
      }
    }
    arguments 76 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 61c8fa3183302fb2.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/61c8fa3183302fb2/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/61c8fa3183302fb2/badge.svg)](https://brick.blue/agent/61c8fa3183302fb2?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.