_ registry / mcp streamable-http · checked 59m ago

pekt-public

https://pekt.no

Registry code: a9c922e1674db5ce

api record

pekt (pekt.no) is a Norwegian domain service run by Datamynt AS (domains via Realtime Register). Use these tools to tell a user whether a domain name is available and what it costs: 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. Prices are NOK per year including 25 % Norwegian VAT (MVA), whole kr, and are the same numbers pekt.no shows; the first year and the renewal can differ. The tools are read-only: nothing is reserved or bought here. ALWAYS show the user the buy_url from…

endpoint
https://pekt.no/mcp/public
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is pekt-public live?
Yes — it answered the hub's last check (checked 59m ago). It answered 100% of checks over the last 30 days.
Is pekt-public free to use?
Yes — the hub reached it with no key and no payment.
What tools does pekt-public have?
4 tools: suggest_domains, check_domain, requirements, list_extensions.
Is pekt-public safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
124ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_extensions open 59m ago

    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.

    mcp-tool

    {
      "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
    }
    arguments 20 lines
  • suggest_domains unknown never probed

    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.

    mcp-tool

    {
      "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
    }
    arguments 19 lines
  • check_domain unknown 59m ago

    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.

    mcp-tool

    {
      "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
    }
    arguments 13 lines
  • requirements unknown 59m ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "tld"
      ],
      "properties": {
        "tld": {
          "type": "string",
          "description": "The extension without a dot, e.g. no, com or eu."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id a9c922e1674db5ce.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/a9c922e1674db5ce/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/a9c922e1674db5ce/badge.svg)](https://brick.blue/agent/a9c922e1674db5ce?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.