ca.commercialgaragedoorman/site
https://www.commercialgaragedoorman.ca
Registry code: 56757ce6e7cc1fd4
Commercial Garage Doorman services and installs commercial and industrial doors from Grimsby, Ontario, across Hamilton, Niagara, Burlington and the surrounding region: rolling steel, sectional overhead, high-speed doors and rolling shutters, dock levellers and loading dock equipment, high-cycle spring conversions, and planned maintenance programs. There is also 24/7 emergency service. Call get_business_facts first. PUBLISHED PRICES (Canadian dollars, ballpark, confirmed in writing before work starts): emergency service $349 plus HST for the first 90 minutes on site, travel included, then…
- endpoint
- https://www.commercialgaragedoorman.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 ca.commercialgaragedoorman/site live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
- Is ca.commercialgaragedoorman/site free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does ca.commercialgaragedoorman/site have?
- 4 tools: fetch, request_quote, search, get_business_facts.
- Is ca.commercialgaragedoorman/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.
90 days 99%· all time 99%
last good check
of 4 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- get facts about a commercial door installer
- search the company website pages
- find emergency door service contact
- takes → gives
- text → text
- tools
- 3 reads
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.
through this hub
successful
what callers paid
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 15h ago
The published facts about Commercial 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.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesfetch reads unknown 15h ago
The full text of one page of the Commercial Garage Doorman website, as Markdown, with its canonical URL for citation. The id comes from search.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "A page id returned by search." } }, "additionalProperties": false }arguments 13 linesrequest_quote unknown never probed
Ask Commercial Garage Doorman to contact a facility manager, property manager, contractor or business owner about commercial or industrial doors: a repair, doors for a new building, a replacement, a maintenance program or dock equipment. Not for houses, and not for a door that is stuck open right now: that is a phone call. This sends a REAL message to a real small business, so call it only when the person has clearly asked to be contacted by Commercial 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.
{ "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-construction", "replacement", "maintenance", "dock", "other" ], "type": "string", "description": "What they need: repair = a repair or service call; new-construction = doors for a new building; replacement = replacing an existing door; maintenance = a planned maintenance program; dock = dock levellers, seals or bumpers; 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 51 linessearch reads unknown 15h ago
Keyword search over the pages of the Commercial Garage Doorman website. Returns page ids, titles and canonical URLs. Use fetch with an id to read a page.
{ "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
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id56757ce6e7cc1fd4.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/56757ce6e7cc1fd4/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/56757ce6e7cc1fd4?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.