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.

LICHIDARE.MD

REMOTE · MCP.LICHIDARE.MD

Assets for sale in Moldova from insolvency, enforcement, bank collateral and public auctions

Available components

+4 this week 76 Trust /100

Last scanned (3 hours ago)

Scores higher than 70% of remote servers

Reachable. Last reached 24 Oct 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
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1205 tokens (~241/item across 5 items; 5 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 Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 86% 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 5 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 current MCP spec version (2026-07-28).Pass
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.

  • 24 Oct 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.

  • 22 Oct 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.

  • 21 Oct 26 0
    • Tool “alert_subscription_link” rewrote its description, which is the text the model reads security
  • 20 Oct 26 +1

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

  • 18 Oct 26 +1

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

  • 16 Oct 26 +1
    • Tool “get_listing” rewrote its description, which is the text the model reads security
    • Tool “upcoming_auctions” rewrote its description, which is the text the model reads security
  • 14 Oct 26 +1

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

  • 13 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
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 24 Oct 2026 · Probed https://mcp.lichidare.md/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.lichidare.md CN=YR1,O=Let's Encrypt,C=US 4 Oct 2026 2 Jan 2027 RSA 2048 SHA256-RSA 6fc9254f8d2dc5654aed45cae87e207cc10
SANs: mcp.lichidare.md
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 mcp.lichidare.md. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
md. present 127 14 Verified
lichidare.md. 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
strict-transport-security max-age=63072000

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.lichidare.md/mcp Verified 200
http (plaintext) http://mcp.lichidare.md/mcp HTTPS enforced 308 https://mcp.lichidare.md/mcp
MCP tools · 5 exposed · ~1,096 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
alert_subscription_link ~206

Intoarce linkul catre catalogul LICHIDARE.MD filtrat dupa o categorie, o procedura si o regiune, cu formularul de alerte deschis si aceste trei criterii deja selectate, plus canalul Telegram. Utilizatorul introduce doar adresa de e-mail si confirma abonarea din e-mail. Instrumentul nu trimite si nu stocheaza nicio adresa de e-mail.

NameTypeReqDescription
categorystring–imobile (inclusiv terenuri), transport, echipament (industrial/agricol) sau alte bunuri
procedurestring–Procedura de vanzare: insolvabilitate, executare_silita, gaj_bancar, sfs (bunuri confiscate), apl (primarii), alta
regionstring–Raion sau municipiu, ex. 'Chisinau', 'Balti', 'Nisporeni', 'Stefan Voda'

No output schema declared.

No examples provided.

get_listing ~231

Intoarce detaliile unui anunt LICHIDARE.MD dupa id: descriere, lista loturilor cu preturi de pornire, data licitatiei, vanzatorul (rolul si denumirea) si sursa oficiala (Monitorul Oficial, Registrul Insolvabilitatii etc.). Telefoanele si e-mailurile nu sunt incluse: datele de contact si conditiile de participare sunt in anuntul oficial (source_url). Cererea de participare se depune direct la vanzator; LICHIDARE.MD nu o transmite. applications_closed=true inseamna ca termenul de depunere a expirat.

NameTypeReqDescription
idintegeryesId-ul anuntului, ex. 8927 din https://lichidare.md/listing.php?id=8927
langstring–Limba textelor din anunt (ro sau ru), daca exista traducere
max_lotsinteger–Cate loturi sa fie listate (unele anunturi au sute de loturi)

No output schema declared.

No examples provided.

market_overview ~57

Statistica agregata a catalogului LICHIDARE.MD: anunturi active, licitatii viitoare, repartizarea pe categorii, proceduri si tipuri de vanzatori. Nu contine date despre persoane.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_listings ~354

Cauta in catalogul LICHIDARE.MD anunturi active de vanzare a bunurilor din insolvabilitate, executare silita, gaj bancar, SFS si primarii din Republica Moldova. Filtreaza dupa text, categorie, procedura, regiune, interval de pret si existenta licitatiei. Intoarce o lista scurta cu id, titlu, pret de pornire, localitate, data licitatiei si link; detaliile se obtin cu get_listing.

NameTypeReqDescription
auction_onlyboolean–Doar anunturi vandute prin licitatie
categorystring–imobile (inclusiv terenuri), transport, echipament (industrial/agricol) sau alte bunuri
langstring–Limba textelor din anunt (ro sau ru), daca exista traducere
limitinteger––
pageinteger–Pagina rezultatelor
price_maxnumber–Pret maxim de pornire
price_minnumber–Pret minim de pornire
procedurestring–Procedura de vanzare: insolvabilitate, executare_silita, gaj_bancar, sfs (bunuri confiscate), apl (primarii), alta
qstring–Text liber, ex. 'tractor', 'apartament', 'teren agricol', numele vanzatorului
regionstring–Raion sau municipiu, ex. 'Chisinau', 'Balti', 'Nisporeni', 'Stefan Voda'
sortstring––

No output schema declared.

No examples provided.

upcoming_auctions ~248

Lista licitatiilor programate in urmatoarele N zile (implicit 14), ordonate dupa data, cu filtre optionale pe categorie, procedura si regiune. Pentru intrebari de tipul 'ce licitatii sunt saptamana viitoare in Chisinau'. Licitatiile la care termenul de depunere a cererilor a expirat raman in lista, marcate DEPUNEREA CERERILOR INCHISA (applications_closed=true).

NameTypeReqDescription
categorystring–imobile (inclusiv terenuri), transport, echipament (industrial/agricol) sau alte bunuri
daysinteger–Orizontul in zile de la data de azi (ora Moldovei)
limitinteger––
procedurestring–Procedura de vanzare: insolvabilitate, executare_silita, gaj_bancar, sfs (bunuri confiscate), apl (primarii), alta
regionstring–Raion sau municipiu, ex. 'Chisinau', 'Balti', 'Nisporeni', 'Stefan Voda'

No output schema declared.

No examples provided.

Install

How do I install the LICHIDARE.MD MCP server?

LICHIDARE.MD is a hosted endpoint at https://mcp.lichidare.md/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 · mcp.lichidare.md

# add to Claude Code
claude mcp add --transport http md-lichidare-catalog 'https://mcp.lichidare.md/mcp'
Common questions

What is the LICHIDARE.MD MCP server?

LICHIDARE.MD is an MCP server listed in the public MCP registry as md.lichidare/catalog. Assets for sale in Moldova from insolvency, enforcement, bank collateral and public auctions. This page covers its hosted endpoint (https://mcp.lichidare.md/mcp).

Is the LICHIDARE.MD MCP server safe to use?

LICHIDARE.MD scores 76 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 LICHIDARE.MD MCP server expose?

LICHIDARE.MD exposes 5 tools: search_listings, get_listing, upcoming_auctions, market_overview, alert_subscription_link. Their descriptions and schemas cost roughly 1,096 tokens of context every time the server is loaded.

Does the LICHIDARE.MD MCP server require authentication?

No. We connected to LICHIDARE.MD without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the LICHIDARE.MD MCP server still maintained?

LICHIDARE.MD is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.