MapleV Tesla Collision Parts
REMOTE · MAPLEV.CA
Tesla Model 3 and Model Y collision parts by OE number. CAD prices, ships Canada-wide, read-only.
Available components
Last scanned (19 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 4 Nov 2026.
Category E-commerce
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
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 817 tokens (~204/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
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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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
- Stability: 0.97 → pass security
- 2 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Probed https://maplev.ca/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=maplev.ca | CN=WE1,O=Google Trust Services,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | a0d4915f4001dce10e6f152a155f9541 |
| SANs: maplev.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 maplev.ca. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ca. | present | 26384 | 13 | Verified |
| maplev.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=2592000 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://maplev.ca/mcp | Verified | 200 | |
| http (plaintext) | http://maplev.ca/mcp | HTTPS enforced | 301 | https://maplev.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 →
get_delivery_options Get delivery options for a city ~261
Given a delivery city anywhere in Canada (province recommended), return MapleV's delivery options with ETA, cut-off time and CAD fee. Inside the local delivery area (Metro Vancouver and the Fraser Valley, BC): same-day and next-day delivery, plus 2-hour rush in the metro core. Everywhere else in Canada: ground courier with the typical transit time for the destination province, freight quoted at checkout. Answers questions like 'can MapleV get this part to my shop in Abbotsford today?' or 'how long does shipping to Calgary take?'. Fees are customer-facing CAD; local delivery is free on orders at or above the published threshold.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | Delivery city, e.g. 'Burnaby', 'Abbotsford', 'Calgary', 'Toronto'. |
| orderSubtotalCAD | number | – | Order subtotal in CAD, used only to show whether the free-delivery threshold is met. Defaults to 0. |
| province | string | – | Province or territory, as a code or name ('BC', 'Alberta', 'Québec'). Give it for any city outside Metro Vancouver: the transit estimate is per province, and without it a city outside the local BC de… |
No output schema declared.
No examples provided.
get_part Get part details ~81
Look up a single MapleV part by its catalog id (e.g. 'P-001') or by any Tesla OE part number / variant. Returns full details including grade, fitment, and CAD list price.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Catalog id like 'P-001', or an OE part number such as '1519965-SC-B'. |
No output schema declared.
No examples provided.
list_categories List catalog categories ~28
List all part categories in the MapleV Tesla collision catalog with the number of SKUs in each.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_parts Search parts ~230
Search MapleV's Tesla Model 3 / Model Y collision parts catalog by keyword, OE part number, vehicle model, or category. Returns matching parts with names, OE numbers, grade, category, and CAD list price.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category name, e.g. 'Front Bumpers', 'Lighting'. |
| grade | string | – | Filter by part grade. |
| limit | integer | – | Max results (default 20). |
| model | string | – | Filter to parts that fit this Tesla model. |
| query | string | – | Free-text search, any word order: part words, model name and/or OE part number, e.g. 'Model Y front bumper', 'Juniper tail lamp bracket', '1084168'. English, French (Québec shop terms) and Chinese ar… |
No output schema declared.
No examples provided.
How do I install the MapleV Tesla Collision Parts MCP server?
MapleV Tesla Collision Parts is a hosted endpoint at https://maplev.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 · maplev.ca
claude mcp add --transport http ca-maplev-tesla-collision-parts 'https://maplev.ca/mcp'
What is the MapleV Tesla Collision Parts MCP server?
MapleV Tesla Collision Parts is an MCP server listed in the public MCP registry as ca.maplev/tesla-collision-parts. Tesla Model 3 and Model Y collision parts by OE number. CAD prices, ships Canada-wide, read-only. This page covers its hosted endpoint (https://maplev.ca/mcp).
Is the MapleV Tesla Collision Parts MCP server safe to use?
MapleV Tesla Collision Parts scores 87 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 MapleV Tesla Collision Parts MCP server expose?
MapleV Tesla Collision Parts exposes 4 tools: search_parts, get_part, list_categories, get_delivery_options. Their descriptions and schemas cost roughly 600 tokens of context every time the server is loaded.
Does the MapleV Tesla Collision Parts MCP server require authentication?
No. We connected to MapleV Tesla Collision Parts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MapleV Tesla Collision Parts MCP server still maintained?
MapleV Tesla Collision Parts is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.