Apier MCP server
Commit Nov 11, 2026Provides AI agents with structured access to Norwegian company data, regulatory compliance, signing authority, and annual accounts.
Also known as PowerLaunch/apier-mcp, apier-mcp
- Stars
- 0
- Tools
- 19
- Downloads, 30 days
- —
- Latest version
- 2026.10.0
- Last commit
- Nov 11, 2026
- License
- MIT
What is Apier MCP?
Apier provides AI agents with structured access to Norwegian company data, regulatory compliance, signing authority, and annual accounts. It exposes 19 tools, such as get_company_summary, get_public_obligations, get_exchange_rate.
Summary generated from the project's README
About Apier MCP server
Apier provides AI agents with structured access to Norwegian corporate data and regulatory information. It allows users to resolve 9-digit organisation numbers against the Brønnøysund Register Centre to retrieve specific details such as coded signing rules, annual accounts, and company profiles. The server is designed for developers using MCP clients like Claude Desktop, Cursor, VS Code, or Zed.
Users can connect via a hosted HTTP endpoint or use the @apier-no/mcp npm proxy for local stdio connections. While discovery is keyless, protected tool calls require an API key provided via the APIER_API_KEY environment variable. The server includes a sandbox mode using synthetic fixtures, allowing developers to test tools like get_company_deadlines or get_company_authority using self-invented sandbox bearer tokens without needing a formal account.
What you can do with it
- 1Identify Norwegian company detailsAn agent can find the specific organisation number for a known company name.
- 2Verify corporate signing authorityA developer can retrieve the coded signing rules and legal authority for a specific organisation number.
- 3Monitor regulatory deadlinesAn AI can calculate upcoming filing deadlines for VAT, A-melding, and annual accounts.
- 4Access financial recordsAn agent can retrieve the most recent annual accounts for a Norwegian entity.
Written from the project's README. Every use case is checked against a quote from it.
How to install Apier MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Apier MCP in Claude Code
$ claude mcp add --transport http apier-mcp https://www.apier.no/api/mcpInstall Apier MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"apier-mcp": {
"url": "https://www.apier.no/api/mcp"
}
}
}Install Apier MCP in VS Code
.vscode/mcp.json
{
"servers": {
"apier-mcp": {
"type": "http",
"url": "https://www.apier.no/api/mcp"
}
}
}Install Apier MCP in VS Code CLI
$ code --add-mcp '{"name":"apier-mcp","type":"http","url":"https://www.apier.no/api/mcp"}'Install Apier MCP in Codex
$ codex mcp add apier-mcp --url https://www.apier.no/api/mcpInstall Apier MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.apier-mcp] url = "https://www.apier.no/api/mcp"
Install Apier MCP in Gemini CLI
$ gemini mcp add -s user --transport http apier-mcp https://www.apier.no/api/mcpInstall Apier MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"apier-mcp": {
"url": "https://www.apier.no/api/mcp",
"type": "http"
}
}
}Apier MCP tools 19
Detected from the READMEget_company_summaryget_public_obligationsget_exchange_rateget_company_profileget_company_contextget_company_deadlinesget_company_obligationsget_public_deadlinesexplain_compliance_errorsearch_companiesget_company_verificationget_company_authority
Show all 19 toolsShow fewer tools
get_company_accountsget_company_evidence_packlist_changesget_altinn_migration_guidanceget_pricingget_credit_balanceredeem_issuance_token
Configuration
APIER_API_KEY
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablepowerlaunch/apier-mcp is public and reachablegithub.com/powerlaunch/apier-mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-11github.com/powerlaunch/apier-mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model19 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 1639 msPass
README
View on GitHubApier MCP Server — Norwegian company data and compliance for AI agents
Apier is a hosted MCP (Model Context Protocol) server that gives AI agents structured access to Norwegian company data and regulatory compliance. It resolves any 9-digit organisasjonsnummer (organisation number) against Brønnøysundregistrene (the Brønnøysund Register Centre / Enhetsregisteret), returns the register's coded signing rules for the company (signaturrett and prokura, uninterpreted), reads annual accounts (årsregnskap) from Regnskapsregisteret and computes filing deadlines for MVA, A-melding and Årsregnskap. It reads open public registers only: it submits nothing to government and brokers no government access. This repository is the thin, hardened npm proxy (@apier-no/mcp) that connects local stdio MCP clients to the hosted server.
What you can ask
With this server connected, an AI agent can answer questions like:
- "What's the organisasjonsnummer for Equinor?" (search_companies)
- "What are the register's coded signing rules for org number 923 609 016, signaturrett and prokura?" (get_company_authority)
- "Is this company VAT-registered, and what regulatory obligations does it have?" (get_company_summary)
- "What filing deadlines is this company facing in the next six months?" (get_company_deadlines)
- "Show me the latest annual accounts (årsregnskap) for this company." (get_company_accounts)
- "What is the Altinn 3 equivalent of this old Altinn 2 role code?" (get_altinn_migration_guidance)
- "What's the current Norges Bank exchange rate for EUR to NOK?" (get_exchange_rate)
Tools
The hosted server at https://www.apier.no/api/mcp publishes its current tool list, with each tool's full description and required_scope, at the keyless discovery endpoint GET https://www.apier.no/api/mcp (and through tools/list). That endpoint is the source of truth; this README keeps no count. On 2026-11-06 it listed:
get_company_summaryget_public_obligationsget_exchange_rateget_company_profileget_company_contextget_company_deadlinesget_company_obligationsget_public_deadlinesexplain_compliance_errorsearch_companiesget_company_verificationget_company_authorityget_company_accountsget_company_evidence_packlist_changesget_altinn_migration_guidanceget_pricingget_credit_balanceredeem_issuance_token
Try without a key
Starting this proxy requires APIER_API_KEY (see Quickstart). The proxy forwards whatever bearer you give it as Authorization: Bearer … and never inspects the key's shape. Without a real key you still have two sandbox paths, both served from synthetic fixtures and never from a government register:
- Direct HTTP to the sandbox mirror under
/api/v1/sandbox/on apier.no. Every Category B company endpoint has a mirror there. It is not zero-auth: it expects a self-invented sandbox bearer,apier_sandbox_test_<suffix>(any suffix of 1–64 characters fromA-Za-z0-9_-), which the server recognises by its prefix and answers with fixtures — no signup and no key store behind it. A separate, truly zero-auth mirror lives under/api/v1/sandbox/public/for the single fixture org999999999. - The same sandbox bearer on the hosted MCP endpoint
https://www.apier.no/api/mcp. SendAuthorization: Bearer apier_sandbox_test_<suffix>and the fixture-backed company tools (get_company_context,get_company_obligations,get_company_deadlines,get_company_summary,get_company_verification,explain_compliance_error,get_company_authority,get_company_accounts) are routed to the sandbox mirror, with_meta.is_sandbox: trueon every result; the remaining tools answer exactly as they would without a key. Because this proxy forwards the bearer unchanged, settingAPIER_API_KEYto such a value lets a stdio client rehearse those tools against fixtures too.
List the canonical sandbox test data (no auth at all):
curl -sL https://apier.no/api/v1/sandbox/fixtures
Trimmed response — … marks omitted fields:
{"success":true,"data":{"schema_version":"1.0.0",
"reserved_test_orgs":[{"org_number":"999000001","name":"Sandbox AS","entity_type":"AS","data_tier":"tier_1", …}],
"realistic_orgs":[{"org_number":"818000006","name":"Fjellberg Regnskap AS","entity_type":"AS","data_tier":"tier_1_2"}, …],
"magic_scenarios":[{"org_number":"999660010","state":"konkurs","label":"Bankrupt (konkurs)"}, …], …}}
Verify the bankrupt fixture company with a self-invented bearer — any suffix of 1–64 chars from A-Za-z0-9_- after apier_sandbox_test_ works; here bash's $RANDOM supplies one. (This call goes to the www host directly: the apex→www 308 redirect makes curl drop the Authorization header.)
curl -s -H "Authorization: Bearer apier_sandbox_test_$RANDOM" https://www.apier.no/api/v1/sandbox/company/999660010/verify
Trimmed response — … marks omitted fields:
{"success":true,"data":{"org_number":"999660010","name":"Sandbox Konkurs AS",
"verification_status":"fail",
"signals":{"is_active":false,"not_bankrupt":false, …},
"summary":"Selskapet er ikke aktivt registrert i Enhetsregisteret.", …}}
Don't confuse the two prefixes: a real API key is apr_<tier>_… (apr_free_, apr_starter_, apr_pro_ or apr_ent_) and comes from signup via https://www.apier.no/docs/authentication, while apier_sandbox_test_ is self-generated and needs no signup. (Earlier README versions mentioned apier_live_ / apier_test_ keys; no key of that shape was ever issued.) GET /api/v1/sandbox/fixtures is the canonical machine-readable table of sandbox test data.
Quickstart
Hosted endpoint (streamable HTTP)
The fastest path — no install. Point any streamable-HTTP-capable MCP client at:
https://www.apier.no/api/mcp
Discovery is keyless: initialize, tools/list, resources and prompts all work without credentials, so an agent can explore the full catalogue before authenticating. An API key (Authorization: Bearer apr_<tier>_…) is needed only for protected tool calls. See https://www.apier.no/docs/authentication for how to get a key, then create one in the dashboard at https://www.apier.no/dashboard.
npx stdio proxy (@apier-no/mcp)
For stdio-only clients, this package wraps mcp-remote, reads APIER_API_KEY from your environment, removes it from the spawned child's environment, redacts it from stderr, and hands the bearer value over out-of-band so it never appears on the child's command line — see SECURITY.md.
mcp-remote moved from geelen/mcp-remote to punkpeye/mcp-remote; the npm package name is unchanged, and 0.8.1 is published with SLSA provenance attestations.
Published as @apier-no/mcp. The @apier scope was unavailable, so this package ships under the @apier-no scope.
Claude Desktop / Cursor (claude_desktop_config.json / ~/.cursor/mcp.json):
{
"mcpServers": {
"apier": {
"command": "npx",
"args": ["-y", "@apier-no/mcp"],
"env": { "APIER_API_KEY": "apr_<tier>_<your_key_here>" }
}
}
}
VS Code (.vscode/mcp.json):
{
"servers": {
"apier": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@apier-no/mcp"],
"env": { "APIER_API_KEY": "apr_<tier>_<your_key_here>" }
}
}
}
Zed (settings.json):
{
"context_servers": {
"apier": {
"source": "custom",
"command": "npx",
"args": ["-y", "@apier-no/mcp"],
"env": { "APIER_API_KEY": "apr_<tier>_<your_key_here>" }
}
}
}
Ready-to-paste config files for each client live in examples/.
Configuration
| Variable | Required | Default |
|---|---|---|
APIER_API_KEY |
yes | — |
--endpoint <url> |
no | https://www.apier.no/api/mcp |
MCP_REMOTE_CONFIG_DIR |
no | ~/.mcp-auth |
Security
APIER_API_KEYis read by the parent process and scrubbed from the spawned child's environment, and stderr is passed through a redactor that stripsBearer …, bareapr_<tier>_…keys andapr_issue_…key-issuance tokens, the legacyapier_(live|test)_…shape,ghp_…, andAuthorization:substrings.- The key never appears in the child's command line. The
--headerargument carries only the placeholderAuthorization:${APIER_MCP_AUTH_HEADER}; the bearer value is passed out-of-band in that variable and expanded bymcp-remoteat request time. Command lines are world-readable on Linux (/proc/<pid>/cmdline), process environments are not — so this is no longer readable by other local users (#33, fixed in 1.2.0). An attacker already running as you can still read the environment — see SECURITY.md. - Non-https endpoints are rejected before spawn;
mcp-remoteis exact-pinned and releases are published with npm provenance via GitHub Actions Trusted Publishing (OIDC). - Treat client config files (
claude_desktop_config.json,.cursor/mcp.json, …) like.envfiles — never commit them with a real key.
Full threat model and disclosure policy: SECURITY.md.
Documentation
- MCP server docs: https://www.apier.no/docs/mcp
- Apier platform docs: https://apier.no/docs
License
MIT
Apier MCP questions
How do I add Apier MCP to Claude Code?
Run claude mcp add --transport http apier-mcp https://www.apier.no/api/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Apier MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Apier MCP provide?
It exposes 19 tools, including get_company_summary, get_public_obligations, get_exchange_rate, get_company_profile, get_company_context.
Does this server submit data to the government?
No, the server only reads open public registers and does not submit any information to government agencies or brokers access.
How do I test the server with fake data?
You can use a self-generated sandbox bearer starting with 'apier_sandbox_test_' followed by any suffix to access fixture-backed company tools.