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.

Neofort IMO — ansambluri rezidențiale București

REMOTE · WWW.NEOFORT.RO

New-build apartments for sale in Bucharest by Neofort IMO: availability, prices excl. VAT, contact.

Available components

75 Trust /100

Last scanned (18 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 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 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
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1084 tokens (~180/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 Management20
  • Stability observed for 6 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
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 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

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 →

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Stability: unverified → 0.03 ▲ functional
  • 15 Nov 26 72

    First indexed and scored.

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 21 Nov 2026 · Probed https://www.neofort.ro/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.neofort.ro CN=YR1,O=Let's Encrypt,C=US 25 Oct 2026 23 Jan 2027 RSA 2048 SHA256-RSA 51bd9774c0cf25bea32d7b029efc1fb4fa5
SANs: www.neofort.ro
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.neofort.ro. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ro. DS published 39877 8 Verified
neofort.ro. 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=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.neofort.ro/api/mcp Verified 200
http (plaintext) http://www.neofort.ro/api/mcp HTTPS enforced 308 https://www.neofort.ro/api/mcp
MCP tools · 6 exposed · ~843 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
calculate_mortgage ~201

Indicative monthly mortgage payment, using the same formula as the calculator on neofort.ro. VAT (21%) is added to the price first, because website prices exclude VAT and the bank finances the full price. Give either a price in EUR excluding VAT or a project (its starting price is used). Defaults: 15% down payment, 25 years, 7.5% APR (DAE). Not a bank offer.

NameTypeReqDescription
dae_pctnumber–Annual percentage rate (DAE) in % (default 7.5).
down_payment_pctnumber–Down payment in % of the price incl. VAT (default 15).
price_eur_excl_vatnumber–Apartment price in EUR, excluding VAT.
projectstring–Alternative to price: project slug, number or name (uses its starting price).
yearsinteger–Loan term in years (default 25).

No output schema declared.

No examples provided.

get_contact ~92

How to reach Neofort IMO: phone, WhatsApp, email, office address, opening hours and contact form. With a project, also the broker in charge of it and their phone. Use this to send the person to a human for a firm offer, a viewing or a reservation — this server cannot send requests.

NameTypeReqDescription
projectstring–Optional project slug, number or name, to get its broker.

No output schema declared.

No examples provided.

get_project ~121

Full details of one Neofort IMO residential project: description, every apartment type with prices and availability (sold units are marked), parking, amenities, distances to metro/schools/shops, FAQ and broker. Works for projects on sale and for sold projects in the portfolio. Accepts the slug, "Neofort 84", "84" or part of the name.

NameTypeReqDescription
projectstringyesProject slug, number or name, e.g. "neofort-84-titan-pallady" or "Neofort 84".

No output schema declared.

No examples provided.

list_projects ~83

List all Neofort IMO residential projects currently on sale (zone, stage, room types, starting price in EUR excl. VAT, available units). Optionally also the sold projects from the portfolio, as track record.

NameTypeReqDescription
include_soldboolean–Also list sold projects from the portfolio (default false).
zonestring–Optional area or sector filter.

No output schema declared.

No examples provided.

search_apartments ~223

Search AVAILABLE apartments across Neofort IMO residential projects in Bucharest. Filters: rooms, max price (EUR, excl. VAT), min area, zone/sector, stage, promotions only. Results are sorted by price ascending and include every price option shown on the website (e.g. by down-payment level). All prices are in EUR and EXCLUDE 21% VAT.

NameTypeReqDescription
limitinteger–Max results (default 20).
max_price_eurnumber–Maximum price in EUR, excluding VAT.
min_area_sqmnumber–Minimum usable area in square metres.
promo_onlyboolean–Only apartments with an active promotion.
roomsinteger–Number of rooms (1 = studio/garsonieră; 4 means 4 or more).
stagestring–finalizat = ready to move in; in_constructie = under construction.
zonestring–Area or sector, e.g. "Titan", "Colentina", "Sector 3", "Militari".

No output schema declared.

No examples provided.

search_articles ~123

Search the Neofort IMO blog (Romanian) about buying property in Bucharest: taxes, VAT, mortgages, legislation, short-term rental, owners associations, neighbourhoods. Returns title, summary, dates and links; read the "markdown" link for the full text. Without a query, returns the latest articles.

NameTypeReqDescription
limitinteger–Max results (default 5).
querystring–Topic keywords, ideally in Romanian, e.g. "impozit locuinta", "TVA apartament nou", "regim hotelier".

No output schema declared.

No examples provided.

Install

How do I install the Neofort IMO — ansambluri rezidențiale București MCP server?

Neofort IMO — ansambluri rezidențiale București is a hosted endpoint at https://www.neofort.ro/api/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 · www.neofort.ro

# add to Claude Code
claude mcp add --transport http ro-neofort-www-ansambluri-rezidentiale 'https://www.neofort.ro/api/mcp'
Common questions

What is the Neofort IMO — ansambluri rezidențiale București MCP server?

Neofort IMO — ansambluri rezidențiale București is an MCP server listed in the public MCP registry as ro.neofort.www/ansambluri-rezidentiale. New-build apartments for sale in Bucharest by Neofort IMO: availability, prices excl. VAT, contact. This page covers its hosted endpoint (https://www.neofort.ro/api/mcp).

Is the Neofort IMO — ansambluri rezidențiale București MCP server safe to use?

Neofort IMO — ansambluri rezidențiale București scores 75 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 Neofort IMO — ansambluri rezidențiale București MCP server expose?

Neofort IMO — ansambluri rezidențiale București exposes 6 tools: search_apartments, get_project, list_projects, search_articles, get_contact, calculate_mortgage. Their descriptions and schemas cost roughly 843 tokens of context every time the server is loaded.

Does the Neofort IMO — ansambluri rezidențiale București MCP server require authentication?

No. We connected to Neofort IMO — ansambluri rezidențiale București without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Neofort IMO — ansambluri rezidențiale București MCP server still maintained?

Neofort IMO — ansambluri rezidențiale București 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 Neofort IMO — ansambluri rezidențiale București MCP server?

VerifyMCP ran 13 checks on Neofort IMO — ansambluri rezidențiale București, 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.