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

remedybridge-tools

https://remedybridge.co.uk

Registry code: 8144ea30c12f502a

api record

Free, read-only tools from RemedyBridge for tenants in England and Wales with repairs, damp and mould or disrepair in a rented home. Use search_housing_repair_help for questions about a landlord’s repair duties, Awaab’s Law, complaints, the Housing Ombudsman, Environmental Health and the pre-action protocol, and for what a housing term means; use check_awaabs_law_deadlines, calculate_landlord_complaint_deadlines and calculate_pre_action_protocol_timetable for dates, which count working days and leave out bank holidays; use get_repair_letter_template for a letter to send a landlord (it returns…

endpoint
https://remedybridge.co.uk/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 remedybridge-tools live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is remedybridge-tools free to use?
Yes — the hub reached it with no key and no payment.
What tools does remedybridge-tools have?
6 tools: search_housing_repair_help, check_awaabs_law_deadlines, get_repair_letter_template, calculate_landlord_complaint_deadlines, calculate_pre_action_protocol_timetable, build_evidence_checklist.
Is remedybridge-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
236ms

last good check

priced tools
0

of 6 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

_ what it can do 6 tools
1 open 5 never probed 1 of 6 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.

  • build_evidence_checklist open 1h ago

    Lists the evidence worth gathering about disrepair in a rented home, for the problems and the landlord given: what everyone should keep (dated photos, copies of every report, reference numbers, appointments and complaint letters), then what each problem needs and what each kind of landlord’s case needs. Problems: "damp" (damp or mould), "leak" (leaks or water ingress), "heating" (heating or boiler), "electrics" (unsafe electrics), "windows" (windows or doors), "pests" (pests or vermin), "structural" (structural or plaster). It asks for no personal details.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "landlord": {
          "enum": [
            "council",
            "association",
            "private"
          ],
          "type": "string",
          "description": "\"council\", \"association\" (a housing association) or \"private\"."
        },
        "problems": {
          "type": "array",
          "items": {
            "enum": [
              "damp",
              "leak",
              "heating",
              "electrics",
              "windows",
              "pests",
              "structural"
            ],
            "type": "string"
          },
          "maxItems": 7,
          "description": "The problems in the home, any of \"damp\", \"leak\", \"heating\", \"electrics\", \"windows\", \"pests\", \"structural\"."
        }
      },
      "additionalProperties": false
    }
    arguments 32 lines
  • search_housing_repair_help unknown never probed

    Answers tenants’ questions about repairs, damp and mould and disrepair in rented homes in England and Wales, from RemedyBridge’s published guides: what a landlord must repair and how quickly, Awaab’s Law, section 11 of the Landlord and Tenant Act 1985 and fitness for human habitation, reporting repairs, landlord complaints and the Housing Ombudsman, Environmental Health and HHSRS, withholding rent, eviction after a complaint, the pre-action protocol and evidence. It searches the quick answer and the questions and answers of every guide, and a glossary of 54 housing terms, and returns each answer with the link to its page. Use it for "what is", "who is responsible", "how long" and "what can I do" questions. It does not assess anyone’s situation.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "maxLength": 200,
          "description": "The question or term in plain words, e.g. \"how long does my landlord have to fix a leak\" or \"section 11\"."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • check_awaabs_law_deadlines unknown never probed

    Works out the dates Awaab’s Law gives a council or housing association in England (the Hazards in Social Housing (Prescribed Requirements) (England) Regulations 2025, SI 2025/1042) to deal with damp or mould: investigate it, give the tenant a written summary, finish any safety work and start any further work. It counts working days from the day after the landlord found out, leaving out weekends and bank holidays in England and Wales, and says whether each date has passed. For an emergency hazard it gives the 24-hour rule; for other hazards it gives the position on Awaab’s Law Phase 2 from the site’s legal register. It says when Awaab’s Law does not apply (private landlords, Wales, shared ownership and long leases). It does not decide whether a hazard is significant, and a missed date is a dated failure, not an entitlement to anything.

    mcp-tool

    {
      "type": "object",
      "required": [
        "landlord"
      ],
      "properties": {
        "asAt": {
          "type": "string",
          "format": "date",
          "description": "Work it out as at this date instead of today in England (YYYY-MM-DD)."
        },
        "hazard": {
          "enum": [
            "damp_mould",
            "emergency",
            "other"
          ],
          "type": "string",
          "description": "For a council or housing association: \"damp_mould\", \"emergency\" (something putting someone in immediate danger, such as a gas leak or exposed live wiring) or \"other\" (another problem, such as a broken boiler, a broken window or unsafe stairs)."
        },
        "awareOn": {
          "type": "string",
          "format": "date",
          "description": "Damp or mould: the day the landlord found out, usually the day it was first reported (in writing, if it was) (YYYY-MM-DD)."
        },
        "landlord": {
          "enum": [
            "council",
            "housing_association",
            "private",
            "wales",
            "ownership"
          ],
          "type": "string",
          "description": "Who the landlord is: \"council\" or \"housing_association\" (in England), \"private\" (a private landlord or letting agent), \"wales\" (any landlord in Wales) or \"ownership\" (the tenant owns a share, or has a long lease)."
        },
        "investigatedOn": {
          "type": "string",
          "format": "date",
          "description": "Damp or mould: the day the landlord’s investigation finished, if it has. Leave out if it has not investigated, or if not known (YYYY-MM-DD)."
        }
      },
      "additionalProperties": false
    }
    arguments 44 lines
  • get_repair_letter_template unknown never probed

    Gives the text of a letter for a tenant to send their landlord, with [bracketed] gaps to fill in: "first-report" to report a repair in writing for the first time, "chaser" when it was reported and nothing has happened, "complaint" to make a formal complaint under the landlord’s complaints procedure (citing section 11 of the Landlord and Tenant Act 1985 in England, or sections 91 and 92 of the Renting Homes (Wales) Act 2016 in Wales), or "awaabs-law" to ask a council or housing association in England to deal with a hazard under Awaab’s Law. The Awaab’s Law letter is given only to a tenant of a council or housing association in England with a tenancy (not a licence, shared ownership or a long lease). It never takes the tenant’s name, address or details: fill in the gaps with them. The letters state facts and make a request; they promise no outcome.

    mcp-tool

    {
      "type": "object",
      "required": [
        "template"
      ],
      "properties": {
        "tenure": {
          "enum": [
            "tenancy",
            "licence",
            "shared_or_lease",
            "unsure"
          ],
          "type": "string",
          "description": "How the tenant occupies the home: \"tenancy\", \"licence\" (some supported or temporary housing), \"shared_or_lease\" (shared ownership or a long lease) or \"unsure\" (default). Only a tenancy gets the Awaab’s Law letter."
        },
        "country": {
          "enum": [
            "england",
            "wales"
          ],
          "type": "string",
          "description": "Where the home is: \"england\" (default) or \"wales\". Wales has its own housing law, and the complaint letter cites a different Act."
        },
        "landlord": {
          "enum": [
            "social",
            "private"
          ],
          "type": "string",
          "description": "\"social\" for a council or housing association (default), or \"private\" for a private landlord or letting agent."
        },
        "template": {
          "enum": [
            "first-report",
            "chaser",
            "complaint",
            "awaabs-law"
          ],
          "type": "string",
          "description": "Which letter: \"first-report\", \"chaser\", \"complaint\" or \"awaabs-law\"."
        }
      },
      "additionalProperties": false
    }
    arguments 45 lines
  • calculate_landlord_complaint_deadlines unknown 1h ago

    Works out when a council or housing association in England must acknowledge and answer a tenant’s complaint under the Housing Ombudsman’s Complaint Handling Code (2024): at stage 1, acknowledge within 5 working days and respond within 10 working days of acknowledging (paras 6.2 to 6.4); at stage 2, acknowledge within 5 and respond within 20 (paras 6.11 to 6.15), each with the longest extension. It counts working days, leaving out weekends and bank holidays in England and Wales; a complaint received at a weekend or on a bank holiday counts from the next working day. Give the dates the landlord acknowledged or answered, if it has, to see whether each was on time. It says when the Code does not usually apply (private landlords, Wales). It never says what a complaint will achieve.

    mcp-tool

    {
      "type": "object",
      "required": [
        "landlord"
      ],
      "properties": {
        "asAt": {
          "type": "string",
          "format": "date",
          "description": "Work it out as at this date instead of today in England (YYYY-MM-DD)."
        },
        "stage": {
          "enum": [
            "1",
            "2"
          ],
          "type": "string",
          "description": "For a council or housing association: \"1\" for a complaint, or \"2\" when the tenant has asked for it to go to stage 2 after an unsatisfactory stage 1 answer."
        },
        "landlord": {
          "enum": [
            "council",
            "housing_association",
            "private",
            "wales"
          ],
          "type": "string",
          "description": "Who the landlord is: \"council\" or \"housing_association\" (in England), \"private\" (a private landlord or letting agent) or \"wales\" (any landlord in Wales)."
        },
        "receivedOn": {
          "type": "string",
          "format": "date",
          "description": "The day the landlord received the complaint (stage 1) or the request for stage 2. Sent by email or an online form: the day it was sent (YYYY-MM-DD)."
        },
        "respondedOn": {
          "type": "string",
          "format": "date",
          "description": "The day the landlord gave its response at this stage, if it has (YYYY-MM-DD)."
        },
        "acknowledgedOn": {
          "type": "string",
          "format": "date",
          "description": "The day the landlord acknowledged it, if it has (YYYY-MM-DD)."
        }
      },
      "additionalProperties": false
    }
    arguments 47 lines
  • calculate_pre_action_protocol_timetable unknown 1h ago

    Works out the timetable the Pre-Action Protocol for Housing Conditions Claims (England) sets after a tenant’s letter of claim: the letter is treated as received two days after its date, the landlord should reply within 20 working days of that (paras 6.2 and 7.2(a)), the inspection should follow within 20 working days of the reply (para 7.4(a)), the expert’s report or agreed schedule within 10 working days of the inspection (para 7.4(b) and (d)), and the landlord’s full response within 20 working days of receiving it (para 6.3). Give the later dates as they happen to see each next date and whether each step was on time. It counts working days, leaving out weekends and bank holidays in England and Wales. The protocol calls these long stops, and they can be changed by agreement (para 9). Wales has its own protocol, with the same periods for the reply, the inspection and the report.

    mcp-tool

    {
      "type": "object",
      "required": [
        "letterDate"
      ],
      "properties": {
        "asAt": {
          "type": "string",
          "format": "date",
          "description": "Work it out as at this date instead of today in England (YYYY-MM-DD)."
        },
        "replyDate": {
          "type": "string",
          "format": "date",
          "description": "The day the landlord replied to the letter of claim, if it has (YYYY-MM-DD)."
        },
        "letterDate": {
          "type": "string",
          "format": "date",
          "description": "The date written on the letter of claim, not the day the landlord got it (YYYY-MM-DD)."
        },
        "inspectionDate": {
          "type": "string",
          "format": "date",
          "description": "The day the property was inspected (by a single joint expert, or at a joint inspection), if it has been. Needs replyDate (YYYY-MM-DD)."
        },
        "reportReceivedDate": {
          "type": "string",
          "format": "date",
          "description": "The day the expert’s report or the agreed schedule arrived, if it has. Needs inspectionDate (YYYY-MM-DD)."
        }
      },
      "additionalProperties": false
    }
    arguments 34 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 8144ea30c12f502a.

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