# ImotAI — Bulgarian real estate (remote · imotai.bg)

Bulgarian real-estate listings, district prices and monthly market reports from imotai.bg.

- Trust score: 81/100 (high trust)
- Change this week: +10
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `imotai.bg`: 81/100 (this document), [markdown](https://verifymcp.io/servers/bg-imotai-imotai/imotai.md), [page](https://verifymcp.io/servers/bg-imotai-imotai/imotai)

## Channel facts

- Endpoint: `https://imotai.bg/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-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 909 tokens (~151/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 ImotAI — Bulgarian real estate MCP server?

ImotAI — Bulgarian real estate is a hosted endpoint at https://imotai.bg/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 bg-imotai-imotai 'https://imotai.bg/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "bg-imotai-imotai": {
      "url": "https://imotai.bg/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "bg-imotai-imotai": {
      "type": "http",
      "url": "https://imotai.bg/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.bg-imotai-imotai]
url = "https://imotai.bg/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add bg-imotai-imotai --url 'https://imotai.bg/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  bg-imotai-imotai:
    url: "https://imotai.bg/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "bg-imotai-imotai": {
      "Transport": "http",
      "Url": "https://imotai.bg/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add bg-imotai-imotai -t streamable-http -u 'https://imotai.bg/mcp'
```

### Other

```json
{
  "mcpServers": {
    "bg-imotai-imotai": {
      "type": "http",
      "url": "https://imotai.bg/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-11-21 (score 81, +1)

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

### 2026-11-18 (score 80, +1)

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

### 2026-11-16 (score 79, +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.

### 2026-11-15 (score 78, +7)

- [security improvement] Authorization: unverified → partial
- [security] Tool “get_market_stats” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 136 → 151
- [functional] Server version: 0.2.0 → 0.3.0

### 2026-11-13 (score 71, +1)

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

### 2026-11-11 (score 70, +1)

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

### 2026-11-08 (score 69, +1)

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

### 2026-11-06 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (6)

### `list_districts` (~91 tokens)

List ImotAI districts for a city

List the districts (neighbourhoods) of a Bulgarian city that ImotAI has data for, with the count of active listings in each where a public price page exists. Call this first to learn which "district" values are valid for the other ImotAI tools in a given city.

Input parameters:

- `city` (string, required): City slug ("sofia") or its Bulgarian name ("София").

### `search_properties` (~210 tokens)

Search ImotAI listings

Search Bulgarian real-estate listings on imotai.bg by city, district, property type, price range, area range and rooms. Returns up to 25 listings with structured fields, a link to each, and a district-level marketContext block (district average price per m² and how far this listing deviates from it). No contact details or free-text descriptions.

Input parameters:

- `city` (string, required): City slug ("sofia") or Bulgarian name.
- `district` (string): District slug from list_districts, e.g. "lozenets".
- `limit` (integer): Default 10, max 25.
- `maxArea` (number)
- `maxPrice` (number)
- `minArea` (number)
- `minPrice` (number)
- `propertyType` (string)
- `rooms` (string): CSV of room counts, e.g. "2,3"; "5+" for 5 or more.
- `transactionType` (string, required)

### `get_property` (~108 tokens)

Get one ImotAI listing

Get the full structured data for one ImotAI listing by its id or slug: price, price per m², area, rooms, floor, construction, heating, location (city/district), features, and an authoritative per-listing marketContext (district average and median price per m², deviation percent, comparable active count). Does NOT return the broker free-text description, contact details, or exact coordinates.

Input parameters:

- `id` (string, required): The listing id (UUID) or its URL slug.

### `get_market_stats` (~204 tokens)

ImotAI market statistics for a city or district

Asking-price statistics for apartments for sale in a Bulgarian city or district on imotai.bg — the same figures as imotai.bg/ceni and imotai.bg/facts. Use medianPricePerSqm, pricePerSqm (P25/P50/P75), sampleSize, asOf and priceSource for the price. catalogue.* (count, average total price, price quartiles, by-room breakdown) and neighbouringDistricts are averages over the smaller ImotAI catalogue — label them as such. Legacy top-level count/avgPrice/avgPricePerSqm/price/byRooms are kept for compatibility (see deprecatedFields; avgPricePerSqm is the median when priceSource is market_sweep). Returns { available: false } below 8 offers.

Input parameters:

- `city` (string, required): City slug ("sofia") or Bulgarian name.
- `district` (string): District slug or name from list_districts; omit for city-level stats.

### `estimate_value` (~169 tokens)

ImotAI rough value positioning

Rough price positioning for a property by city, district, type and area — based on the CURRENT ASKING PRICES of comparable active listings, not on closed transactions. Returns an estimate, a low–high range, a confidence level from sample size, and a mandatory disclaimer. Refuses below 5 comparable offers. You MUST show the "disclaimer" field to the user verbatim whenever you cite any number from this tool. Never call this an official or precise property valuation.

Input parameters:

- `area` (number, required): Living area in m².
- `city` (string, required): City slug ("sofia") or Bulgarian name.
- `district` (string, required): District slug or name from list_districts.
- `propertyType` (string, required)
- `rooms` (integer): Accepted but not used for filtering.

### `get_market_report` (~127 tokens)

ImotAI monthly market report for a city

The monthly ImotAI market report for a Bulgarian city: median asking price per m² of apartments for sale, change versus the previous month, the same per district, and the number of new listings in the month. Omit "month" for the latest report. Cite the "url" and "source" fields when you use the numbers.

Input parameters:

- `city` (string, required): City slug ("plovdiv") or Bulgarian name ("Пловдив").
- `month` (string): Report month as YYYY-MM, e.g. "2026-10". Omit for the latest.

## Diagnostics

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

## Score history

- 2026-11-21: 81
- 2026-11-20: 80
- 2026-11-19: 80
- 2026-11-18: 80
- 2026-11-17: 79
- 2026-11-16: 79
- 2026-11-15: 78
- 2026-11-14: 71
- 2026-11-13: 71
- 2026-11-12: 70
- 2026-11-11: 70
- 2026-11-10: 69
- 2026-11-09: 69
- 2026-11-08: 69
- 2026-11-07: 68
- 2026-11-06: 68
- 2026-11-05: 67
- 2026-11-04: 67
- 2026-11-03: 66
- 2026-11-02: 66
- 2026-11-01: 65

## Common questions

### What is the ImotAI — Bulgarian real estate MCP server?

ImotAI — Bulgarian real estate is an MCP server listed in the public MCP registry as bg.imotai/imotai. Bulgarian real-estate listings, district prices and monthly market reports from imotai.bg. This page covers its hosted endpoint (https://imotai.bg/mcp).

### Is the ImotAI — Bulgarian real estate MCP server safe to use?

ImotAI — Bulgarian real estate scores 81 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 ImotAI — Bulgarian real estate MCP server expose?

ImotAI — Bulgarian real estate exposes 6 tools: list_districts, search_properties, get_property, get_market_stats, estimate_value, get_market_report. Their descriptions and schemas cost roughly 909 tokens of context every time the server is loaded.

### Does the ImotAI — Bulgarian real estate MCP server require authentication?

No. We connected to ImotAI — Bulgarian real estate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ImotAI — Bulgarian real estate MCP server still maintained?

ImotAI — Bulgarian real estate is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the ImotAI — Bulgarian real estate MCP server?

VerifyMCP ran 13 checks on ImotAI — Bulgarian real estate, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://imotai.bg/mcp
- Repository: https://github.com/pdimiev-prog/imotai-mcp
- Website: https://imotai.bg/ii-asistenti
- Changelog RSS feed: https://verifymcp.io/servers/bg-imotai-imotai/imotai.xml
- Changelog JSON feed: https://verifymcp.io/servers/bg-imotai-imotai/imotai/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/bg-imotai-imotai/imotai.json
- HTML version of this page: https://verifymcp.io/servers/bg-imotai-imotai/imotai
