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

andare-homes-free-tools

https://andarehomes.com

Registry code: d34f6d883f8c0388

api record

Free renovation tools for Toronto and Ontario homeowners from Andare Homes. Each tool returns the answer, its source and a link to the tool page and the free quote form. Preliminary planning only.

endpoint
https://andarehomes.com/mcp
protocol
streamable-http ·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 andare-homes-free-tools live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is andare-homes-free-tools free to use?
Yes — the hub reached it with no key and no payment.
What tools does andare-homes-free-tools have?
11 tools: toronto-building-permit-checker, garden-suite-zoning-checker, toronto-permit-review-time-calculator, egress-window-size-calculator, second-suite-requirements-checklist, deck-permit-and-guard-checker-toronto, stair-calculator-ontario, renovation-materials-calculator, ….
Is andare-homes-free-tools 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
100%

90 days 100%· all time 100%

latency
189ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 11 tools
11 never probed 0 of 11 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.

  • toronto-building-permit-checker unknown never probed

    Says whether a project in Toronto needs a building permit, usually does not, or depends, with the City source for the answer. Preliminary planning only. Example: /api/tools/toronto-building-permit-checker?project=deck&h=high&att=yes&exit=no

    mcp-tool

    {
      "type": "object",
      "required": [
        "project"
      ],
      "properties": {
        "h": {
          "enum": [
            "low",
            "high",
            "unsure"
          ],
          "type": "string",
          "description": "deck: How high will the finished deck level be above the adjacent finished grade?"
        },
        "bt": {
          "enum": [
            "house",
            "other"
          ],
          "type": "string",
          "description": "opening: What kind of building is it?"
        },
        "ht": {
          "enum": [
            "t12",
            "t20",
            "over"
          ],
          "type": "string",
          "description": "fence: How tall will it be?"
        },
        "lb": {
          "enum": [
            "yes",
            "no",
            "unsure"
          ],
          "type": "string",
          "description": "wall: Is the wall load bearing?"
        },
        "att": {
          "enum": [
            "yes",
            "no"
          ],
          "type": "string",
          "description": "deck: Will the deck be attached to the house? | shed: Will it be attached to a house, garage or any other structure?"
        },
        "chg": {
          "enum": [
            "yes",
            "no",
            "unsure"
          ],
          "type": "string",
          "description": "opening: Will the work affect the structural support or create a new exit?"
        },
        "exit": {
          "enum": [
            "yes",
            "no",
            "unsure"
          ],
          "type": "string",
          "description": "deck: Will it have a roof, or will it be part of a required exit from the house?"
        },
        "kind": {
          "enum": [
            "new",
            "repl",
            "add",
            "valve"
          ],
          "type": "string",
          "description": "opening: What is the work? | plumbing: What is the plumbing work?"
        },
        "mech": {
          "enum": [
            "yes",
            "no"
          ],
          "type": "string",
          "description": "basement: Will it include new plumbing or heating work?"
        },
        "pool": {
          "enum": [
            "yes",
            "no"
          ],
          "type": "string",
          "description": "fence: Is the fence a swimming pool enclosure?"
        },
        "size": {
          "enum": [
            "small",
            "exact",
            "big"
          ],
          "type": "string",
          "description": "shed: What is the gross floor area?"
        },
        "plumb": {
          "enum": [
            "yes",
            "no"
          ],
          "type": "string",
          "description": "kitchen: Will you add or move plumbing, such as relocating a sink, shower, tub, toilet or drain? | shed: Will it have plumbing?"
        },
        "scope": {
          "enum": [
            "yes",
            "no"
          ],
          "type": "string",
          "description": "kitchen: Is the work limited to replacing cabinets, counters, finishes and fixtures in the same locations?"
        },
        "suite": {
          "enum": [
            "yes",
            "no"
          ],
          "type": "string",
          "description": "basement: Will the work create a second suite or any additional dwelling unit?"
        },
        "walls": {
          "enum": [
            "yes",
            "no"
          ],
          "type": "string",
          "description": "kitchen: Will you add or remove any walls or change any openings?"
        },
        "where": {
          "enum": [
            "front",
            "other"
          ],
          "type": "string",
          "description": "fence: Where will the fence be?"
        },
        "struct": {
          "enum": [
            "yes",
            "no",
            "unsure"
          ],
          "type": "string",
          "description": "basement: Will it include structural or material alterations, such as adding or removing walls, excavation, underpinning or a new basement entrance? | roofing: Will the work include any structural repair, such as replacing rafters, trusses or framing, or changing the roof shape?"
        },
        "project": {
          "enum": [
            "basement",
            "deck",
            "wall",
            "opening",
            "kitchen",
            "plumbing",
            "shed",
            "roofing",
            "fence"
          ],
          "type": "string",
          "description": "What is being built"
        }
      }
    }
    arguments 168 lines
  • garden-suite-zoning-checker unknown never probed

    Checks height, separation, floor area, setbacks and lot coverage of a garden suite against Toronto By-law 849-2025. Preliminary planning only. Example: /api/tools/garden-suite-zoning-checker?zone=yes&laneway=no&lot_area=400&lot_depth=40&lot_frontage=10&house_gfa=180&house_footprint=90&ancillary_footprint=40&suite_height=4&separation=5&suite_gfa=50&rear_setback=2&side_setback=1.5&one_storey=yes&rear_openings=no&side_openings=yes

    mcp-tool

    {
      "type": "object",
      "required": [
        "zone",
        "laneway",
        "lot_area",
        "lot_depth",
        "lot_frontage",
        "house_gfa",
        "house_footprint",
        "ancillary_footprint",
        "suite_height",
        "separation",
        "suite_gfa",
        "rear_setback",
        "side_setback",
        "one_storey",
        "rear_openings",
        "side_openings"
      ],
      "properties": {
        "zone": {
          "enum": [
            "yes",
            "no",
            "unsure"
          ],
          "type": "string",
          "description": "Property is in a residential zone (R, RD, RS, RT, RM)"
        },
        "laneway": {
          "enum": [
            "yes",
            "no"
          ],
          "type": "string",
          "description": "Property abuts a public laneway"
        },
        "lot_area": {
          "type": "number",
          "description": "Lot area (m2)"
        },
        "house_gfa": {
          "type": "number",
          "description": "House gross floor area, all floors (m2)"
        },
        "lot_depth": {
          "type": "number",
          "description": "Lot depth (m)"
        },
        "suite_gfa": {
          "type": "number",
          "description": "Suite gross floor area, all floors including a basement (m2)"
        },
        "one_storey": {
          "enum": [
            "yes",
            "no"
          ],
          "type": "string",
          "description": "Suite is one storey"
        },
        "separation": {
          "type": "number",
          "description": "Distance from the main wall of the house (m)"
        },
        "lot_frontage": {
          "type": "number",
          "description": "Lot frontage (m)"
        },
        "rear_setback": {
          "type": "number",
          "description": "Rear yard setback (m)"
        },
        "side_setback": {
          "type": "number",
          "description": "Smallest side yard setback (m)"
        },
        "suite_height": {
          "type": "number",
          "description": "Suite height from average grade (m)"
        },
        "rear_openings": {
          "enum": [
            "yes",
            "no"
          ],
          "type": "string",
          "description": "Rear lot line abuts a residential-zone lot and the rear wall has openings more than 4.0 m above grade"
        },
        "side_openings": {
          "enum": [
            "yes",
            "no"
          ],
          "type": "string",
          "description": "Side wall facing a side lot line (not a street) has doors or windows"
        },
        "house_footprint": {
          "type": "number",
          "description": "House footprint (m2)"
        },
        "ancillary_footprint": {
          "type": "number",
          "description": "Footprint of all ancillary buildings together, including the suite (m2)"
        }
      }
    }
    arguments 108 lines
  • toronto-permit-review-time-calculator unknown never probed

    Gives the last day of the City of Toronto published review time for a complete building permit application, by review stream. Preliminary planning only. Example: /api/tools/toronto-permit-review-time-calculator?stream=house&date=2026-12-01&zoning_certificate=yes

    mcp-tool

    {
      "type": "object",
      "required": [
        "stream",
        "date",
        "zoning_certificate"
      ],
      "properties": {
        "date": {
          "type": "string",
          "description": "Date the complete application is taken in (YYYY-MM-DD)"
        },
        "stream": {
          "enum": [
            "house",
            "small",
            "large",
            "complex",
            "express"
          ],
          "type": "string",
          "description": "Review stream: house = House Stream (10 business days); small = Small Building Stream (15); large = Large and Complex, large building (20); complex = Large and Complex, complex building (30); express = Express Services (goal of 3)"
        },
        "zoning_certificate": {
          "enum": [
            "yes",
            "no"
          ],
          "type": "string",
          "description": "Application includes an issued Zoning Applicable Law Certificate and all fees paid"
        }
      }
    }
    arguments 33 lines
  • egress-window-size-calculator unknown never probed

    Tests a bedroom escape window against Ontario Building Code Article 9.9.10.1: open area of at least 0.35 m2, no dimension under 380 mm, sill height and window well clearance. Preliminary planning only. Example: /api/tools/egress-window-size-calculator?units=mm&type=casement&width=600&height=700&floor=basement&well=yes&well_clearance=600

    mcp-tool

    {
      "type": "object",
      "required": [
        "type",
        "width",
        "height",
        "floor"
      ],
      "properties": {
        "sill": {
          "type": "number",
          "description": "Sill height above the floor (tested only when floor is above) (units)"
        },
        "type": {
          "enum": [
            "casement",
            "awning",
            "single-hung",
            "double-hung",
            "sliding",
            "hopper",
            "other"
          ],
          "type": "string",
          "description": "Window type"
        },
        "well": {
          "enum": [
            "yes",
            "no"
          ],
          "type": "string",
          "description": "The window opens into a window well"
        },
        "floor": {
          "enum": [
            "basement",
            "above"
          ],
          "type": "string",
          "description": "basement = window in a basement area; above = any other floor"
        },
        "units": {
          "enum": [
            "mm",
            "in"
          ],
          "type": "string",
          "description": "Units of width, height, sill and clearance"
        },
        "width": {
          "type": "number",
          "description": "Clear width of the unobstructed open portion with the window fully open (units)"
        },
        "height": {
          "type": "number",
          "description": "Clear height of the unobstructed open portion with the window fully open (units)"
        },
        "well_clearance": {
          "type": "number",
          "description": "Clearance in front of the window inside the well (units)"
        }
      }
    }
    arguments 64 lines
  • second-suite-requirements-checklist unknown never probed

    A checklist of Ontario Building Code, Planning Act, Fire Code and City of Toronto items to check before adding a secondary suite to a house, each with its section number. Preliminary planning only. Example: /api/tools/second-suite-requirements-checklist?building=detached&smaller=yes&units_now=1&location=basement&fuel=yes&parking=one&rental=yes

    mcp-tool

    {
      "type": "object",
      "required": [
        "building",
        "smaller",
        "units_now",
        "location",
        "fuel",
        "parking",
        "rental"
      ],
      "properties": {
        "fuel": {
          "enum": [
            "yes",
            "no",
            "unsure"
          ],
          "type": "string",
          "description": "A fuel-burning appliance, flue, fireplace or attached garage is in or next to the suite"
        },
        "rental": {
          "enum": [
            "yes",
            "no",
            "unsure"
          ],
          "type": "string",
          "description": "The suite will be rented"
        },
        "parking": {
          "enum": [
            "none",
            "one",
            "more"
          ],
          "type": "string",
          "description": "Parking spaces available for the suite"
        },
        "smaller": {
          "enum": [
            "yes",
            "no"
          ],
          "type": "string",
          "description": "The new unit will be smaller than the main unit"
        },
        "building": {
          "enum": [
            "detached",
            "semi",
            "row",
            "other"
          ],
          "type": "string",
          "description": "Existing building type"
        },
        "location": {
          "enum": [
            "basement",
            "above",
            "addition"
          ],
          "type": "string",
          "description": "Where the suite will be"
        },
        "units_now": {
          "enum": [
            "1",
            "2"
          ],
          "type": "string",
          "description": "Dwelling units in the house now"
        }
      }
    }
    arguments 76 lines
  • deck-permit-and-guard-checker-toronto unknown never probed

    Says whether a deck in Toronto needs a building permit, whether a guard is required, the minimum guard height, opening size and stair handrail rule, from the City of Toronto and Ontario Building Code Part 9. Preliminary planning only. Example: /api/tools/deck-permit-and-guard-checker-toronto?units=mm&height=900&attached=yes&roofed=no&exit=no&risers=4&guard_height=900&gap=90

    mcp-tool

    {
      "type": "object",
      "required": [
        "height",
        "attached",
        "roofed",
        "exit"
      ],
      "properties": {
        "gap": {
          "type": "number",
          "description": "Planned clear opening between pickets or balusters (units)"
        },
        "exit": {
          "enum": [
            "yes",
            "no",
            "unsure"
          ],
          "type": "string",
          "description": "The deck forms part of an exit required under the Building Code"
        },
        "units": {
          "enum": [
            "mm",
            "in"
          ],
          "type": "string",
          "description": "Units of height, guard height and gap"
        },
        "height": {
          "type": "number",
          "description": "Height of the finished deck surface above the adjacent finished grade (units)"
        },
        "risers": {
          "type": "number",
          "description": "Number of risers on the deck stairs (whole number)"
        },
        "roofed": {
          "enum": [
            "yes",
            "no"
          ],
          "type": "string",
          "description": "The deck has a roof"
        },
        "attached": {
          "enum": [
            "yes",
            "no"
          ],
          "type": "string",
          "description": "The deck is attached to the house"
        },
        "guard_height": {
          "type": "number",
          "description": "Planned guard height (units)"
        }
      }
    }
    arguments 60 lines
  • stair-calculator-ontario unknown never probed

    Gives the number of risers allowed for a total rise, the rise and run of each option, and tests headroom and width against Ontario Building Code Part 9 Section 9.8. Preliminary planning only. Example: /api/tools/stair-calculator-ontario?units=mm&type=private&rise=2600&run=3500&headroom=1980&width=900

    mcp-tool

    {
      "type": "object",
      "required": [
        "rise"
      ],
      "properties": {
        "run": {
          "type": "number",
          "description": "Total horizontal run available (units)"
        },
        "rise": {
          "type": "number",
          "description": "Total rise from finished floor to finished floor (units)"
        },
        "type": {
          "enum": [
            "private",
            "public"
          ],
          "type": "string",
          "description": "private = stairs inside or outside a house or dwelling unit; public = public stairs in a residential building"
        },
        "units": {
          "enum": [
            "mm",
            "in"
          ],
          "type": "string",
          "description": "Units of rise, run, headroom and width"
        },
        "width": {
          "type": "number",
          "description": "Stair width (units)"
        },
        "headroom": {
          "type": "number",
          "description": "Clear height over the stair (units)"
        }
      }
    }
    arguments 40 lines
  • renovation-materials-calculator unknown never probed

    How much paint, how many drywall sheets or how many boxes of flooring a rectangular room needs, with an adjustable waste allowance. Quantities only. Preliminary planning only. Example: /api/tools/renovation-materials-calculator?material=paint&units=ft&length=12&width=10&height=8&openings=40&coats=2&coverage=350

    mcp-tool

    {
      "type": "object",
      "required": [
        "material",
        "length",
        "width"
      ],
      "properties": {
        "coats": {
          "type": "number",
          "description": "Number of coats (paint)"
        },
        "sheet": {
          "enum": [
            "8",
            "10",
            "12"
          ],
          "type": "string",
          "description": "Drywall sheet length in feet, 4 ft wide (drywall)"
        },
        "units": {
          "enum": [
            "ft",
            "m"
          ],
          "type": "string",
          "description": "ft = feet, sq ft and gallons; m = metres, m2 and litres"
        },
        "waste": {
          "type": "number",
          "description": "Waste allowance in percent (drywall and floor) (%)"
        },
        "width": {
          "type": "number",
          "description": "Room width (units)"
        },
        "height": {
          "type": "number",
          "description": "Ceiling height (paint and drywall) (units)"
        },
        "length": {
          "type": "number",
          "description": "Room length (units)"
        },
        "ceiling": {
          "enum": [
            "yes",
            "no"
          ],
          "type": "string",
          "description": "Include the ceiling (paint and drywall)"
        },
        "coverage": {
          "type": "number",
          "description": "Coverage printed on the paint can (paint) (sq ft per gallon or m2 per litre)"
        },
        "material": {
          "enum": [
            "paint",
            "drywall",
            "floor"
          ],
          "type": "string",
          "description": "What to calculate"
        },
        "openings": {
          "type": "number",
          "description": "Doors and windows to subtract (paint and drywall) (area in sq ft or m2)"
        },
        "box_coverage": {
          "type": "number",
          "description": "Coverage printed on one box of flooring (floor) (sq ft or m2)"
        }
      }
    }
    arguments 76 lines
  • accessible-ramp-and-doorway-calculator unknown 2h ago

    Ramp length for a rise at the Ontario Building Code 1 in 12 gradient, a slope check, or a doorway clear width check, using Section 3.8. Preliminary planning only. Example: /api/tools/accessible-ramp-and-doorway-calculator?mode=len&units=mm&rise=600

    mcp-tool

    {
      "type": "object",
      "required": [
        "mode"
      ],
      "properties": {
        "run": {
          "type": "number",
          "description": "Horizontal run (mode slope) (units)"
        },
        "door": {
          "enum": [
            "path",
            "suite-wide",
            "suite-narrow"
          ],
          "type": "string",
          "description": "Which doorway (mode door): path = barrier-free path of travel; suite-wide = bathroom or bedroom door in a suite served by a corridor 1,060 mm or wider; suite-narrow = same, corridor narrower than 1,060 mm"
        },
        "mode": {
          "enum": [
            "len",
            "slope",
            "door"
          ],
          "type": "string",
          "description": "len = ramp length needed for a rise (needs rise); slope = check an existing slope (needs rise and run); door = doorway clear width (needs width and door)"
        },
        "rise": {
          "type": "number",
          "description": "Total rise (modes len and slope) (units)"
        },
        "units": {
          "enum": [
            "mm",
            "in"
          ],
          "type": "string",
          "description": "Units of rise, run and width"
        },
        "width": {
          "type": "number",
          "description": "Clear width with the door open (mode door) (units)"
        }
      }
    }
    arguments 46 lines
  • basement-ceiling-height-and-egress-checker unknown 2h ago

    Tests basement ceiling height, height under beams and ducts, and stair headroom against Ontario Building Code Part 9, for a house basement or a secondary suite. Window sizes are tested by the egress window size calculator. Preliminary planning only. Example: /api/tools/basement-ceiling-height-and-egress-checker?units=mm&type=suite&ceiling=2000&obstruction=1900&stair=1980

    mcp-tool

    {
      "type": "object",
      "required": [
        "type",
        "ceiling"
      ],
      "properties": {
        "type": {
          "enum": [
            "house",
            "suite"
          ],
          "type": "string",
          "description": "house = basement of a house without a secondary suite; suite = secondary suite"
        },
        "share": {
          "type": "number",
          "description": "house only: percent of the basement floor area with a ceiling of 2,100 mm or more (default 100 when the ceiling is 2,100 mm or more, otherwise 0) (%)"
        },
        "stair": {
          "type": "number",
          "description": "Clear height over the basement stair, measured from the line through the tread nosings (units)"
        },
        "units": {
          "enum": [
            "mm",
            "in"
          ],
          "type": "string",
          "description": "Units of every height"
        },
        "bedroom": {
          "enum": [
            "yes",
            "no"
          ],
          "type": "string",
          "description": "house only: a bedroom is planned in the basement"
        },
        "ceiling": {
          "type": "number",
          "description": "Finished ceiling height over the main part of the space, floor to underside of the finished ceiling (units)"
        },
        "bedroom_low": {
          "type": "number",
          "description": "house with bedroom only: lowest ceiling in the bedroom (units)"
        },
        "obstruction": {
          "type": "number",
          "description": "Lowest clear height under a beam or duct (units)"
        },
        "bedroom_share": {
          "type": "number",
          "description": "house with bedroom only: percent of the required bedroom floor area with a ceiling of 2,300 mm or more (%)"
        }
      }
    }
    arguments 57 lines
  • bathroom-exhaust-fan-calculator unknown 2h ago

    Minimum bathroom exhaust fan rating in CFM from room size, ceiling height and fixtures, using the Home Ventilating Institute guidance. Preliminary planning only. Example: /api/tools/bathroom-exhaust-fan-calculator?units=ft&length=8&width=10&height=8

    mcp-tool

    {
      "type": "object",
      "required": [
        "length",
        "width"
      ],
      "properties": {
        "units": {
          "enum": [
            "ft",
            "m"
          ],
          "type": "string",
          "description": "Units of length, width and height"
        },
        "width": {
          "type": "number",
          "description": "Room width (units)"
        },
        "height": {
          "type": "number",
          "description": "Ceiling height (units)"
        },
        "length": {
          "type": "number",
          "description": "Room length (units)"
        },
        "fixtures": {
          "type": "string",
          "description": "Comma separated fixtures in the room; needed only when the room is over 100 sq ft"
        }
      }
    }
    arguments 33 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 d34f6d883f8c0388.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d34f6d883f8c0388/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/d34f6d883f8c0388/badge.svg)](https://brick.blue/agent/d34f6d883f8c0388?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.