MapleV Tesla Collision Parts
REMOTE · QFKSOPXMPHTDMAJLBCIK.SUPABASE.CO · SCANNED SEP 20
Search Tesla Model 3 and Model Y collision parts by OE number. CAD prices, BC delivery, read-only.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability83
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 534 tokens (~133/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 Management40
- Stability observed for 12 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
- 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
How do I install the MapleV Tesla Collision Parts MCP server?
MapleV Tesla Collision Parts is a hosted endpoint at https://qfksopxmphtdmajlbcik.supabase.co/functions/v1/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 · qfksopxmphtdmajlbcik.supabase.co
claude mcp add --transport http ca-maplev-tesla-collision-parts 'https://qfksopxmphtdmajlbcik.supabase.co/functions/v1/mcp'
{
"mcpServers": {
"ca-maplev-tesla-collision-parts": {
"url": "https://qfksopxmphtdmajlbcik.supabase.co/functions/v1/mcp"
}
}
} {
"servers": {
"ca-maplev-tesla-collision-parts": {
"type": "http",
"url": "https://qfksopxmphtdmajlbcik.supabase.co/functions/v1/mcp"
}
}
} [mcp_servers.ca-maplev-tesla-collision-parts] url = "https://qfksopxmphtdmajlbcik.supabase.co/functions/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ca-maplev-tesla-collision-parts": {
"type": "remote",
"url": "https://qfksopxmphtdmajlbcik.supabase.co/functions/v1/mcp",
"enabled": true
}
}
} openclaw mcp add ca-maplev-tesla-collision-parts --url 'https://qfksopxmphtdmajlbcik.supabase.co/functions/v1/mcp' --transport streamable-http
mcp_servers:
ca-maplev-tesla-collision-parts:
url: "https://qfksopxmphtdmajlbcik.supabase.co/functions/v1/mcp" {
"McpServers": {
"ca-maplev-tesla-collision-parts": {
"Transport": "http",
"Url": "https://qfksopxmphtdmajlbcik.supabase.co/functions/v1/mcp"
}
}
} assistant mcp add ca-maplev-tesla-collision-parts -t streamable-http -u 'https://qfksopxmphtdmajlbcik.supabase.co/functions/v1/mcp'
{
"mcpServers": {
"ca-maplev-tesla-collision-parts": {
"type": "http",
"url": "https://qfksopxmphtdmajlbcik.supabase.co/functions/v1/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 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.
- 11 Sept 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.
- 9 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 8 Sept 26 68
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 20 Sept 2026 · Probed https://qfksopxmphtdmajlbcik.supabase.co/functions/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=supabase.co | CN=WE1,O=Google Trust Services,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 7c35296a896c0a6f13f8495266045d45 |
| SANs: supabase.co, *.supabase.co | ||||||
| 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 qfksopxmphtdmajlbcik.supabase.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| supabase.co. | 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; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://qfksopxmphtdmajlbcik.supabase.co/functions/v1/mcp | Verified | 200 | |
| http (plaintext) | http://qfksopxmphtdmajlbcik.supabase.co/functions/v1/mcp | HTTPS enforced | 301 | https://qfksopxmphtdmajlbcik.supabase.co/functions/v1/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 ~155
Given a delivery city in British Columbia (and optionally the province), return MapleV's available delivery tiers with ETA, cut-off time and CAD fee. Answers questions like 'can MapleV get this part to my shop in Abbotsford today?'. Fees shown are customer-facing CAD; delivery is free on orders at or above the published threshold.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | Delivery city, e.g. 'Burnaby', 'Abbotsford', 'Victoria'. |
| 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. Defaults to BC; anything outside BC is quoted as freight. |
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 ~133
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 keyword or OE part number (partial matches supported). |
No output schema declared.
No examples provided.
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. Search Tesla Model 3 and Model Y collision parts by OE number. CAD prices, BC delivery, read-only. This page covers its hosted endpoint (https://qfksopxmphtdmajlbcik.supabase.co/functions/v1/mcp).
Is the MapleV Tesla Collision Parts MCP server safe to use?
MapleV Tesla Collision Parts 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 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 397 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.