Remote MCP · Endpoint

LenDb.ai MCP server

No. LenDb.ai answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://lendb.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.lendb/lendb
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
115 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Find US mortgage loan officers for a borrower's situation and place. Free, lender-neutral, sourced.
Listing
From the official MCP registry (active).
Recent checks of LenDb.ai
CheckedResultHandshake
4 hours agoHandshake completed115 ms
10 days agoHandshake completed117 ms
11 days agoHandshake completed304 ms
11 days agoHandshake completed125 ms
13 days agoHandshake completed698 ms
14 days agoHandshake completed332 ms
15 days agoHandshake completed120 ms
16 days agoHandshake completed129 ms
17 days agoHandshake completed118 ms
19 days agoHandshake completed1.49 s
22 days agoHandshake completed88 ms
24 days agoHandshake completed190 ms
26 days agoHandshake completed98 ms
29 days agoHandshake completed213 ms

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

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 LenDb.ai and makes no claim about it beyond what these checks measured.