Garage Doorman
REMOTE · WWW.GARAGEDOORMAN.CA
Garage Doorman, Grimsby ON residential garage door repair: business facts, site search, quotes.
Available components
Last scanned (22 hours ago)
Scores higher than 88% of remote servers
Reachable. Last reached 21 Nov 2026.
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 603 tokens (~150/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 21 Oct 26 0
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 21 Sept 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://www.garagedoorman.ca/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.garagedoorman.ca | CN=WE1,O=Google Trust Services,C=US | 30 Oct 2026 | 28 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 52ec1fd13366d40133d7a012040aa1e |
| SANs: www.garagedoorman.ca | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.garagedoorman.ca. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ca. | DS published | 26384 | 13 | Verified |
| garagedoorman.ca. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.garagedoorman.ca/mcp | Verified | 200 | |
| http (plaintext) | http://www.garagedoorman.ca/mcp | HTTPS enforced | 301 | https://www.garagedoorman.ca/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fetch Read a page from Garage Doorman ~49
The full text of one page of the Garage Doorman website, as Markdown, with its canonical URL for citation. The id comes from search.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | A page id returned by search. |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| metadata | object | – | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
get_business_facts Garage Doorman: business facts ~57
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_quote Ask Garage Doorman for a quote or a callback ~296
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.
| Name | Type | Req | Description |
|---|---|---|---|
| consent_to_contact | boolean | yes | Must be true: the customer has asked to be contacted by this business about this request. |
| details | string | yes | What they need, in the customer's own terms. Plain text, no links, 800 characters at most. |
| string | – | The customer's email address. Give this or phone. | |
| name | string | yes | The customer's own name. |
| phone | string | – | The customer's phone number, ten digits. Give this or email. |
| preferred_time | string | – | When they would like to be contacted or visited, if they said. |
| service | string | – | 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. |
| town | string | – | Town or postal code where the work is. |
No output schema declared.
No examples provided.
search Search Garage Doorman ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Plain words to look for, for example "broken spring" or "vinyl plank basement". |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
How do I install the Garage Doorman MCP server?
Garage Doorman is a hosted endpoint at https://www.garagedoorman.ca/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.garagedoorman.ca
claude mcp add --transport http ca-garagedoorman-business-card 'https://www.garagedoorman.ca/mcp'
What is the Garage Doorman MCP server?
Garage Doorman is an MCP server listed in the public MCP registry as ca.garagedoorman/business-card. Garage Doorman, Grimsby ON residential garage door repair: business facts, site search, quotes. This page covers its hosted endpoint (https://www.garagedoorman.ca/mcp).
Is the Garage Doorman MCP server safe to use?
Garage Doorman scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Garage Doorman MCP server expose?
Garage Doorman exposes 4 tools: get_business_facts, search, fetch, request_quote. Their descriptions and schemas cost roughly 465 tokens of context every time the server is loaded.
Does the Garage Doorman MCP server require authentication?
No. We connected to Garage Doorman without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Garage Doorman MCP server still maintained?
Garage Doorman is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Garage Doorman MCP server?
VerifyMCP ran 13 checks on Garage Doorman, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.