Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Kay1 Electric (Vancouver electrician)

REMOTE · KAY1ELECTRIC.CA

Licensed electrician in Coquitlam & Greater Vancouver, BC: services, areas, free estimate requests.

Available components

+3 this week 74 Trust /100

Last scanned (9 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 5 Nov 2026.

Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 736 tokens (~147/item across 5 items; 5 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 Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

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.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 30 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 29 Oct 26 71

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Probed https://kay1electric.ca/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=kay1electric.ca CN=YE1,O=Let's Encrypt,C=US 9 Oct 2026 7 Jan 2027 ECDSA 256 ECDSA-SHA384 522740bc06e4cf0a654c4a9f6aaea8da94f
SANs: kay1electric.ca, www.kay1electric.ca
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of kay1electric.ca. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ca. present 26384 13 Verified
kay1electric.ca. absent 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
Header Value
strict-transport-security max-age=31536000
content-security-policy upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://kay1electric.ca/mcp/ Verified 200
http (plaintext) http://kay1electric.ca/mcp/ HTTPS enforced 301 https://kay1electric.ca/mcp/
MCP tools · 5 exposed · ~600 tokens

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 →

Tool Tokens
get_business_info ~38

Contact details, office hours, after-hours emergency policy, licensing, service area summary and how to request a free estimate from Kay1 Electric Ltd.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_page ~86

Returns the Markdown version of a kay1electric.ca page, e.g. "/our-services/ev-charger-installation/" or "/fa/contact-us/". Use list_services, list_service_areas or https://kay1electric.ca/llms.txt to find paths.

NameTypeReqDescription
pathstringyesSite path or full URL of the page, e.g. "/about-us/".

No output schema declared.

No examples provided.

list_service_areas ~55

Cities in Greater Vancouver that Kay1 Electric serves, with example neighbourhoods and each city page URL.

NameTypeReqDescription
languagestring–Language of the returned page links: en (English, default) or fa (Persian).

No output schema declared.

No examples provided.

list_services ~75

The electrical services Kay1 Electric offers (panel upgrades, EV chargers, commercial work, repairs, rewiring, lighting, heat pump / hot tub wiring, smart home, inspections), each with its page URL.

NameTypeReqDescription
languagestring–Language of the returned page links: en (English, default) or fa (Persian).

No output schema declared.

No examples provided.

request_quote ~346

Send a free-estimate request to Kay1 Electric on the customer's behalf. Kay1 receives it by email and calls the customer back during office hours (7:00 AM - 9:30 PM daily, Pacific Time); if an email is given, the customer also gets a confirmation email. Only call this after showing the customer the details and getting their explicit OK to send them and be contacted. Do not invent details. Not for emergencies: for sparking, burning smells or no power, tell the customer to call (778) 900-1004 now (911 for fire or danger to life).

NameTypeReqDescription
agent_namestring–Name of the AI assistant or app sending this request, e.g. "ChatGPT" or "Claude".
citystringyesCity where the work is.
customer_confirmedbooleanyesMust be true: the customer reviewed these details, asked you to send them to Kay1 Electric, and agreed to be contacted by phone or email.
detailsstring–Short description of the job: property type (house, condo, business), current panel size if known, what needs doing or what is wrong. No links.
emailstring–Customer email (optional). If given, a confirmation email is sent to it.
namestringyesCustomer full name.
phonestringyesCustomer phone number with area code (North American), e.g. "604-555-0123".
preferred_languagestring–Language the customer prefers for the call back.
servicestringyesType of electrical work.
urgencystring–How soon the work is needed.

No output schema declared.

No examples provided.

Install

How do I install the Kay1 Electric (Vancouver electrician) MCP server?

Kay1 Electric (Vancouver electrician) is a hosted endpoint at https://kay1electric.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 · kay1electric.ca

# add to Claude Code
claude mcp add --transport http ca-kay1electric-kay1-electric 'https://kay1electric.ca/mcp/'
Common questions

What is the Kay1 Electric (Vancouver electrician) MCP server?

Kay1 Electric (Vancouver electrician) is an MCP server listed in the public MCP registry as ca.kay1electric/kay1-electric. Licensed electrician in Coquitlam & Greater Vancouver, BC: services, areas, free estimate requests. This page covers its hosted endpoint (https://kay1electric.ca/mcp/).

Is the Kay1 Electric (Vancouver electrician) MCP server safe to use?

Kay1 Electric (Vancouver electrician) scores 74 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 Kay1 Electric (Vancouver electrician) MCP server expose?

Kay1 Electric (Vancouver electrician) exposes 5 tools: get_business_info, list_services, list_service_areas, get_page, request_quote. Their descriptions and schemas cost roughly 600 tokens of context every time the server is loaded.

Does the Kay1 Electric (Vancouver electrician) MCP server require authentication?

No. We connected to Kay1 Electric (Vancouver electrician) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Kay1 Electric (Vancouver electrician) MCP server still maintained?

Kay1 Electric (Vancouver electrician) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.