nordic-registry

This Nordics Registry MCP Server provides read-only access to company information from four registries (Norway, Denmark, Finland, and Sweden) through a single MCP interface. It exposes 23 tools that allow you to search by name, retrieve detailed company records, inspect governance and signing authority, and fetch Swedish annual reports. The server is designed to be used with MCP clients or AI copilots that can issue the standard MCP queries and parse the structured responses. Typical workflows include checking whether a company is active, extracting board members and signatories, and performing batch validations of multiple org numbers across registries.

Prerequisites:

• Docker installed and running on your host
• Access to the Docker image olgasafonova/nordic-registry-mcp-server (or build your own image from the repository)

Installation steps:

1. Pull the image: docker pull olgasafonova/nordic-registry-mcp-server

2. Run the MCP server container: docker run -d --name nordic-registry-mcp -p 8080:8080 olgasafonova/nordic-registry-mcp-server

3. Verify the server is responding (replace localhost with your host as needed): curl http://localhost:8080/health

4. Configure your MCP client to connect to the server at the exposed endpoint (e.g., http://localhost:8080/mcp).

Notes:

• If you need to pass environment variables (e.g., API keys for optional registries or rate limits), use docker run -e VAR_NAME=value ...
• You can also deploy this server in a Kubernetes cluster or via your preferred container orchestration.

Tips:

• The server is read-only and relies on public registries; no data caching beyond session scope is performed.
• If Sweden (Bolagsverket) OAuth2 credentials are required for certain datasets, obtain and configure the credentials via environment variables as described by the container's documentation.
• Ensure network access to external registries from your deployment environment; some endpoints may require authentication or have rate limits.
• For large batch lookups, consider using the MCP client’s batch endpoints and pagination as documented by the MCP server.

Common issues:

• Container fails to start due to port conflicts: ensure the exposed port is free or change the host port mapping.
• Missing credentials for Swedish data: supply OAuth2 tokens or client credentials per the provider’s instructions.
• DNS or network DNS resolution issues when the MCP client attempts to reach the server: verify network routing and firewall settings.