Every finance team has this file: a supplier column of organisasjonsnummer (orgnr, org.nr) typed in by hand.
Some are wrong. checks them against Brønnøysundregistrene / Enhetsregisteret (brreg) and fills in the rest.
The prompt Here's .
Check every org.nr, drop the ones that aren't real companies, and add legal form, status, VAT number and city. : Step 1 — on every row It does no network call, so run it on all six before spending a lookup on any.
Two rows are interesting: is the dedupe key — the spaced row and row 1 are the same company.
And is a plain answer, not an exception: MOD11 catches the transposed digit in .
That's one lookup saved and one bad supplier caught for free.
Step 2 — on the survivors Five rows, five calls, ~60 lines of Python (): Three different failures, three different fixes, and the column keeps them apart: — never a valid number.
Someone mistyped it.
Search by name. — passes MOD11, but raises .
Well-formed is not the same as real; only the network call can tell you. — a real, active entity that is simply not in Merverdiavgiftsregisteret.
If it sends you an invoice with MVA on it, that's the finding.
One column deserves a note. 's is blank because the API returned — the register publishes no figure. is not ; the report carries so you can tell "unknown" from "zero" instead of writing a false headcount into your spreadsheet.
Source: Enhetsregisteret, NLOD 2.0.
Same JSON over MCP and REST.
Repo: https://github.com/foretak/registry-mcp