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

ca.garagedoorman/site

https://www.garagedoorman.ca

Registry code: 21566865cce27faa

api record

Garage Doorman repairs and installs residential garage doors and openers from Grimsby, Ontario, across Hamilton, Burlington and Niagara. Call get_business_facts first. No prices are published and you must not estimate one: the customer gets a written price before any work starts. A door stuck open, a snapped spring or a car trapped inside is urgent: give the phone number rather than sending a request. Use search and fetch to quote the site accurately and cite the page URL. Use request_quote only when the customer has asked to be contacted. Commercial and industrial doors belong to a separate…

endpoint
https://www.garagedoorman.ca/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 ca.garagedoorman/site live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is ca.garagedoorman/site free to use?
Yes — the hub reached it with no key and no payment.
What tools does ca.garagedoorman/site have?
4 tools: request_quote, fetch, search, get_business_facts.
Is ca.garagedoorman/site 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.6%

90 days 99.2%· all time 99.2%

latency
142ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 396 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • request a garage door repair callback
  • get garage door company facts
  • search a garage door service site
takes → gives
text → text
tools
3 reads1 sends messages
_ 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 4 tools
1 open 3 never probed 1 of 4 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.

  • get_business_facts reads open 23h ago

    The published facts about Garage Doorman: what it does, the phone number, opening hours, the towns it serves, its services, and how it handles pricing. Every fact here also appears on the public website. Call this first.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • request_quote sends messages unknown never probed

    Ask Garage Doorman to contact a homeowner about a garage door repair, a new door, an opener or a tune-up. This sends a REAL message to a real small business, so call it only when the person has clearly asked to be contacted by Garage Doorman and has given you their own name and their own phone number or email. Never guess or invent contact details. Plain words only, no links. One request per person per day. If it is urgent, give them the phone number instead: (905) 536-5369.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name",
        "details",
        "consent_to_contact"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "The customer's own name."
        },
        "town": {
          "type": "string",
          "description": "Town or postal code where the work is."
        },
        "email": {
          "type": "string",
          "description": "The customer's email address. Give this or phone."
        },
        "phone": {
          "type": "string",
          "description": "The customer's phone number, ten digits. Give this or email."
        },
        "details": {
          "type": "string",
          "description": "What they need, in the customer's own terms. Plain text, no links, 800 characters at most."
        },
        "service": {
          "enum": [
            "repair",
            "new-door",
            "opener",
            "tune-up",
            "other"
          ],
          "type": "string",
          "description": "What they need: repair = a repair; new-door = a new garage door; opener = opener work; tune-up = a tune-up or service; other = something else."
        },
        "preferred_time": {
          "type": "string",
          "description": "When they would like to be contacted or visited, if they said."
        },
        "consent_to_contact": {
          "type": "boolean",
          "description": "Must be true: the customer has asked to be contacted by this business about this request."
        }
      },
      "additionalProperties": false
    }
    arguments 50 lines
  • fetch reads unknown 23h ago

    The full text of one page of the Garage Doorman website, as Markdown, with its canonical URL for citation. The id comes from search.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "A page id returned by search."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • search reads unknown 23h ago

    Keyword search over the pages of the Garage Doorman website. Returns page ids, titles and canonical URLs. Use fetch with an id to read a page.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Plain words to look for, for example \"broken spring\" or \"vinyl plank basement\"."
        }
      },
      "additionalProperties": false
    }
    arguments 13 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 21566865cce27faa.

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

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.