Apiverket
NPM · APIVERKET-MCP-SERVER · SCANNED AUG 3
Query Swedish public data: companies, SCB statistics, weather, transport, and more.
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 72 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 755 tokens (~251/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · apiverket-mcp-server
claude mcp add vinvuk-apiverket-mcp -- npx -y apiverket-mcp-server
codex mcp add vinvuk-apiverket-mcp -- npx -y apiverket-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vinvuk-apiverket-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"apiverket-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add vinvuk-apiverket-mcp --command npx --arg -y --arg apiverket-mcp-server
mcp_servers:
vinvuk-apiverket-mcp:
command: "npx"
args: ["-y", "apiverket-mcp-server"] {
"mcpServers": {
"vinvuk-apiverket-mcp": {
"command": "npx",
"args": [
"-y",
"apiverket-mcp-server"
]
}
}
} 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.
- 2 Aug 26 +45
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Schema quality: unverified → excellent ▲ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: MIT functional
- 1 Aug 26 +19
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 31 Jul 26 −46
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 51
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
govdata_discover Discover Apiverket Endpoints ~244
Search and browse available Swedish government data endpoints in the Apiverket API. Use this tool to find the right endpoint before calling govdata_query. The API covers 139 endpoints across 16 categories including weather, transport, economy, health, environment, parliament, police, education, and more. Args: - query (string, optional): Keyword to search across endpoint names, descriptions, and paths - category (string, optional): Filter by category name When called with no arguments, returns all available categories with endpoint counts. Examples: - Find weather endpoints: query="weather" - Browse transport category: category="Transport" - Find pension info: query="pension" - List all categories: (no arguments) Returns: Matching endpoints with their paths, parameters, and descriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | — | Filter by category name (e.g. 'Weather & Climate', 'Economy & Finance'). Use without query to browse a category. |
| query | string | — | Search keyword to find relevant endpoints (e.g. 'weather', 'train', 'population', 'pension'). Leave empty to list all categories. |
No output schema declared.
No examples provided.
govdata_query Query Apiverket API ~490
Call any Apiverket API endpoint to retrieve Swedish government data. Use govdata_discover first to find the right endpoint path and required parameters. Then call this tool with the endpoint path and any path/query parameters. Args: - endpoint (string, required): The API path (e.g. "/v1/weather/{city}") - path_params (object, optional): Values for path parameters like {city}, {code}, {id} - query_params (object, optional): Query string parameters (q, limit, offset, lat, lon, etc.) Examples: - Current weather in Stockholm: endpoint="/v1/weather/{city}", path_params={"city": "stockholm"} - Search jobs: endpoint="/v1/jobs/search", query_params={"q": "developer", "limit": 5} - Train departures from Stockholm Central: endpoint="/v1/transport/trains/{station}", path_params={"station": "Cst"} - Exchange rates: endpoint="/v1/rates" - Population by municipality: endpoint="/v1/population/{municipalityCode}", path_params={"municipalityCode": "0180"} - Police events in Stockholm: endpoint="/v1/police/events", query_params={"location": "Stockholm", "limit": 10} - Find EV chargers near a location: endpoint="/v1/infrastructure/ev-chargers", query_params={"lat": 59.33, "lon": 18.07} Returns: The API response as JSON, containing a "meta" envelope with request info and a "data" object with the actual data. Error handling: - Returns clear error messages if the API is unreachable, the endpoint doesn't exist, or parameters are invalid - Large responses are automatically truncated with pagination guidance
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | yes | API endpoint path from the discover tool (e.g. '/v1/weather/{city}', '/v1/rates', '/v1/police/events') |
| path_params | object | — | Path parameter values to substitute in the endpoint URL. Example: { "city": "stockholm" } for /v1/weather/{city} |
| query_params | object | — | Query string parameters. Example: { "q": "developer", "limit": 5 } for search endpoints |
No output schema declared.
No examples provided.