# AUTO411 Vehicle Intelligence (remote · mcp.411specs.com)

Identity-first automotive intelligence for vehicle resolution, specs, safety and efficiency.

- Trust score: 75/100 (medium)
- Change this week: +11
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- remote · `mcp.411specs.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/simonizer69-auto411-vehicle-intelligence/mcp.md), [page](https://verifymcp.io/servers/simonizer69-auto411-vehicle-intelligence/mcp)

## Channel facts

- Endpoint: `https://mcp.411specs.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `3.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-04.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1119 tokens (~223/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the AUTO411 Vehicle Intelligence MCP server?

AUTO411 Vehicle Intelligence is a hosted endpoint at https://mcp.411specs.com/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.

### Claude

```bash
claude mcp add --transport http simonizer69-auto411-vehicle-intelligence 'https://mcp.411specs.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "simonizer69-auto411-vehicle-intelligence": {
      "url": "https://mcp.411specs.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "simonizer69-auto411-vehicle-intelligence": {
      "type": "http",
      "url": "https://mcp.411specs.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.simonizer69-auto411-vehicle-intelligence]
url = "https://mcp.411specs.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "simonizer69-auto411-vehicle-intelligence": {
      "type": "remote",
      "url": "https://mcp.411specs.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add simonizer69-auto411-vehicle-intelligence --url 'https://mcp.411specs.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  simonizer69-auto411-vehicle-intelligence:
    url: "https://mcp.411specs.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "simonizer69-auto411-vehicle-intelligence": {
      "Transport": "http",
      "Url": "https://mcp.411specs.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add simonizer69-auto411-vehicle-intelligence -t streamable-http -u 'https://mcp.411specs.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "simonizer69-auto411-vehicle-intelligence": {
      "type": "http",
      "url": "https://mcp.411specs.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-04 (score 75, +1)

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

### 2026-10-02 (score 74, +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.

### 2026-09-29 (score 73, +1)

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

### 2026-09-28 (score 72, +8)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 64)

First indexed and scored.

## MCP tools (5)

### `resolve_vehicle` (~220 tokens)

Resolve Vehicle Identity

Use this when identifying a vehicle from a full VIN or from year, make, and model with optional configuration refinements. Returns MATCHED_SINGLE, NEEDS_IDENTITY, or NO_MATCH and never silently chooses among legitimate configurations.

Input parameters:

- `configuration_id` (integer): AUTO411 configuration identifier returned by a prior NEEDS_IDENTITY response.
- `drivetrain` (string): Optional identity refinement. Use only an explicitly known drivetrain.
- `engine` (string): Optional identity refinement. Use only an explicitly known engine.
- `make` (string): Vehicle make. Required with year and model when VIN is not provided.
- `model` (string): Customer-facing model family. Required with year and make when VIN is not provided.
- `trim` (string): Optional identity refinement. Use only an explicitly known trim.
- `vin` (string): Full 17-character VIN. Use VIN by itself as the identity path, or omit it and provide year, make, and model.
- `year` (integer): Model year. Required with make and model when VIN is not provided.

Output parameters:

- `agent_instruction` (string)
- `canonical_vehicle`
- `choice_count` (integer)
- `choices` (array)
- `completeness` (string)
- `configuration_id` (number|null)
- `conflicts` (array)
- `error` (object)
- `evidence_status` (string)
- `fact_scope` (string)
- `missing_fields` (array)
- `resolution_status` (string)

### `get_vehicle_specs` (~227 tokens)

Get Vehicle Specifications

Use this when engine and powertrain specifications are needed for a vehicle identified by VIN or year, make, and model. Returns normalized supported facts such as engine, displacement, cylinders, horsepower, transmission, drivetrain, and fuel type only after identity resolves safely.

Input parameters:

- `configuration_id` (integer): AUTO411 configuration identifier returned by a prior NEEDS_IDENTITY response.
- `drivetrain` (string): Optional identity refinement. Use only an explicitly known drivetrain.
- `engine` (string): Optional identity refinement. Use only an explicitly known engine.
- `make` (string): Vehicle make. Required with year and model when VIN is not provided.
- `model` (string): Customer-facing model family. Required with year and make when VIN is not provided.
- `trim` (string): Optional identity refinement. Use only an explicitly known trim.
- `vin` (string): Full 17-character VIN. Use VIN by itself as the identity path, or omit it and provide year, make, and model.
- `year` (integer): Model year. Required with make and model when VIN is not provided.

Output parameters:

- `agent_instruction` (string)
- `canonical_vehicle`
- `choice_count` (integer)
- `choices` (array)
- `completeness` (string)
- `configuration_id` (number|null)
- `conflicts` (array)
- `error` (object)
- `evidence_status` (string)
- `fact_scope` (string)
- `missing_fields` (array)
- `policy_withheld` (array)
- `resolution_status` (string)
- `specifications` (object)

### `get_vehicle_fitment` (~228 tokens)

Get Wheel and Tire Fitment

Use this for wheel and tire fitment after identifying a vehicle by VIN or year, make, and model. Returns available OEM tire sizes, bolt pattern / PCD, center bore, wheel offset, and thread / lug size without guessing through ambiguous configurations.

Input parameters:

- `configuration_id` (integer): AUTO411 configuration identifier returned by a prior NEEDS_IDENTITY response.
- `drivetrain` (string): Optional identity refinement. Use only an explicitly known drivetrain.
- `engine` (string): Optional identity refinement. Use only an explicitly known engine.
- `make` (string): Vehicle make. Required with year and model when VIN is not provided.
- `model` (string): Customer-facing model family. Required with year and make when VIN is not provided.
- `trim` (string): Optional identity refinement. Use only an explicitly known trim.
- `vin` (string): Full 17-character VIN. Use VIN by itself as the identity path, or omit it and provide year, make, and model.
- `year` (integer): Model year. Required with make and model when VIN is not provided.

Output parameters:

- `agent_instruction` (string)
- `canonical_vehicle`
- `choice_count` (integer)
- `choices` (array)
- `completeness` (string)
- `configuration_id` (number|null)
- `conflicts` (array)
- `error` (object)
- `evidence_status` (string)
- `fact_scope` (string)
- `fitment` (object)
- `missing_fields` (array)
- `policy_withheld` (array)
- `resolution_status` (string)

### `get_vehicle_safety` (~224 tokens)

Get Vehicle Safety Information

Use this for available NHTSA-backed recalls, complaints, investigations, manufacturer communications, and safety ratings. Safety facts remain explicitly YMM-scoped and never establish configuration identity.

Input parameters:

- `configuration_id` (integer): AUTO411 configuration identifier returned by a prior NEEDS_IDENTITY response.
- `drivetrain` (string): Optional identity refinement. Use only an explicitly known drivetrain.
- `engine` (string): Optional identity refinement. Use only an explicitly known engine.
- `limit` (integer): Maximum records per safety category
- `make` (string): Vehicle make. Required with year and model when VIN is not provided.
- `model` (string): Customer-facing model family. Required with year and make when VIN is not provided.
- `trim` (string): Optional identity refinement. Use only an explicitly known trim.
- `vin` (string): Full 17-character VIN. Use VIN by itself as the identity path, or omit it and provide year, make, and model.
- `year` (integer): Model year. Required with make and model when VIN is not provided.

Output parameters:

- `agent_instruction` (string)
- `canonical_vehicle`
- `choice_count` (integer)
- `choices` (array)
- `completeness` (string)
- `configuration_id` (number|null)
- `conflicts` (array)
- `error` (object)
- `evidence_status` (string)
- `fact_scope` (string)
- `missing_fields` (array)
- `resolution_status` (string)
- `safety` (object)
- `source_errors` (array)

### `get_vehicle_efficiency` (~220 tokens)

Get Vehicle Efficiency

Use this for available EPA city, highway, and combined MPG, MPGe, range, fuel-cost, emissions, and related efficiency facts after vehicle identity resolves safely. Ambiguous EPA variants remain NEEDS_IDENTITY.

Input parameters:

- `configuration_id` (integer): AUTO411 configuration identifier returned by a prior NEEDS_IDENTITY response.
- `drivetrain` (string): Optional identity refinement. Use only an explicitly known drivetrain.
- `engine` (string): Optional identity refinement. Use only an explicitly known engine.
- `make` (string): Vehicle make. Required with year and model when VIN is not provided.
- `model` (string): Customer-facing model family. Required with year and make when VIN is not provided.
- `trim` (string): Optional identity refinement. Use only an explicitly known trim.
- `vin` (string): Full 17-character VIN. Use VIN by itself as the identity path, or omit it and provide year, make, and model.
- `year` (integer): Model year. Required with make and model when VIN is not provided.

Output parameters:

- `agent_instruction` (string)
- `candidates` (array)
- `canonical_vehicle`
- `choice_count` (integer)
- `choices` (array)
- `completeness` (string)
- `configuration_id` (number|null)
- `conflicts` (array)
- `efficiency`
- `error` (object)
- `evidence_status` (string)
- `fact_scope` (string)
- `missing_fields` (array)
- `resolution_status` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/simonizer69-auto411-vehicle-intelligence/mcp#diagnostics

## Score history

- 2026-10-04: 75
- 2026-10-03: 74
- 2026-10-02: 74
- 2026-10-01: 73
- 2026-09-30: 73
- 2026-09-29: 73
- 2026-09-28: 72
- 2026-09-27: 64

## Common questions

### What is the AUTO411 Vehicle Intelligence MCP server?

AUTO411 Vehicle Intelligence is an MCP server listed in the public MCP registry as io.github.simonizer69/auto411-vehicle-intelligence. Identity-first automotive intelligence for vehicle resolution, specs, safety and efficiency. This page covers its hosted endpoint (https://mcp.411specs.com/mcp).

### Is the AUTO411 Vehicle Intelligence MCP server safe to use?

AUTO411 Vehicle Intelligence scores 75 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 AUTO411 Vehicle Intelligence MCP server expose?

AUTO411 Vehicle Intelligence exposes 5 tools: resolve_vehicle, get_vehicle_specs, get_vehicle_fitment, get_vehicle_safety, get_vehicle_efficiency. Their descriptions and schemas cost roughly 1,119 tokens of context every time the server is loaded.

### Does the AUTO411 Vehicle Intelligence MCP server require authentication?

Yes. AUTO411 Vehicle Intelligence asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the AUTO411 Vehicle Intelligence MCP server still maintained?

AUTO411 Vehicle Intelligence is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.411specs.com/mcp
- Authorisation metadata: https://mcp.411specs.com/.well-known/oauth-protected-resource/mcp
- Changelog RSS feed: https://verifymcp.io/servers/simonizer69-auto411-vehicle-intelligence/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/simonizer69-auto411-vehicle-intelligence/mcp.json
- HTML version of this page: https://verifymcp.io/servers/simonizer69-auto411-vehicle-intelligence/mcp