YoAuto MCP
REMOTE · YOAUTO.MD
Official YoAuto MCP gateway for vehicle search and marketplace workflows in Moldova.
Available components
Last scanned (42 minutes ago)
Scores higher than 46% of remote servers
Reachable. Last reached 23 Oct 2026.
Category E-commerce
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 Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 571 tokens (~57/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 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
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 23 Oct 26 +29
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Schema quality: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 22 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 21 Oct 26 +4
- Endpoint reachability: not serving MCP → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 30 Sept 26 −4
- Endpoint reachability: reachable → not serving MCP ▼ security
- Capabilities: pass → unverified ▼ functional
- 29 Sept 26 +4
- Endpoint reachability: not serving MCP → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 28 Sept 26 0
- 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 −4
- Endpoint reachability: reachable → not serving MCP ▼ security
- Capabilities: pass → unverified ▼ functional
- 26 Sept 26 +4
- Endpoint reachability: not serving MCP → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
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 23 Oct 2026 · Probed https://yoauto.md/api/mcp/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=yoauto.md | CN=YE2,O=Let's Encrypt,C=US | 1 Oct 2026 | 30 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6f98430fad60b0f70ee616f069fabb62af9 |
| SANs: *.yoauto.md, yoauto.md | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of yoauto.md. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| md. | present | 127 | 14 | Verified |
| yoauto.md. | present | 2371 | 13 | Verified |
| yoauto.md. | Verified address RRset verified with the apex keys |
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 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://yoauto.md/api/mcp/sse | Verified | 200 | |
| http (plaintext) | http://yoauto.md/api/mcp/sse | Served over HTTP | 200 |
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 →
buy_agent_energy ~72
Позволяет агенту приобрести (или пополнить) баланс внутренней энергии (Energy) для выполнения платных операций. Авторизация берется из контекста сессии (Authorization header) либо параметра auth_token.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | integer | yes | – |
| auth_token | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
check_vin_history ~46
Информирует о проведении полной проверки VIN через веб-интерфейс и панель администратора YoAuto.
| Name | Type | Req | Description |
|---|---|---|---|
| auth_token | – | – | – |
| vin | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_agent_balance ~61
Возвращает баланс кредитов (Energy), статус подписки и роль авторизованного агента. Авторизация берется из контекста сессии (Authorization header) либо параметра auth_token.
| Name | Type | Req | Description |
|---|---|---|---|
| auth_token | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_dealer_info ~35
Возвращает информацию о дилере по его ID.
| Name | Type | Req | Description |
|---|---|---|---|
| auth_token | – | – | – |
| dealer_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_listing_details ~91
Возвращает подробные технические характеристики и метаданные конкретного автомобиля по его ID. Если передан валидный auth_token авторизованного агента, показываются полные контактные данные продавца и VIN. В ином случае персональные данные скрываются/маскируются для безопасности.
| Name | Type | Req | Description |
|---|---|---|---|
| auth_token | – | – | – |
| car_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_user_credits ~34
Возвращает баланс энергии пользователя/агента.
| Name | Type | Req | Description |
|---|---|---|---|
| auth_token | – | – | – |
| user_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_yoauto_info ~59
Возвращает информацию о проекте YoAuto (платформа автомобильной торговли в Молдове). Полезно для ознакомления ИИ-агентов с возможностями проекта и правилами конфиденциальности.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_cars ~54
Ищет авто в базе YoAuto. Возвращает Markdown с пагинацией.
| Name | Type | Req | Description |
|---|---|---|---|
| auth_token | – | – | – |
| brand | string | yes | – |
| model | string | – | – |
| page | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_vehicles ~56
Псевдоним для search_cars: Ищет авто в базе YoAuto.
| Name | Type | Req | Description |
|---|---|---|---|
| auth_token | – | – | – |
| brand | string | yes | – |
| model | string | – | – |
| page | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
send_internal_message ~63
Отправляет сообщение продавцу автомобиля. Авторизация берется из контекста сессии (Authorization header) либо параметра auth_token.
| Name | Type | Req | Description |
|---|---|---|---|
| auth_token | – | – | – |
| car_id | string | yes | – |
| message | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the YoAuto MCP server?
YoAuto MCP is a hosted endpoint at https://yoauto.md/api/mcp/sse, 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 · yoauto.md
claude mcp add --transport http atomix-spec-yoauto-mcp 'https://yoauto.md/api/mcp/sse'
What is the YoAuto MCP server?
YoAuto MCP is listed in the public MCP registry as io.github.atomix-spec/yoauto-mcp. Official YoAuto MCP gateway for vehicle search and marketplace workflows in Moldova. This page covers its hosted endpoint (https://yoauto.md/api/mcp/sse).
Is the YoAuto MCP server safe to use?
YoAuto MCP scores 59 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 YoAuto MCP server expose?
YoAuto MCP exposes 10 tools: search_cars, search_vehicles, get_dealer_info, get_user_credits, check_vin_history, and 5 more. Their descriptions and schemas cost roughly 571 tokens of context every time the server is loaded.
Does the YoAuto MCP server require authentication?
No. We connected to YoAuto MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the YoAuto MCP server still maintained?
YoAuto MCP is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.