Remote MCP · Endpoint

HMDA Mortgage Data MCP server

No. HMDA Mortgage Data answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.olyport.com/hmda/mcp

The last check completed an MCP handshake.

Registry name
com.olyport/hmda
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
79 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Home mortgage lending patterns, denial rates, and fair lending data
Listing
From the official MCP registry (active).
Recent checks of HMDA Mortgage Data
CheckedResultHandshake
2 hours agoHandshake completed79 ms
2 days agoHandshake completed81 ms
4 days agoHandshake completed84 ms
6 days agoHandshake completed78 ms
7 days agoHandshake completed87 ms
8 days agoHandshake completed78 ms
10 days agoHandshake completed80 ms
12 days agoHandshake completed96 ms
14 days agoHandshake completed77 ms
16 days agoHandshake completed232 ms
17 days agoHandshake completed82 ms
18 days agoHandshake completed96 ms
19 days agoHandshake completed78 ms
20 days agoHandshake completed228 ms
21 days agoHandshake completed76 ms
22 days agoHandshake completed80 ms
23 days agoHandshake completed85 ms

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

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