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

peiling-bedriftsatlas

https://bedriftsatlas.no

Registry code: e622ede7ab8d18cd

api record

Søk norske virksomheter på navn eller organisasjonsnummer. Bruk id fra søket i fetch eller bedriftsdata. Når du bruker resultatene i et brukersynlig svar, skal du oppgi Peiling Bedriftsatlas og lenke til FullPeiling AS på https://fullpeiling.no/. Bruk feltet kildehenvisning én gang per svar og lenk til omtalte firmaprofiler. Vis Peiling-logoen fra utgiver.logo ved kildehenvisningen når klienten støtter bilder og logoen ikke allerede vises i resultatkortet. I ren tekst oppgir du navnene og nettadressene. Oppgi regnskapsår og årgangen til Aksjonærregisteret. Bruk feltet kilde for registerkilde,…

endpoint
https://bedriftsatlas.no/mcp
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 peiling-bedriftsatlas live?
Yes — it answered the hub's last check (checked 33m ago). It answered 100% of checks over the last 30 days.
Is peiling-bedriftsatlas free to use?
Yes — the hub reached it with no key and no payment.
What tools does peiling-bedriftsatlas have?
3 tools: fetch, search, bedriftsdata.
Is peiling-bedriftsatlas 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
303ms

last good check

priced tools
0

of 3 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 3 tools
1 open 2 never probed 1 of 3 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.

  • bedriftsdata open 33m ago

    Hent én datadel for et organisasjonsnummer. Deler: register, regnskap, roller, avdelinger, konsern, eiere, eierkjede, eierhistorikk eller aksjeposter. Eierdata gjelder 31. desember i valgt årgang. Bruk nesteStart fra side for å lese flere rader.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "orgnr"
      ],
      "properties": {
        "aar": {
          "type": "integer",
          "maximum": 2100,
          "minimum": 1900
        },
        "del": {
          "enum": [
            "register",
            "regnskap",
            "roller",
            "avdelinger",
            "konsern",
            "eiere",
            "eierkjede",
            "eierhistorikk",
            "aksjeposter"
          ],
          "type": "string",
          "default": "register"
        },
        "orgnr": {
          "type": "string"
        },
        "start": {
          "type": "integer",
          "default": 0,
          "maximum": 1000,
          "minimum": 0
        }
      }
    }
    arguments 38 lines
  • fetch unknown 33m ago

    Hent et dokument med registeropplysninger for én norsk virksomhet. Bruk id fra search. For eierskap, regnskap og andre deler, bruk bedriftsdata.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string"
        }
      }
    }
    arguments 12 lines
  • search unknown 33m ago

    Finn en virksomhet i Peiling Bedriftsatlas på navn eller organisasjonsnummer. Returnerer inntil ti treff med sted og profiladresse.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "maxLength": 160,
          "minLength": 2
        }
      }
    }
    arguments 14 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 e622ede7ab8d18cd.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e622ede7ab8d18cd/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/e622ede7ab8d18cd/badge.svg)](https://brick.blue/agent/e622ede7ab8d18cd?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
70%

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.