Remote MCP · Endpoint

Veldora MCP server

No. Veldora answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://veldora.no/mcp

The last check completed an MCP handshake.

Registry name
io.github.tintun2602/veldora
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
200 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Norwegian public data for AI agents: companies, tenders, addresses, laws, exchange rates.
Listing
From the official MCP registry (active).
Recent checks of Veldora
CheckedResultHandshake
13 minutes agoHandshake completed200 ms
9 days agoHandshake completed189 ms
9 days agoHandshake completed216 ms
11 days agoHandshake completed205 ms
12 days agoHandshake completed175 ms
13 days agoHandshake completed323 ms
14 days agoHandshake completed187 ms
15 days agoHandshake completed195 ms
16 days agoHandshake completed366 ms
19 days agoHandshake completed178 ms
21 days agoHandshake completed180 ms
24 days agoHandshake completed168 ms
26 days agoHandshake completed291 ms
28 days agoHandshake completed188 ms

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

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