pekt – norske domener is an MCP server published by io.github.datamynt, hosted at pekt.no. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 8 tools, including check_domain, suggest_domains, requirements, list_extensions, list_services.
Check if a domain is available and what it costs at pekt, a Norwegian domain service. No login.
83 connections through 4 shared values. Tap any node.
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.
| Parameter | Type | Description |
|---|---|---|
| name * | string | 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. |
{
"name": "check_domain",
"title": "Check if a domain is available and what it costs",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "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."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
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.
| Parameter | Type | Description |
|---|---|---|
| name * | string | The name without extension, e.g. mycompany. |
| limit | integer | How many extensions to check, default 10, max 25. |
{
"name": "suggest_domains",
"title": "Check a name across popular extensions",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "The name without extension, e.g. mycompany."
},
"limit": {
"type": "integer",
"maximum": 25,
"minimum": 1,
"description": "How many extensions to check, default 10, max 25."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| tld * | string | The extension without a dot, e.g. no, com or eu. |
{
"name": "requirements",
"title": "What an extension needs and costs",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"tld"
],
"properties": {
"tld": {
"type": "string",
"description": "The extension without a dot, e.g. no, com or eu."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| category | string | popular (default), bedrift, teknologi, butikk, kreativt, livsstil or sted. |
{
"name": "list_extensions",
"title": "List the extensions pekt sells, with prices",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [],
"properties": {
"category": {
"enum": [
"popular",
"bedrift",
"teknologi",
"butikk",
"kreativt",
"livsstil",
"sted"
],
"type": "string",
"description": "popular (default), bedrift, teknologi, butikk, kreativt, livsstil or sted."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}List the services pekt can point a domain at, grouped as web (where the site or app is hosted) and mail (who receives e-mail): Vercel, Netlify, GitHub Pages, Cloud Run, Cloudflare Pages, Firebase, Render, Fly.io, Lovable, Replit, Webflow, Framer, Shopify, Squarespace, Wix, Google Workspace, Microsoft 365, Proton Mail, Fastmail, iCloud Mail, plus custom IP or host targets and "none". For each: its key, group, name and the inputs the user must copy from the provider. Use it when the user is building a site or app, or setting up e-mail, and needs to connect a domain; then call dns_records. No lookups.
No parameters.
{
"name": "list_services",
"title": "Services pekt can point a domain at",
"description": "List the services pekt can point a domain at, grouped as web (where the site or app is hosted) and mail (who receives e-mail): Vercel, Netlify, GitHub Pages, Cloud Run, Cloudflare Pages, Firebase, Render, Fly.io, Lovable, Replit, Webflow, Framer, Shopify, Squarespace, Wix, Google Workspace, Microsoft 365, Proton Mail, Fastmail, iCloud Mail, plus custom IP or host targets and \"none\". For each: its key, group, name and the inputs the user must copy from the provider. Use it when the user is building a site or app, or setting up e-mail, and needs to connect a domain; then call dns_records. No lookups.",
"inputSchema": {
"type": "object",
"required": [],
"properties": {},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}Get the exact DNS records that point one domain at one service from list_services, for any domain at any DNS provider: name, type, TTL and values to set, and values to remove. The domain's current records are read from public DNS, so an existing SPF is merged and an existing CAA extended, the same way pekt changes its own zones (one planner). Use it when the user must point a domain at their app, site or mail provider, or asks which records to add. Read-only: nothing changes. how_to_apply says how the records get written: by the user at their DNS provider, or by pekt after the owner approves when the domain is at pekt. blocked=true means the change would break something (see findings) and no records are given; an error with retryable=true means a lookup failed, so try again after retry_after seconds.
| Parameter | Type | Description |
|---|---|---|
| domain * | string | The domain itself, e.g. example.no (Unicode such as blåbær.no is fine). Any registrar, any DNS provider. |
| params | object | The inputs that service needs (see list_services), copied from the provider. Omit for services with no required inputs. |
| service * | string | A service key from list_services, e.g. the web or mail service the user named. |
{
"name": "dns_records",
"title": "Exact DNS records to point a domain at a service",
"description": "Get the exact DNS records that point one domain at one service from list_services, for any domain at any DNS provider: name, type, TTL and values to set, and values to remove. The domain's current records are read from public DNS, so an existing SPF is merged and an existing CAA extended, the same way pekt changes its own zones (one planner). Use it when the user must point a domain at their app, site or mail provider, or asks which records to add. Read-only: nothing changes. how_to_apply says how the records get written: by the user at their DNS provider, or by pekt after the owner approves when the domain is at pekt. blocked=true means the change would break something (see findings) and no records are given; an error with retryable=true means a lookup failed, so try again after retry_after seconds.",
"inputSchema": {
"type": "object",
"required": [
"domain",
"service"
],
"properties": {
"domain": {
"type": "string",
"description": "The domain itself, e.g. example.no (Unicode such as blåbær.no is fine). Any registrar, any DNS provider."
},
"params": {
"type": "object",
"description": "The inputs that service needs (see list_services), copied from the provider. Omit for services with no required inputs.",
"additionalProperties": {
"type": "string"
}
},
"service": {
"type": "string",
"description": "A service key from list_services, e.g. the web or mail service the user named."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}See what a domain points at today, from public DNS: its nameservers and DNS provider, the web target (apex and www records and the service they match), the mail provider (MX, SPF, DMARC) and the DNSSEC state. Use it before suggesting changes, to explain the current setup, or to check that new records are live. Works for any domain; read-only.
| Parameter | Type | Description |
|---|---|---|
| domain * | string | The domain itself, e.g. example.no (Unicode such as blåbær.no is fine). Any registrar, any DNS provider. |
{
"name": "check_pointing",
"title": "What a domain points at today",
"description": "See what a domain points at today, from public DNS: its nameservers and DNS provider, the web target (apex and www records and the service they match), the mail provider (MX, SPF, DMARC) and the DNSSEC state. Use it before suggesting changes, to explain the current setup, or to check that new records are live. Works for any domain; read-only.",
"inputSchema": {
"type": "object",
"required": [
"domain"
],
"properties": {
"domain": {
"type": "string",
"description": "The domain itself, e.g. example.no (Unicode such as blåbær.no is fine). Any registrar, any DNS provider."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}Look up the BRC-100 identity key a domain handle (a domain, or name@domain) points at. The answer comes from the domain's _metanet TXT record in public DNS: identity_key is the 66-hex compressed public key or null, record is the DNS name it came from, and dnssec is validated (the resolver checked the DNSSEC signatures), unsigned or unknown. Every name@domain resolves to the domain's key. error is set when the domain has several identity records or one that cannot be read. This is the domain owner's claim; it does not prove the key holder agrees.
| Parameter | Type | Description |
|---|---|---|
| handle * | string | A domain (example.no) or name@domain (post@example.no). |
{
"name": "resolve_identity",
"title": "Which BRC-100 identity a domain points at",
"description": "Look up the BRC-100 identity key a domain handle (a domain, or name@domain) points at. The answer comes from the domain's _metanet TXT record in public DNS: identity_key is the 66-hex compressed public key or null, record is the DNS name it came from, and dnssec is validated (the resolver checked the DNSSEC signatures), unsigned or unknown. Every name@domain resolves to the domain's key. error is set when the domain has several identity records or one that cannot be read. This is the domain owner's claim; it does not prove the key holder agrees.",
"inputSchema": {
"type": "object",
"required": [
"handle"
],
"properties": {
"handle": {
"type": "string",
"description": "A domain (example.no) or name@domain (post@example.no)."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}pekt (pekt.no) is a Norwegian domain registrar run by Datamynt AS (domains via Realtime Register). It helps a user find a domain, own it and point it. Find: check_domain for one domain, suggest_domains for one name across popular extensions, requirements for what an extension needs, list_extensions for what pekt sells. Point (any domain, any DNS provider): list_services for the services pekt can point a domain at, dns_records for the exact records one service needs, check_pointing for what a domain points at today. Prices are NOK per year including 25 % Norwegian VAT (MVA), whole kr, the same numbers pekt.no shows; the first year and the renewal can differ. Every tool is read-only: nothing is reserved, bought or changed here. ALWAYS show the user the buy_url from a price result, because buying happens on pekt.no. environment OTE means a sandbox where the answers are not real.
Names, descriptions and schemas were written by the server and are shown as data.
Shared addresses on big platforms (Cloudflare, Vercel and the like) put unrelated servers together; those are marked shared_infrastructure. A match is a pivot, not a link between operators.