# Hunt Auto Group Texas: used car data (remote · texas.huntautogroup.com)

Read-only used-car data for Texas: NHTSA recalls and crash stars, EPA MPG, size by model year.

- Trust score: 80/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `texas.huntautogroup.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-huntautogroup-texas-data/api-mcp.md), [page](https://verifymcp.io/servers/com-huntautogroup-texas-data/api-mcp)

## Channel facts

- Endpoint: `https://texas.huntautogroup.com/api/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.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-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 407 tokens (~81/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 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.
- **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 6 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 Hunt Auto Group Texas: used car data MCP server?

Hunt Auto Group Texas: used car data is a hosted endpoint at https://texas.huntautogroup.com/api/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 com-huntautogroup-texas-data 'https://texas.huntautogroup.com/api/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "com-huntautogroup-texas-data": {
      "url": "https://texas.huntautogroup.com/api/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-huntautogroup-texas-data": {
      "type": "http",
      "url": "https://texas.huntautogroup.com/api/mcp/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-huntautogroup-texas-data]
url = "https://texas.huntautogroup.com/api/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-huntautogroup-texas-data": {
      "type": "remote",
      "url": "https://texas.huntautogroup.com/api/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-huntautogroup-texas-data --url 'https://texas.huntautogroup.com/api/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-huntautogroup-texas-data:
    url: "https://texas.huntautogroup.com/api/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "com-huntautogroup-texas-data": {
      "Transport": "http",
      "Url": "https://texas.huntautogroup.com/api/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-huntautogroup-texas-data -t streamable-http -u 'https://texas.huntautogroup.com/api/mcp/'
```

### Other

```json
{
  "mcpServers": {
    "com-huntautogroup-texas-data": {
      "type": "http",
      "url": "https://texas.huntautogroup.com/api/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-11-21 (score 80, +1)

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

### 2026-11-19 (score 79, +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.

### 2026-11-17 (score 78, +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.

### 2026-11-15 (score 77, +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.

### 2026-11-13 (score 76, +1)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security improvement] Transport: fail → pass
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.20
- [functional improvement] MCP protocol: unverified → pass

### 2026-11-12 (score 75, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.13 → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-11 (score 75, +1)

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

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

## MCP tools (5)

### `list_models` (~70 tokens)

List car models

Car models this site has data for (Austin to San Antonio used-car buyers), with slug, category and years. Paginate with next_cursor.

Input parameters:

- `category` (string): Only this body category
- `cursor` (string): next_cursor from the previous page
- `limit` (integer): Page size

### `get_model` (~57 tokens)

Get a model summary

One model across all years: NHTSA recall campaigns, owner complaints, overall stars and EPA combined MPG per year, with page links.

Input parameters:

- `slug` (string, required): Model slug from list_models, e.g. chevrolet-tahoe

### `get_model_year` (~76 tokens)

Get one model year

One model year in detail: NHTSA recalls, complaints, top complaint components, crash stars; EPA engines, transmissions and MPG; Transport Canada size and weight.

Input parameters:

- `slug` (string, required): Model slug, e.g. toyota-tacoma
- `year` (string, required): Model year, e.g. 2019

### `list_guides` (~92 tokens)

List guides

Published guides, reviews and comparisons (Texas title, tax, inspection, auctions, best years), filtered by language, category or keywords.

Input parameters:

- `category` (string): Guide category
- `cursor` (string): next_cursor from the previous page
- `lang` (string): Language
- `limit` (integer): Page size
- `q` (string): Keywords that must all appear in the title or description

### `get_contact_options` (~45 tokens)

Get contact options

How a person can reach Anthony Hunt for free used-car advice (WhatsApp, email or form). He does not sell cars.

Input parameters:

- `channel` (string): Only this channel

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-huntautogroup-texas-data/api-mcp#diagnostics

## Score history

- 2026-11-21: 80
- 2026-11-20: 79
- 2026-11-19: 79
- 2026-11-18: 78
- 2026-11-17: 78
- 2026-11-16: 77
- 2026-11-15: 77
- 2026-11-14: 76
- 2026-11-13: 76
- 2026-11-12: 75
- 2026-11-11: 75
- 2026-11-10: 74
- 2026-11-09: 74
- 2026-11-08: 73
- 2026-11-07: 73

## Common questions

### What is the Hunt Auto Group Texas: used car data MCP server?

Hunt Auto Group Texas: used car data is an MCP server listed in the public MCP registry as com.huntautogroup.texas/data. Read-only used-car data for Texas: NHTSA recalls and crash stars, EPA MPG, size by model year. This page covers its hosted endpoint (https://texas.huntautogroup.com/api/mcp/).

### Is the Hunt Auto Group Texas: used car data MCP server safe to use?

Hunt Auto Group Texas: used car data scores 80 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 Hunt Auto Group Texas: used car data MCP server expose?

Hunt Auto Group Texas: used car data exposes 5 tools: list_models, get_model, get_model_year, list_guides, get_contact_options. Their descriptions and schemas cost roughly 340 tokens of context every time the server is loaded.

### Does the Hunt Auto Group Texas: used car data MCP server require authentication?

No. We connected to Hunt Auto Group Texas: used car data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Hunt Auto Group Texas: used car data MCP server still maintained?

Hunt Auto Group Texas: used car data is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Hunt Auto Group Texas: used car data MCP server?

VerifyMCP ran 13 checks on Hunt Auto Group Texas: used car data, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://texas.huntautogroup.com/api/mcp/
- Website: https://texas.huntautogroup.com/developers/
- Changelog RSS feed: https://verifymcp.io/servers/com-huntautogroup-texas-data/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-huntautogroup-texas-data/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-huntautogroup-texas-data/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-huntautogroup-texas-data/api-mcp
