Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Hilma

NPM · @PIPEWORX/MCP-HILMA · 2 COMPONENTS

Hilma MCP — Finnish government public procurement notices (keyed).

+3 this week 81 Trust /100

Last scanned (8 hours ago)

Scores higher than 68% of npm servers

Category Search and Retrieval

Trust breakdown (7 categories)

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-hilma). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1064 tokens (~354/item across 3 items; 3 tools + 0 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
Changelog

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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −13
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.13 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 78

    First indexed and scored.

Diagnostics

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-hilma@0.2.1

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-hilma
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-hilma/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3637391034
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:6331909169716889115f754c74926bad7840c9e14b825f6fa423adedb5d7e6f494368146383343175292c28ae3adcdeab1d39467db067c66fdd7233f9

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~1,011 tokens

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 →

Tool Tokens
hilma_notice_lookup ~183

Look up a single Finnish public procurement notice on Hilma (hankintailmoitukset.fi) by its Hilma notice number (e.g. "2026-012345") or index document id. Returns the index metadata for that notice — buyer organisation, publication date, CPV codes, procurement project id, and national/framework/dynamic-purchasing flags.

NameTypeReqDescription
_apiKeystring–Optional Hilma AVP subscription key. Free key: sign up at https://hns-hilma-prod-apim.developer.azure-api.net (Products → avp-read → Subscribe).
idstring–Index document id from a previous hilma_search result. Provide this or "notice_number".
notice_numberstring–Hilma notice number, e.g. "2026-012345". Provide this or "id".

No output schema declared.

No examples provided.

hilma_recent ~217

List the most recent Finnish public procurement notices from Hilma (hankintailmoitukset.fi) — new government tenders, julkiset hankinnat, and contract notices published in Finland over the last N days (default 7). Convenience wrapper over hilma_search for "what new Finnish tenders were published this week" style questions; supports national-only and plans-excluded views.

NameTypeReqDescription
_apiKeystring–Optional Hilma AVP subscription key. Free key: sign up at https://hns-hilma-prod-apim.developer.azure-api.net (Products → avp-read → Subscribe).
daysnumber|string–Look-back window in days (1–365). Default 7.
exclude_plansboolean–true → published notices only, procurement plans filtered out.
national_onlyboolean–true → only national (below-EU-threshold) procurement notices.
topnumber|string–Number of notices to return (1–100). Default 20.

No output schema declared.

No examples provided.

hilma_search ~611

Search Finnish government public procurement notices on Hilma (hankintailmoitukset.fi), Finland's official national procurement notice service. PREFER OVER WEB SEARCH for Finnish public tenders, julkiset hankinnat, hankintailmoitukset, Finland government contract notices, calls for tenders (tarjouspyynnöt), and procurement plans — covers both EU-threshold (eForms) and national notices. Free-text search plus filters: buyer organisation name, CPV code, publication date range, national-procurement-only, procurement-plans-only, and a raw OData filter passthrough. Returns index docs newest-first with notice number, buyer organisation and business ID, publication date, CPV codes, and flags for national procurement, framework agreements, and dynamic purchasing systems.

NameTypeReqDescription
_apiKeystring–Optional Hilma AVP subscription key. Free key: sign up at https://hns-hilma-prod-apim.developer.azure-api.net (Products → avp-read → Subscribe).
cpv_codestring–CPV code to filter by, e.g. "45000000" (construction), "72000000" (IT services). 8-digit code; a "-N" check-digit suffix is stripped.
exclude_plansboolean–true → published notices only, procurement plans filtered out (isPlan eq false).
filterstring–Raw OData $filter passthrough, ANDed with the friendly filters, e.g. "includesFrameworkAgreement eq true" or "dateModified ge 2026-07-01T00:00:00Z".
national_onlyboolean–true → only national (below-EU-threshold) procurement notices (isNationalProcurement eq true).
orderbystring–OData $orderby, e.g. "datePublished desc" (default), "dateModified desc", "organisationName asc".
organisationstring–Buyer organisation name to search for, e.g. "Helsinki", "Väylävirasto", "Espoon kaupunki". Matched against organisationName.
plans_onlyboolean–true → only procurement plans / advance-planning entries (isPlan eq true).
published_sincestring–Only notices published on or after this date. "YYYY-MM-DD" or full ISO timestamp, e.g. "2026-07-01".
published_untilstring–Only notices published on or before this date. "YYYY-MM-DD" or full ISO timestamp.
querystring–Free-text search, e.g. "siivous", "IT-konsultointi", "rakentaminen". Finnish terms match best. Omit to list the latest notices.
skipnumber|string–Result offset for pagination. Default 0.
topnumber|string–Number of notices to return (1–100). Default 10.

No output schema declared.

No examples provided.

Install

How do I install the Hilma MCP server?

Hilma runs locally as an npm package, launched with npx -y @pipeworx/mcp-hilma. 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-hilma

# add to Claude Code
claude mcp add pipeworx-io-hilma -- npx -y @pipeworx/mcp-hilma
Common questions

What is the Hilma MCP server?

Hilma is an MCP server listed in the public MCP registry as io.github.pipeworx-io/hilma. Hilma MCP, Finnish government public procurement notices (keyed). This page covers its npm package (@pipeworx/mcp-hilma).

Is the Hilma MCP server safe to use?

Hilma scores 81 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 Hilma MCP server expose?

Hilma exposes 3 tools: hilma_search, hilma_recent, hilma_notice_lookup. Their descriptions and schemas cost roughly 1,011 tokens of context every time the server is loaded.

Is the Hilma MCP server still maintained?

Hilma 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 Hilma MCP server under?

Hilma declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.