Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AutoIsto CZ — car watch

REMOTE · WWW.AUTOISTO.CZ

Watches Czech used-car ads for a buyer. Takes no contact; active only after e-mail opt-in.

Available components

+4 this week 73 Trust /100

Last scanned (9 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1167 tokens (~233/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 Management50
  • Stability observed for 15 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 (80% 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 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 6 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
Changelog

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.

  • 5 Nov 26 +1

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

  • 3 Nov 26 +1

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

  • 1 Nov 26 +1

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

  • 30 Oct 26 +1

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

  • 28 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 909 → 1167 ▼ functional
    • Tool coverage: 100% → 80% ▼ functional
    • New tool “intent_search_offers” functional
  • 27 Oct 26 +1

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

  • 25 Oct 26 +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.

  • 24 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “intent_list_matches” rewrote its description, which is the text the model reads security
    • Tool “intent_publish_intent” rewrote its description, which is the text the model reads security
Diagnostics

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 5 Nov 2026 · Probed https://www.autoisto.cz/mcp/zamery

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=autoisto.cz CN=YE1,O=Let's Encrypt,C=US 30 Sept 2026 29 Dec 2026 ECDSA 256 ECDSA-SHA384 55fc80d8ed7c564d245f799b04a5b2bb86b
SANs: *.autoisto.cz, autoisto.cz
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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 insecure

Validation of www.autoisto.cz. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
cz. present 20237 13 Verified
autoisto.cz. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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=15552000
content-security-policy default-src 'self'; script-src 'self' 'nonce-ZDAyZDg3YjEtNjVjYy00NTU2LTlhMTMtMTU1NjIzNzgwZGFm' 'strict-dynamic'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://*.bazos.cz https://*.tipcars.com https://*.skodaplus.cz https://*.sdn.cz https://*.porscheinformatik.com https://*.vshcdn.net https://*.autoesa.cz https://*.hyundai-promise.cz https://*.pewneauto.pl https://*.louda.cz https://*.kia.cz https://*.renault.cz https://*.emilfreyselect.cz https://*.davocar.cz https://*.bmw.cz; font-src 'self'; connect-src 'self'; manifest-src 'self'; worker-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests;
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(self), geolocation=(), payment=(), usb=(), magnetometer=(), gyroscope=(), accelerometer=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.autoisto.cz/mcp/zamery Verified 200
http (plaintext) http://www.autoisto.cz/mcp/zamery HTTPS enforced 301 https://www.autoisto.cz/mcp/zamery
MCP tools · 5 exposed · ~931 tokens

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 →

Tool Tokens
intent_get_intent ~82

Use this to check whether an intent created with intent_publish_intent is already confirmed by the user and active, waiting, expired or withdrawn. Requires the intentCode; returns the statement and dates only — never the user's e-mail, the hidden limit or any other personal data.

NameTypeReqDescription
intentCodestringyesThe intentCode returned by intent_publish_intent.
NameTypeReqDescription
activeSincestring|null––
buyBystring|null––
foundbooleanyes–
hasHiddenLimitboolean––
niceToHavestring|null––
statementstring––
statusstring–awaiting_consent = the user has not confirmed on the AutoIsto page yet; awaiting_email_confirmation = the user filled in the page and must click the link in the e-mail; active = AutoIsto is watching;…
validUntilstring–Date (YYYY-MM-DD) until which the intent is watched (before confirmation: until the draft is deleted).

No examples provided.

intent_list_matches ~179

Use this when the user asks what AutoIsto has found for an intent created with intent_publish_intent. These are the same cars AutoIsto e-mails to the user; this server cannot send messages into the conversation by itself. Requires the intentCode; optional since (ISO time) returns only newer matches. Returns at most 20 newest matches with the price in CZK and AutoIsto price verdict at the time of the match and a link. Before the user confirms the intent there are no matches. Matches come from listings AutoIsto CZ aggregates from the market, so they cover only cars listed on AutoIsto CZ and may be incomplete; a car may already be sold.

NameTypeReqDescription
intentCodestringyesThe intentCode returned by intent_publish_intent.
sincestring–Only matches found after this ISO time.
NameTypeReqDescription
foundbooleanyes–
matchesarray––
moreboolean–More matches exist than returned; call again with since.
statusstring–awaiting_consent = the user has not confirmed on the AutoIsto page yet; awaiting_email_confirmation = the user filled in the page and must click the link in the e-mail; active = AutoIsto is watching;…

No examples provided.

intent_publish_intent ~377

Use this when the user asks AutoIsto to keep watching Czech car listings for them over time (e.g. "let me know until March about an estate car under 300 000 CZK, not diesel"). This does NOT start watching by itself and takes no e-mail address or other personal data: it returns a consentUrl on www.autoisto.cz that the user must open themselves, enter their own e-mail there and confirm by clicking the link AutoIsto e-mails them. Never ask the user for their e-mail in the conversation and never open the link for them. An unconfirmed draft is deleted after 24 hours. Matching cars are e-mailed to the user and can also be read with intent_list_matches using the returned intentCode — keep it in the conversation. hiddenLimitCzk is optional: the most the user would pay, stored encrypted and never shown to sellers or returned by any tool; pass it only if the user said it. Matches come from listings AutoIsto CZ aggregates from the Czech market (its own sellers' listings and public listings from Czech car portals), so they cover only cars listed on AutoIsto CZ (Czech Republic, CZK) and may be incomplete.

NameTypeReqDescription
buyBystring–Date (YYYY-MM-DD) by which the user wants to buy; watching stops after it.
hiddenLimitCzkinteger–Optional private maximum price in CZK; encrypted on receipt and never returned by any tool.
niceToHavestring–Wishes that are not required (never filters), e.g. "tažné, automat".
statementstringyesWhat the car MUST be, as one short Czech (or Slovak) phrase with prices in CZK, e.g. "kombi do 300000 Kč ne diesel".
NameTypeReqDescription
buyBystring|nullyes–
consentExpiresAtstringyesISO time after which the unconfirmed draft is deleted.
consentUrlstringyesPage on www.autoisto.cz where the USER confirms the intent with their own e-mail. Show it unchanged.
hasHiddenLimitbooleanyesWhether a hidden limit was stored. Its value is never returned.
intentCodestringyesSecret code of this intent; use it with intent_get_intent, intent_list_matches and intent_withdraw_intent.
niceToHavestring|nullyes–
notUnderstoodarrayyesWords of the statement that are NOT watched for. Tell the person.
statementstringyes–
statusstringyesawaiting_consent = the user has not confirmed on the AutoIsto page yet; awaiting_email_confirmation = the user filled in the page and must click the link in the e-mail; active = AutoIsto is watching;…
understoodarrayyesWhat AutoIsto will watch for, read from the statement (in Czech). Tell the person before they confirm.

No examples provided.

intent_search_offers ~225

Use this when the user wants to find a used car for sale in the Czech Republic now. Pass what they are looking for as one short phrase (Czech or Slovak works best), e.g. "toyota rav4 hybrid do 600000 Kč". Returns up to 20 cars from AutoIsto CZ's offer in its own order, each with a link to the car on www.autoisto.cz, plus what was understood, which words were not applied and what had to be relaxed. When suggestIntent is true (nothing or little found, or part of the phrase was dropped), offer the user intent_publish_intent with the same statement so AutoIsto CZ keeps watching. Results come from listings AutoIsto CZ aggregates from the Czech market and may be incomplete; no seller contact is returned.

NameTypeReqDescription
limitinteger–At most this many cars (default 10; AutoIsto CZ returns at most 10).
statementstringyesWhat the user is looking for, e.g. "suv automat do 500000 Kč".

No output schema declared.

No examples provided.

intent_withdraw_intent ~68

Use this when the user wants AutoIsto to stop watching for an intent created with intent_publish_intent. Takes effect immediately; nothing more is e-mailed for it. Requires the intentCode.

NameTypeReqDescription
intentCodestringyesThe intentCode returned by intent_publish_intent.
NameTypeReqDescription
foundbooleanyes–
statusstring––

No examples provided.

Install

How do I install the AutoIsto CZ — car watch MCP server?

AutoIsto CZ — car watch is a hosted endpoint at https://www.autoisto.cz/mcp/zamery, 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 · www.autoisto.cz

# add to Claude Code
claude mcp add --transport http cz-autoisto-intents 'https://www.autoisto.cz/mcp/zamery'
Common questions

What is the AutoIsto CZ — car watch MCP server?

AutoIsto CZ — car watch is an MCP server listed in the public MCP registry as cz.autoisto/intents. Watches Czech used-car ads for a buyer. Takes no contact; active only after e-mail opt-in. This page covers its hosted endpoint (https://www.autoisto.cz/mcp/zamery).

Is the AutoIsto CZ — car watch MCP server safe to use?

AutoIsto CZ — car watch scores 73 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 AutoIsto CZ — car watch MCP server expose?

AutoIsto CZ — car watch exposes 5 tools: intent_publish_intent, intent_get_intent, intent_list_matches, intent_withdraw_intent, intent_search_offers. Their descriptions and schemas cost roughly 931 tokens of context every time the server is loaded.

Does the AutoIsto CZ — car watch MCP server require authentication?

No. We connected to AutoIsto CZ — car watch without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AutoIsto CZ — car watch MCP server still maintained?

AutoIsto CZ — car watch is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.