Remote MCP · Endpoint

LICHIDARE.MD MCP server

No. LICHIDARE.MD answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.lichidare.md/mcp

The last check completed an MCP handshake.

Registry name
md.lichidare/catalog
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
124 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Assets for sale in Moldova from insolvency, enforcement, bank collateral and public auctions
Listing
From the official MCP registry (active).
Recent checks of LICHIDARE.MD
CheckedResultHandshake
1 hour agoHandshake completed124 ms
12 hours agoHandshake completed94 ms
1 day agoHandshake completed71 ms
2 days agoHandshake completed78 ms
4 days agoHandshake completed134 ms
4 days agoHandshake completed127 ms
5 days agoHandshake completed206 ms
6 days agoHandshake completed101 ms
8 days agoHandshake completed222 ms
11 days agoHandshake completed76 ms
13 days agoHandshake completed115 ms
16 days agoHandshake completed599 ms
18 days agoHandshake completed851 ms
20 days agoHandshake completed74 ms
22 days agoHandshake completed107 ms
24 days agoHandshake completed126 ms

The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with LICHIDARE.MD and makes no claim about it beyond what these checks measured.