# Isto Intents (remote · istointents.com)

Ask a local listing portal to keep looking for a used car or home; the user confirms there.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `istointents.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-istointents-intents/istointents.md), [page](https://verifymcp.io/servers/com-istointents-intents/istointents)

## Channel facts

- Endpoint: `https://istointents.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.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-10-25.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (intent_withdraw_intent).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 66/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 5 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 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.

### Claude

```bash
claude mcp add --transport http com-istointents-intents 'https://istointents.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-istointents-intents": {
      "url": "https://istointents.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-istointents-intents": {
      "type": "http",
      "url": "https://istointents.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-istointents-intents]
url = "https://istointents.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-istointents-intents": {
      "type": "remote",
      "url": "https://istointents.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-istointents-intents --url 'https://istointents.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-istointents-intents:
    url: "https://istointents.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-istointents-intents": {
      "Transport": "http",
      "Url": "https://istointents.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-istointents-intents -t streamable-http -u 'https://istointents.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-istointents-intents": {
      "type": "http",
      "url": "https://istointents.com/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-10-25 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-24 (score 63)

First indexed and scored.

## MCP tools (4)

### `intent_publish_intent` (~448 tokens)

Ask a local portal to keep looking for the user (needs the user's confirmation)

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.

Input parameters:

- `buyBy` (string): Date (YYYY-MM-DD) by which the user wants to buy; watching stops after it.
- `category` (string, required): vehicle = cars and other road vehicles; property = homes, flats and land.
- `country` (string, required): 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, required): What it MUST be, in the user's own words and language, e.g. "estate car under 15000 €, not diesel".

Output parameters:

- `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)
- `served` (array): With no_holder: where portals can be reached today.
- `status` (string)
- `understood` (array)

### `intent_get_intent` (~73 tokens)

State of a forwarded intent

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.

Input parameters:

- `intentCode` (string, required): The intentCode returned by intent_publish_intent.

Output parameters:

- `found` (boolean)
- `holder` (object)
- `status` (string)

### `intent_list_matches` (~90 tokens)

Listings the portal found for a forwarded intent

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.

Input parameters:

- `intentCode` (string, required): The intentCode returned by intent_publish_intent.
- `since` (string): Optional ISO time; only matches delivered after it.

Output parameters:

- `found` (boolean)
- `holder` (object)
- `matches` (array)
- `status` (string)

### `intent_withdraw_intent` (~55 tokens)

Stop a forwarded intent

Stops the intent at the portal immediately; nothing more is sent to the user. Cannot be undone — publishing again needs a new confirmation.

Input parameters:

- `intentCode` (string, required): The intentCode returned by intent_publish_intent.

Output parameters:

- `found` (boolean)
- `holder` (object)
- `status` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-istointents-intents/istointents#diagnostics

## Score history

- 2026-10-25: 63
- 2026-10-24: 63

## Common questions

### 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.

## Links

- Remote endpoint: https://istointents.com/mcp
- Website: https://istointents.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-istointents-intents/istointents.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-istointents-intents/istointents.json
- HTML version of this page: https://verifymcp.io/servers/com-istointents-intents/istointents