ImotAI — Bulgarian real estate
REMOTE · IMOTAI.BG
Bulgarian real-estate listings, district prices and monthly market reports from imotai.bg.
Available components
Last scanned (21 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
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 Security80
- 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. 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability69
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +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.
- 18 Nov 26 +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.
- 16 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.
- 15 Nov 26 +7
- Authorization: unverified → partial ▲ security
- Tool “get_market_stats” rewrote its description, which is the text the model reads security
- Schema quality: 136 → 151 ▼ functional
- Server version: 0.2.0 → 0.3.0 functional
- 13 Nov 26 +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.
- 11 Nov 26 +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.
- 8 Nov 26 +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.
- 6 Nov 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 21 Nov 2026 · Probed https://imotai.bg/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=imotai.bg | CN=YE1,O=Let's Encrypt,C=US | 5 Nov 2026 | 3 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 62b6f6f7715d87cf28cbc53bf6b029123a9 |
| SANs: *.imotai.bg, imotai.bg | ||||||
| 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 imotai.bg. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| bg. | DS published | 58606 | 8 | Verified |
| imotai.bg. | No DS | 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=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://imotai.bg/mcp | Verified | 200 | |
| http (plaintext) | http://imotai.bg/mcp | HTTPS enforced | 301 | https://imotai.bg/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 →
estimate_value ImotAI rough value positioning ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| area | number | yes | Living area in m². |
| city | string | yes | City slug ("sofia") or Bulgarian name. |
| district | string | yes | District slug or name from list_districts. |
| propertyType | string | yes | – |
| rooms | integer | – | Accepted but not used for filtering. |
No output schema declared.
No examples provided.
get_market_report ImotAI monthly market report for a city ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City slug ("plovdiv") or Bulgarian name ("Пловдив"). |
| month | string | – | Report month as YYYY-MM, e.g. "2026-10". Omit for the latest. |
No output schema declared.
No examples provided.
get_market_stats ImotAI market statistics for a city or district ~204
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City slug ("sofia") or Bulgarian name. |
| district | string | – | District slug or name from list_districts; omit for city-level stats. |
No output schema declared.
No examples provided.
get_property Get one ImotAI listing ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The listing id (UUID) or its URL slug. |
No output schema declared.
No examples provided.
list_districts List ImotAI districts for a city ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | City slug ("sofia") or its Bulgarian name ("София"). |
No output schema declared.
No examples provided.
search_properties Search ImotAI listings ~210
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | 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 | yes | – |
No output schema declared.
No examples provided.
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.
remote · imotai.bg
claude mcp add --transport http bg-imotai-imotai 'https://imotai.bg/mcp'
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.