Remote MCP · Endpoint

pekt – norske domener MCP server

No. pekt – norske domener answered an MCP handshake 22 minutes ago.

UpLast checked 22 minutes ago

Server URL

https://pekt.no/mcp/public

The last check completed an MCP handshake.

Registry name
io.github.datamynt/pekt
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
132 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Check if a domain is available and what it costs at pekt, a Norwegian domain service. No login.
Listing
From the official MCP registry (active).
Recent checks of pekt – norske domener
CheckedResultHandshake
22 minutes agoHandshake completed132 ms
9 days agoHandshake completed132 ms
10 days agoHandshake completed173 ms
11 days agoHandshake completed137 ms
12 days agoHandshake completed140 ms
14 days agoHandshake completed137 ms
14 days agoHandshake completed142 ms
15 days agoHandshake completed137 ms
17 days agoHandshake completed316 ms
19 days agoHandshake completed158 ms
21 days agoHandshake completed136 ms
24 days agoHandshake completed137 ms
26 days agoHandshake completed138 ms
28 days agoHandshake completed128 ms

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

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