pekt – norske domener
REMOTE · PEKT.NO
Check if a domain is available and what it costs at pekt, a Norwegian domain service. No login.
Available components
Last scanned (10 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 543 tokens (~135/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://pekt.no/mcp/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pekt.no | CN=WR3,O=Google Trust Services,C=US | 12 Oct 2026 | 10 Jan 2027 | RSA 2048 | SHA256-RSA | 7c0ecefae81d48a81256246d76540fef |
| SANs: pekt.no | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pekt.no. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| no. | DS published | 38032 | 13 | Verified |
| pekt.no. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pekt.no/mcp/public | Verified | 200 | |
| http (plaintext) | http://pekt.no/mcp/public | HTTPS enforced | 302 | https://pekt.no/mcp/public |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_domain Check if a domain is available and what it costs ~108
Check whether one domain name is available to register at pekt, a Norwegian domain service, and what it costs: first-year and renewal price in NOK per year including 25 % Norwegian VAT. If the extension is not sold, the reason is given. Always show the user the returned buy_url.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Domain with its extension, e.g. example.no. A bare name such as example is checked as example.no. Unicode names such as blåbær.no are fine. |
No output schema declared.
No examples provided.
list_extensions List the extensions pekt sells, with prices ~71
List the domain extensions pekt sells with first-year and renewal price in NOK per year incl. 25 % VAT. Default is the most popular ones; pass a category for others.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | popular (default), bedrift, teknologi, butikk, kreativt, livsstil or sted. |
No output schema declared.
No examples provided.
requirements What an extension needs and costs ~100
What buying one extension (TLD) at pekt involves: whether it is for sale, price per action (register, renew, transfer), who may own it (e.g. .eu needs an EU/EEA holder, .se and .nu need an ID number) and registry notices. Prices in NOK incl. 25 % VAT.
| Name | Type | Req | Description |
|---|---|---|---|
| tld | string | yes | The extension without a dot, e.g. no, com or eu. |
No output schema declared.
No examples provided.
suggest_domains Check a name across popular extensions ~103
Check one name (e.g. mycompany) across the most popular extensions (.no, .com, .net, .org, .io, .app ...) and return which are available, with prices in NOK per year incl. 25 % VAT and a buy_url for each.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many extensions to check, default 10, max 25. |
| name | string | yes | The name without extension, e.g. mycompany. |
No output schema declared.
No examples provided.
How do I install the pekt – norske domener MCP server?
pekt – norske domener is a hosted endpoint at https://pekt.no/mcp/public, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · pekt.no
claude mcp add --transport http datamynt-pekt 'https://pekt.no/mcp/public'
What is the pekt – norske domener MCP server?
pekt – norske domener is an MCP server listed in the public MCP registry as io.github.datamynt/pekt. Check if a domain is available and what it costs at pekt, a Norwegian domain service. No login. This page covers its hosted endpoint (https://pekt.no/mcp/public).
Is the pekt – norske domener MCP server safe to use?
pekt – norske domener scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the pekt – norske domener MCP server expose?
pekt – norske domener exposes 4 tools: check_domain, suggest_domains, requirements, list_extensions. Their descriptions and schemas cost roughly 382 tokens of context every time the server is loaded.
Does the pekt – norske domener MCP server require authentication?
No. We connected to pekt – norske domener without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the pekt – norske domener MCP server still maintained?
pekt – norske domener is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the pekt – norske domener MCP server?
VerifyMCP ran 13 checks on pekt – norske domener, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.