NBIM MCP Server
MCP server for querying data from Norway's Government Pension Fund Global — the world's largest sovereign wealth fund.
What it does
Provides 6 tools for querying fund data through the Model Context Protocol:
| Tool | Description |
|---|---|
nbim_fund_value |
Current fund value and asset allocation breakdown |
nbim_holdings_search |
Search equity holdings by company, country, or sector |
nbim_top_holdings |
Top N holdings by market value with filters |
nbim_country_allocation |
Geographic allocation across 70+ countries |
nbim_returns |
Annual and cumulative returns since 1998 |
nbim_exclusions |
Companies excluded or under observation |
Install
pip install mcp-nbim
Or with uvx:
uvx mcp-nbim
Quick start
# Run with streamable HTTP (port 8008)
mcp-nbim
# Run with stdio (for Claude Desktop, Claude Code)
mcp-nbim --stdio
Claude Desktop
Add to claude_desktop_config.json:
{
"mcpServers": {
"nbim": {
"command": "uvx",
"args": ["mcp-nbim", "--stdio"]
}
}
}
Or if installed with pip:
{
"mcpServers": {
"nbim": {
"command": "mcp-nbim",
"args": ["--stdio"]
}
}
}
Claude Code
claude mcp add nbim -- uvx mcp-nbim --stdio
Docker
docker compose up
Example queries
- "What is the fund worth today?" →
nbim_fund_value() - "Top 10 holdings in Japan" →
nbim_top_holdings(n=10, country='JP') - "Does the fund own Tesla?" →
nbim_holdings_search(query='Tesla') - "How has the US allocation changed?" → compare
nbim_country_allocation()across years - "Which companies are excluded for coal?" →
nbim_exclusions(criterion='coal') - "Fund performance in 2008" →
nbim_returns(start_year=2008, end_year=2008)
Data sources
- Holdings & fund value: NBIM Investment Data API (JSON, no auth required)
- Returns: Scraped from nbim.no/en/the-fund/returns/ with hardcoded fallback
- Exclusions: Scraped from nbim.no exclusion list
Holdings data updates semi-annually and covers equities (~9,000 companies). Historical data goes back to 1998. No authentication required.
Related
- Norges Bank MCP — Exchange rates, policy rate, yield curves
- Built by Gervi Labs
Metadata
Release files for mcp-nbim 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mcp_nbim-0.1.0.tar.gz | 14.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_nbim-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 30.4 kB
Release files / mcp_nbim-0.1.0.tar.gz
| Download URL | mcp_nbim-0.1.0.tar.gz |
|---|---|
| Size | 14.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
72c39a99c74b2bbe1183e45b4372d5f32a19d004ff29eb573d70b7999e563b54
|
|
BLAKE2b-256 checksum How to use checksums |
8b0df50d99a8fca3d1e4f00bab3d0d9ae3c2a32ec923d5080b41a7403de3baca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Release files / mcp_nbim-0.1.0-py3-none-any.whl
| Download URL | mcp_nbim-0.1.0-py3-none-any.whl |
|---|---|
| Size | 15.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d0e99b1a7908df6dce40a806795ed232ba0f7e70285ebb4efedbd0b0e6f651d3
|
|
BLAKE2b-256 checksum How to use checksums |
084ec3e1725d5481720cf175ca6890b0f07565794ceac7d675b278c69dfbea7e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.2
|
Security for mcp-nbim 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.