Remote MCP · Endpoint

MapLedger MCP server

No. MapLedger answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://mapledger.app/mcp

The last check completed an MCP handshake.

Registry name
app.mapledger/land-and-zoning
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
630 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Zoning, homes per lot, short-term rentals, tax and flood for any property in Austin and Nashville.
Listing
From the official MCP registry (active).
Recent checks of MapLedger
CheckedResultHandshake
20 minutes agoHandshake completed630 ms
8 days agoHandshake completed140 ms
9 days agoHandshake completed151 ms
11 days agoHandshake completed179 ms
12 days agoHandshake completed120 ms
13 days agoHandshake completed264 ms
14 days agoHandshake completed141 ms
14 days agoHandshake completed178 ms
16 days agoHandshake completed113 ms
19 days agoHandshake completed156 ms
21 days agoHandshake completed144 ms
24 days agoHandshake completed131 ms
26 days agoHandshake completed349 ms
28 days agoHandshake completed165 ms

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

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