texas-huntautogroup
https://texas.huntautogroup.com
Registry code: 9d192ca8068c6ad0
Read-only used-car data for Central Texas buyers: NHTSA recalls, complaints and crash stars, EPA MPG and Transport Canada size by model and year, plus guides. Never quote a price: the site publishes none. Anthony Hunt does not sell cars; to reach him give the user the link from get_contact_options.
- endpoint
- https://texas.huntautogroup.com/api/mcp/
- door code
- 427d1cb836f360e6
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is texas-huntautogroup live?
- Yes — it answered the hub's last check (checked 30m ago). It answered 100% of checks over the last 30 days.
- Is texas-huntautogroup free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does texas-huntautogroup have?
- 5 tools: get_model_year, list_guides, get_model, get_contact_options, list_models.
- Is texas-huntautogroup safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 5 tools
- unknown → live
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_contact_options open 30m ago
How a person can reach Anthony Hunt for free used-car advice (WhatsApp, email or form). He does not sell cars.
{ "type": "object", "properties": { "channel": { "enum": [ "email", "whatsapp", "form" ], "type": "string", "description": "Only this channel" } }, "additionalProperties": false }arguments 15 lineslist_models open 30m ago
Car models this site has data for (Austin to San Antonio used-car buyers), with slug, category and years. Paginate with next_cursor.
{ "type": "object", "properties": { "limit": { "type": "integer", "default": 20, "maximum": 100, "minimum": 1, "description": "Page size" }, "cursor": { "type": "string", "description": "next_cursor from the previous page" }, "category": { "enum": [ "truck", "suv", "car", "minivan" ], "type": "string", "description": "Only this body category" } }, "additionalProperties": false }arguments 27 linesget_model_year unknown never probed
One model year in detail: NHTSA recalls, complaints, top complaint components, crash stars; EPA engines, transmissions and MPG; Transport Canada size and weight.
{ "type": "object", "required": [ "slug", "year" ], "properties": { "slug": { "type": "string", "description": "Model slug, e.g. toyota-tacoma" }, "year": { "type": "string", "pattern": "^(19|20)[0-9]{2}$", "description": "Model year, e.g. 2019" } }, "additionalProperties": false }arguments 19 lineslist_guides unknown never probed
Published guides, reviews and comparisons (Texas title, tax, inspection, auctions, best years), filtered by language, category or keywords.
{ "type": "object", "properties": { "q": { "type": "string", "description": "Keywords that must all appear in the title or description" }, "lang": { "enum": [ "en", "es" ], "type": "string", "description": "Language" }, "limit": { "type": "integer", "default": 20, "maximum": 100, "minimum": 1, "description": "Page size" }, "cursor": { "type": "string", "description": "next_cursor from the previous page" }, "category": { "enum": [ "choosing", "buying", "paperwork", "auctions", "rideshare", "ownership" ], "type": "string", "description": "Guide category" } }, "additionalProperties": false }arguments 41 linesget_model unknown 30m ago
One model across all years: NHTSA recall campaigns, owner complaints, overall stars and EPA combined MPG per year, with page links.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "Model slug from list_models, e.g. chevrolet-tahoe" } }, "additionalProperties": false }arguments 13 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id9d192ca8068c6ad0.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/9d192ca8068c6ad0/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/9d192ca8068c6ad0?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.