Remote MCP · Endpoint

SecureLend Underwriting MCP server

No — it is up, but it requires credentials. SecureLend Underwriting answered 2 days ago with an authentication challenge rather than a session.

Auth requiredLast checked 2 days ago

Server URL

https://mcp.securelend.ai/v1/lender/mcp

The endpoint is answering and asked us for credentials. That is a working server, not an outage.

Registry name
ai.securelend/lender
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
27 tools
Uptime, last 30 days
100% from 11 checks
Described by its publisher as
Open a credit file, chase gaps, screen sanctions, draft a cited memo. Person decides.
Listing
From the official MCP registry (active).
Recent checks of SecureLend Underwriting
CheckedResultHandshake
2 days agoCredentials required—
6 days agoCredentials required—
16 days agoHandshake completed179 ms
17 days agoHandshake completed378 ms
18 days agoHandshake completed227 ms
19 days agoHandshake completed257 ms
21 days agoHandshake completed248 ms
21 days agoHandshake completed246 ms
22 days agoHandshake completed233 ms
23 days agoHandshake completed233 ms
25 days agoHandshake completed343 ms

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

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