Remote MCP · Endpoint

NL Ledger MCP server

No. NL Ledger answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://nlledger.ca/mcp

The last check completed an MCP handshake.

Registry name
ca.nlledger/nl-ledger
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
176 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
NL provincial and federal spending records, each with its source. Addresses do not locate work.
Listing
From the official MCP registry (active).
Recent checks of NL Ledger
CheckedResultHandshake
1 hour agoHandshake completed176 ms
2 days agoHandshake completed90 ms
4 days agoHandshake completed168 ms
7 days agoHandshake completed166 ms
9 days agoHandshake completed280 ms
11 days agoHandshake completed44 ms
13 days agoHandshake completed283 ms
15 days agoHandshake completed86 ms
16 days agoHandshake completed280 ms
18 days agoHandshake completed43 ms
19 days agoHandshake completed313 ms
20 days agoHandshake completed203 ms
23 days agoHandshake completed276 ms
24 days agoHandshake completed1.28 s

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