Storting No
NPM · @PIPEWORX/MCP-STORTING-NO · 2 COMPONENTS
Stortinget (Norwegian Parliament) open data MCP — data.stortinget.no.
Available components
Last scanned (13 hours ago)
Scores higher than 72% of npm servers
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-storting-no). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 571 tokens (~81/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 82
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-storting-no@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-storting-no |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-storting-no/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560322765 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:1c15c23878ab0fc558de01a5fea54a0d486dbd1785ba9a29ec5be3a8877032039a68d19b16de1bde4abc7b149814790705a20e88b86ae3d82a37389a7 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
export ~124
Generic fallback to any data.stortinget.no/eksport resource. Use for endpoints without a dedicated tool, e.g. resource "moter" (meetings), "komiteer" (committees) with params {sesjonid}. ?format=json is added automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| params | object | – | Query params, e.g. {"sesjonid": "2023-2024"}. Do not include format. |
| resource | string | yes | Endpoint name under /eksport, e.g. "moter", "komiteer", "sesjoner". |
No output schema declared.
No examples provided.
get_cases ~73
List parliamentary cases/bills ("saker") for a session. Returns saker_liste with numeric case ids (sakid), titles, topics (emne_liste) and status.
| Name | Type | Req | Description |
|---|---|---|---|
| sesjonid | string | yes | Session id, e.g. "2023-2024". Get valid ids from get_sessions. |
No output schema declared.
No examples provided.
get_parties ~53
List all political parties ("partier") known to Stortinget. Returns id (e.g. "A", "H", "FrP"), navn (full name), and representert_parti (currently represented).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_representatives ~80
List members of parliament (MPs, "representanter") for a 4-year electoral period. Returns fornavn (first), etternavn (last), parti (party), fylke (county), kjoenn (gender).
| Name | Type | Req | Description |
|---|---|---|---|
| stortingsperiodeid | string | yes | Electoral period id, e.g. "2021-2025". |
No output schema declared.
No examples provided.
get_sessions ~52
List Norwegian Parliament (Stortinget) sessions. A session ("sesjon") runs ~Oct–Sep with an id like "2023-2024". Use the returned ids as sesjonid for other tools.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_vote_result ~66
Per-MP results ("voteringsresultat") for one vote: how each representative voted (for/against/absent). Pass a votering id from get_votes.
| Name | Type | Req | Description |
|---|---|---|---|
| voteringid | string | yes | Numeric vote id (voteringid) from get_votes. |
No output schema declared.
No examples provided.
get_votes ~69
List the votes ("voteringer") held on a single case. Returns sak_votering_liste; each has a votering id. Pass that id to get_vote_result for per-MP breakdown.
| Name | Type | Req | Description |
|---|---|---|---|
| sakid | string | yes | Numeric case id (sakid) from get_cases. |
No output schema declared.
No examples provided.
How do I install the Storting No MCP server?
Storting No runs locally as an npm package, launched with npx -y @pipeworx/mcp-storting-no. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-storting-no
claude mcp add pipeworx-io-storting-no -- npx -y @pipeworx/mcp-storting-no
What is the Storting No MCP server?
Storting No is an MCP server listed in the public MCP registry as io.github.pipeworx-io/storting-no. Stortinget (Norwegian Parliament) open data MCP, data.stortinget.no. This page covers its npm package (@pipeworx/mcp-storting-no).
Is the Storting No MCP server safe to use?
Storting No scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Storting No MCP server expose?
Storting No exposes 7 tools: get_sessions, get_cases, get_representatives, get_parties, get_votes, and 2 more. Their descriptions and schemas cost roughly 517 tokens of context every time the server is loaded.
Is the Storting No MCP server still maintained?
Storting No is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Storting No MCP server under?
Storting No declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.