Isto Intents
REMOTE · ISTOINTENTS.COM
Ask a local listing portal to keep looking for a used car or home; the user confirms there.
Available components
Last scanned (9 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 25 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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (intent_withdraw_intent). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 862 tokens (~215/item across 4 items; 4 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 Management3
- Stability observed for 1 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
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.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
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.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 63
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 25 Oct 2026 · Probed https://istointents.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=istointents.com | CN=WE1,O=Google Trust Services,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 294091c3a031c4150e8c03f9e648ca45 |
| SANs: istointents.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 istointents.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| istointents.com. | 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 |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://istointents.com/mcp | Verified | 200 | |
| http (plaintext) | http://istointents.com/mcp | HTTPS enforced | 301 | https://istointents.com/mcp |
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 →
intent_get_intent State of a forwarded intent ~73
Returns the state of an intent published with intent_publish_intent, as the portal that holds it reports it, and which portal that is. Matches come from the chosen portal's own aggregation of its national market and may be incomplete.
| Name | Type | Req | Description |
|---|---|---|---|
| intentCode | string | yes | The intentCode returned by intent_publish_intent. |
| Name | Type | Req | Description |
|---|---|---|---|
| found | boolean | yes | – |
| holder | object | – | – |
| status | string | – | – |
No examples provided.
intent_list_matches Listings the portal found for a forwarded intent ~90
Returns the listings the portal found for the intent, unchanged — show every url as given. Works once the user has confirmed on the portal's page. Matches come from the chosen portal's own aggregation of its national market and may be incomplete.
| Name | Type | Req | Description |
|---|---|---|---|
| intentCode | string | yes | The intentCode returned by intent_publish_intent. |
| since | string | – | Optional ISO time; only matches delivered after it. |
| Name | Type | Req | Description |
|---|---|---|---|
| found | boolean | yes | – |
| holder | object | – | – |
| matches | array | – | – |
| status | string | – | – |
No examples provided.
intent_publish_intent Ask a local portal to keep looking for the user (needs the user's confirmation) ~448
Use this when the user wants to be told over time about a used car or a home that is not on offer today, in a given country — e.g. "let me know until March about an estate car in Portugal under 15 000 €, not diesel". The wish goes to an independent listing portal that serves that country and has asked to receive wishes this way (Isto Intents registry, istointents.org). It returns that portal's own consentUrl: the USER must open it, enter their own e-mail there and confirm — nothing is watched before that, and the contact stays with that portal. Never ask the user for their e-mail and never open or fill in the link for them. If several portals fit, the answer is outcome "choose_holder" with their names: ask the user which one, then call again with holder. If none serves the country yet, the answer is outcome "no_holder": tell the user plainly. Send the country only, never a city or address. hiddenLimit is optional and only if the user said it: it is passed once to the portal, sealed there, never stored here or shown to sellers. Matches come from the chosen portal's own aggregation of its national market and may be incomplete.
| Name | Type | Req | Description |
|---|---|---|---|
| buyBy | string | – | Date (YYYY-MM-DD) by which the user wants to buy; watching stops after it. |
| category | string | yes | vehicle = cars and other road vehicles; property = homes, flats and land. |
| country | string | yes | Country where the user wants to buy, ISO 3166-1 alpha-2 (e.g. PT, SK, CZ). Country only. |
| hiddenLimit | object | – | Optional private maximum price, only if the user stated it. |
| holder | string | – | Only after a "choose_holder" answer: the host of the portal the user chose. |
| niceToHave | string | – | Wishes that are not required (never filters), e.g. "tow bar, automatic". |
| statement | string | yes | What it MUST be, in the user's own words and language, e.g. "estate car under 15000 €, not diesel". |
| Name | Type | Req | Description |
|---|---|---|---|
| consentExpiresAt | string | – | – |
| consentUrl | string | – | The portal's page where the USER confirms with their own e-mail. Show it unchanged. |
| hiddenLimit | string | – | What happened to the hidden limit. If not passed, tell the user. |
| holder | object | – | – |
| holders | array | – | – |
| intentCode | string | – | Keep it in the conversation; use it with intent_get_intent, intent_list_matches and intent_withdraw_intent. |
| notUnderstood | array | – | – |
| outcome | string | yes | – |
| served | array | – | With no_holder: where portals can be reached today. |
| status | string | – | – |
| understood | array | – | – |
No examples provided.
intent_withdraw_intent Stop a forwarded intent ~55
Stops the intent at the portal immediately; nothing more is sent to the user. Cannot be undone — publishing again needs a new confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| intentCode | string | yes | The intentCode returned by intent_publish_intent. |
| Name | Type | Req | Description |
|---|---|---|---|
| found | boolean | yes | – |
| holder | object | – | – |
| status | string | – | – |
No examples provided.
How do I install the Isto Intents MCP server?
Isto Intents is a hosted endpoint at https://istointents.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 · istointents.com
claude mcp add --transport http com-istointents-intents 'https://istointents.com/mcp'
What is the Isto Intents MCP server?
Isto Intents is an MCP server listed in the public MCP registry as com.istointents/intents. Ask a local listing portal to keep looking for a used car or home; the user confirms there. This page covers its hosted endpoint (https://istointents.com/mcp).
Is the Isto Intents MCP server safe to use?
Isto Intents scores 63 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 Isto Intents MCP server expose?
Isto Intents exposes 4 tools: intent_publish_intent, intent_get_intent, intent_list_matches, intent_withdraw_intent. Their descriptions and schemas cost roughly 666 tokens of context every time the server is loaded.
Does the Isto Intents MCP server require authentication?
No. We connected to Isto Intents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Isto Intents MCP server still maintained?
Isto Intents is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.