AUTO411 Vehicle Intelligence
REMOTE · MCP.411SPECS.COM · SCANNED OCT 4
Identity-first automotive intelligence for vehicle resolution, specs, safety and efficiency.
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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- 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. 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
- Structured output schemas are declared (100% 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 5 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 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.
remote · mcp.411specs.com
claude mcp add --transport http simonizer69-auto411-vehicle-intelligence 'https://mcp.411specs.com/mcp'
{
"mcpServers": {
"simonizer69-auto411-vehicle-intelligence": {
"url": "https://mcp.411specs.com/mcp"
}
}
} {
"servers": {
"simonizer69-auto411-vehicle-intelligence": {
"type": "http",
"url": "https://mcp.411specs.com/mcp"
}
}
} [mcp_servers.simonizer69-auto411-vehicle-intelligence] url = "https://mcp.411specs.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"simonizer69-auto411-vehicle-intelligence": {
"type": "remote",
"url": "https://mcp.411specs.com/mcp",
"enabled": true
}
}
} openclaw mcp add simonizer69-auto411-vehicle-intelligence --url 'https://mcp.411specs.com/mcp' --transport streamable-http
mcp_servers:
simonizer69-auto411-vehicle-intelligence:
url: "https://mcp.411specs.com/mcp" {
"McpServers": {
"simonizer69-auto411-vehicle-intelligence": {
"Transport": "http",
"Url": "https://mcp.411specs.com/mcp"
}
}
} assistant mcp add simonizer69-auto411-vehicle-intelligence -t streamable-http -u 'https://mcp.411specs.com/mcp'
{
"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.
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.
- 4 Oct 26 +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.
- 2 Oct 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.
- 29 Sept 26 +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.
- 28 Sept 26 +8
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 64
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 8 Oct 2026 · Probed https://mcp.411specs.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=411specs.com | CN=WE1,O=Google Trust Services,C=US | 26 Sept 2026 | 25 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 9655899c0edfcbaf136122a51fd9e9fc |
| SANs: 411specs.com, mcp.411specs.com, *.mcp.411specs.com | ||||||
| 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 mcp.411specs.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| 411specs.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.411specs.com/.well-known/oauth-protected-resource", scope="auto411:read", error="invalid_token", error_description="Access token is missing, expired, or invalid"
Bearer resource_metadata="https://mcp.411specs.com/.well-known/oauth-protected-resource", scope="auto411:read", error="invalid_token", error_description="Access token is missing, expired, or invalid"| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Protected resource metadata
| Document | https://mcp.411specs.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.411specs.com/mcp |
| Authorisation server | https://auto411.us.auth0.com/ |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.411specs.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.411specs.com/mcp | Inconclusive | 401 |
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_vehicle_efficiency Get Vehicle Efficiency ~220
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| agent_instruction | string | yes | – |
| 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 | yes | – |
No examples provided.
get_vehicle_fitment Get Wheel and Tire Fitment ~228
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| agent_instruction | string | yes | – |
| 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 | yes | – |
No examples provided.
get_vehicle_safety Get Vehicle Safety Information ~224
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| agent_instruction | string | yes | – |
| 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 | yes | – |
| safety | object | – | – |
| source_errors | array | – | – |
No examples provided.
get_vehicle_specs Get Vehicle Specifications ~227
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| agent_instruction | string | yes | – |
| 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 | yes | – |
| specifications | object | – | – |
No examples provided.
resolve_vehicle Resolve Vehicle Identity ~220
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| agent_instruction | string | yes | – |
| 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 | yes | – |
No examples provided.
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.