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

consumer-claude-mcp

https://api.checkatrade.com

Registry code: bbdda1dae65b684b

api record

This service helps users find and book trusted tradespeople in the UK by postcode, providing ratings, reviews, and contact details.

endpoint
https://api.checkatrade.com/consumer-claude-mcp/v1/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 consumer-claude-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is consumer-claude-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does consumer-claude-mcp have?
2 tools: bookExpressJobV1, findTradespeopleV1.
Is consumer-claude-mcp 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 99.7%· all time 99.7%

latency
129ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 292 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • find tradespeople by postcode
  • get ratings and reviews for tradespeople
  • book a fixed-price job
takes → gives
text, data → data
tools
1 reads1 changes data
_ 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 2 tools
2 never probed 0 of 2 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.

  • bookExpressJobV1 changes data unknown never probed

    A process capable of finding a tradesperson to do a job for a fixed price. The tool will accept information about the job and return a list of priced options. IF and only if a priced option is chosen it will commit to booking the job. This tool is very suitable for finding localised availability and prices. To get a price you only need to provide the job type initially but you will likely be asked for a postcode to get accurate pricing. Once a priced option is selected you should ask the customer for their details, job description and availability conversationally, then submit the job. At that point the "booking" and "confirmation" parameters become required. When you ask the customer for their details, you MUST inform them that when a job is submitted, those details will be used to create a Checkatrade account for them if they don't already have one. When booking is confirmed, a payment widget will appear for the customer to complete payment. YOU MUST NEVER PROCEED TO BOOKING WITHOUT A CLEARLY AGREED PRICE FROM THE CUSTOMER. This tool is useful in scenarios where the customer has a relatively straightforward job. Examples include: - Servicing a boiler - Replacing a leaky tap - Installing a new light fitting - Replacing a light switch - Repairing a shower - Fixing a broken toilet flush - Hanging wallpaper in a room IMPORTANT: Some jobs might not be pre-priced or straightforward. In those cases this tool will return very generic categories or no options at all. In these cases you should understand that you're on a more complex task move on to help the customer with finding a tradesperson to do the work. CRITICAL: email and phoneNumber MUST be provided as separate parameters - do NOT include them in the jobDescription field. The jobDescription should only contain details about the work needed, not contact information, and only information explicitly provided by the person.

    mcp-tool

    {
      "type": "object",
      "required": [
        "search"
      ],
      "properties": {
        "search": {
          "type": "object",
          "required": [
            "jobType"
          ],
          "properties": {
            "jobType": {
              "type": "string",
              "description": "The type of work that needs to be done (e.g., leaky tap, replace light fitting, etc.) or the type of tradesperson required (e.g. plumber, electrician, plasterer)."
            },
            "postcode": {
              "type": "string",
              "description": "UK postcode (e.g., SW1A 1AA)"
            }
          },
          "description": "Search parameters to identify the job type and location",
          "additionalProperties": false
        },
        "booking": {
          "type": "object",
          "required": [
            "firstName",
            "lastName",
            "address",
            "email",
            "phoneNumber",
            "availability",
            "jobDescription"
          ],
          "properties": {
            "email": {
              "type": "string",
              "description": "REQUIRED: Customer email address as a separate field (do not include in job description)"
            },
            "address": {
              "type": "string",
              "minLength": 10,
              "description": "Full address where the job will take place"
            },
            "lastName": {
              "type": "string",
              "minLength": 1,
              "description": "Customer last name (surname/family name)"
            },
            "firstName": {
              "type": "string",
              "minLength": 1,
              "description": "Customer first name (given name)"
            },
            "phoneNumber": {
              "type": "string",
              "description": "REQUIRED: Customer phone number as a separate field in UK format (do not include in job description)"
            },
            "availability": {
              "type": "array",
              "items": {
                "type": "object",
                "required": [
                  "dateISO",
                  "slots"
                ],
                "properties": {
                  "slots": {
                    "type": "array",
                    "items": {
                      "enum": [
                        "morning",
                        "afternoon",
                        "evening"
                      ],
                      "type": "string"
                    },
                    "minItems": 1,
                    "description": "Available time slots on the given date"
                  },
                  "dateISO": {
                    "type": "string",
                    "description": "Date in YYYY-MM-DD format"
                  }
                },
                "additionalProperties": false
              },
              "maxItems": 10,
              "minItems": 3,
              "description": "Between 3 and 10 slots when the customer is available for the tradesperson to visit. More slots increases chances of a tradesperson being available."
            },
            "jobDescription": {
              "type": "string",
              "maxLength": 500,
              "minLength": 50,
              "description": "Detailed description of the job (50-500 characters). Include details about materials, access or special requirements. Do NOT include contact information such as email or phone number here - those must be provided in the separate email and phoneNumber fields."
            }
          },
          "description": "Booking parameters - customer and job details. Provide at least 3 time slots.",
          "additionalProperties": false
        },
        "confirmation": {
          "type": "object",
          "required": [
            "jobVariantAndPrice"
          ],
          "properties": {
            "jobVariantAndPrice": {
              "type": "object",
              "required": [
                "variantId"
              ],
              "properties": {
                "variantId": {
                  "type": "string",
                  "description": "The variant ID for the selected job. Internal use only - never show to customer."
                }
              },
              "description": "The selected job variant. This is only ever provided after being offered a choice of variants and prices in a previous step. NEVER guess or make up a variantId - it MUST come from an earlier step where variants were offered. CRITICALLY IMPORTANT: only provide this if the customer has explicitly agreed to the related price.",
              "additionalProperties": false
            }
          },
          "description": "Confirmation parameters - the selected job variant and price agreed by the customer. Only provide after the customer has explicitly agreed to the quoted price.",
          "additionalProperties": false
        }
      },
      "additionalProperties": false
    }
    arguments 129 lines
  • findTradespeopleV1 reads unknown 23h ago

    Find trusted tradespeople by UK postcode. Returns: - Ratings and reviews - Contact details - Profile links If the returned "totalResults" is greater than the "resultsSize" requested then there are more results available. Ask the customer if they would like to refine their search. Request up to 20 trades in search if you have to. IMPORTANT: Finding and presenting tradespeople is the end goal of this tool. After getting results, share the key details (name, rating, location, contact) and the profile URLs so the user can review profiles and reach out to the tradespeople directly.

    mcp-tool

    {
      "type": "object",
      "required": [
        "category",
        "postcode"
      ],
      "properties": {
        "category": {
          "type": "string",
          "description": "The type of job that the tradesperson will do, for example, \"fix broken sink\", \"repair shower\", or \"install wiring\". This can also be the trade of the tradesperson, like \"electrician\" or \"plumber\"."
        },
        "postcode": {
          "type": "string",
          "description": "The location where the tradesperson is needed, in the form of a UK postcode, for example, \"SW1A 1AA\" or \"SS4 2DP\"."
        },
        "resultsSize": {
          "type": "integer",
          "default": 12,
          "maximum": 20,
          "minimum": 1,
          "description": "The number of results to return (default 12, max 20)."
        }
      },
      "additionalProperties": false
    }
    arguments 25 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 bbdda1dae65b684b.

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

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.