Remote MCP · Endpoint

Listr.no MCP server

No. Listr.no answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://www.listr.no/api/mcp

The last check completed an MCP handshake.

Registry name
no.listr/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
263 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Short positions and insider trades in Norwegian listed companies. Read-only, no login.
Listing
From the official MCP registry (active).
Recent checks of Listr.no
CheckedResultHandshake
44 minutes agoHandshake completed263 ms
3 days agoHandshake completed191 ms
13 days agoHandshake completed715 ms
13 days agoHandshake completed896 ms
15 days agoHandshake completed241 ms
15 days agoHandshake completed222 ms
17 days agoHandshake completed255 ms
18 days agoHandshake completed178 ms
18 days agoHandshake completed226 ms
20 days agoHandshake completed226 ms
22 days agoHandshake completed200 ms
25 days agoHandshake completed849 ms
27 days agoHandshake completed243 ms
29 days agoHandshake completed272 ms

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

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