Remote MCP · Endpoint

AddressLore MCP server

No. AddressLore answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://addresslore.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.BurettoSofuto/addresslore
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
370 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Vancouver house histories by address: who lived there each year to 1945, permits and the 1912 map.
Listing
From the official MCP registry (active).
Recent checks of AddressLore
CheckedResultHandshake
5 hours agoHandshake completed370 ms
3 days agoHandshake completed51 ms
12 days agoHandshake completed99 ms
12 days agoHandshake completed64 ms
14 days agoHandshake completed90 ms
15 days agoHandshake completed54 ms
16 days agoHandshake completed281 ms
17 days agoHandshake completed257 ms
18 days agoHandshake completed89 ms
19 days agoHandshake completed99 ms
22 days agoHandshake completed57 ms
25 days agoHandshake completed88 ms
27 days agoHandshake completed109 ms

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

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