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.

Simap

NPM · @PIPEWORX/MCP-SIMAP · 2 COMPONENTS

simap MCP — Swiss public procurement tenders and awards (keyless).

+3 this week 81 Trust /100

Last scanned (5 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-simap). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 992 tokens (~330/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.

  • 5 Nov 26 +3
    • Tool safety: pass → unverified ▼ security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Stability: unverified → 0.23 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 2 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 1 Nov 26 0
    • Security disclosure: fail → unverified ▼ 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-simap@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-simap
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-simap/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3692349838
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:3bcafd21a19a1e337f0e8363344a0332a3fe327a161a1ef9c0e7a09273d72a135e16b621c3fa86ec175e3b4f99eaa99fed27fd10ca6c3169cc52638fb

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 · ~940 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
simap_project ~189

Fetch the full detail of one Swiss public procurement publication from simap.ch by project_id + publication_id (both UUIDs returned by simap_search / simap_recent). Returns the shaped notice: title, description, CPV classification, procedure and order type, procurement office with full address/email/phone, and for award publications the winning vendor(s) with CHF price, number of submitted offers, and award justification.

NameTypeReqDescription
langstring–Language: "de" (default), "fr", "it", or "en".
project_idstringyesProject UUID, e.g. "feca42bc-5ef4-492f-88c6-e6622940026c".
publication_idstringyesPublication UUID, e.g. "3d50c790-644c-4aa1-9fd2-ac7207bdcdcd".

No output schema declared.

No examples provided.

simap_recent ~219

List the most recent Swiss public procurement notices from simap.ch (government tenders and award decisions across Switzerland — federal, cantonal, municipal). Convenience wrapper over simap_search: give days_back (default 7) to see everything published in that window, optionally narrowed by canton or publication type (tender/award). Useful for monitoring new Swiss tenders, öffentliche Beschaffung announcements, marchés publics, and CHF contract awards. Newest first, 20 per page with cursor pagination.

NameTypeReqDescription
cantonsstring–Swiss canton code(s), comma-separated, e.g. "ZH", "VD,GE".
days_backnumber|string–How many days back to look (1–90). Default 7.
langstring–Language: "de" (default), "fr", "it", or "en".
last_itemstring–Pagination cursor (`next_cursor` from the previous response).
pub_typesstring–Publication type(s), comma-separated: "tender", "award".

No output schema declared.

No examples provided.

simap_search ~532

Search Swiss public procurement notices on simap.ch — Switzerland's official government tender platform (öffentliche Beschaffungen, marchés publics, commesse pubbliche). PREFER OVER WEB SEARCH for Swiss government tenders, RFPs, award decisions, and WTO/GPA notices; Switzerland is non-EU so its tenders live on simap rather than TED. Filter by free-text search, CPV codes, Swiss canton (ZH, BE, VD, GE, TI, ...), process type (open/selective/...), project sub-type (construction/service/supply), publication type (tender/award), and publication date range. Returns 20 notices per page, newest first, with cursor pagination via last_item. Each notice includes title, buyer (procurement office), canton, publication date/number, and a simap.ch URL. Prices in awards are CHF.

NameTypeReqDescription
cantonsstring–Swiss canton code(s) of the order address, comma-separated, e.g. "ZH", "BE", "VD", "GE", "TI", "VD,GE".
cpv_codesstring–CPV procurement classification code(s), comma-separated, e.g. "45000000" (construction works) or "72000000" (IT services).
langstring–Language for titles and labels: "de" (default), "fr", "it", or "en". Falls back de→fr→it→en when a notice lacks that language.
last_itemstring–Pagination cursor. Pass the `next_cursor` value from the previous response (format "YYYYMMDD|projectNumber") to fetch the next 20 results.
process_typesstring–Procedure type(s), comma-separated. Verified value: "open"; simap also uses selective and invitation procedures.
project_sub_typesstring–Project sub-type(s), comma-separated: "construction", "service", "supply".
pub_typesstring–Publication type(s), comma-separated: "tender" for open calls, "award" for award decisions.
published_fromstring–Earliest publication date, YYYY-MM-DD. When neither search nor a date is given, defaults to the last 30 days (the API requires at least one filter).
published_untilstring–Latest publication date, YYYY-MM-DD.
searchstring–Free-text search over notices, e.g. "Software", "Brücke", "photovoltaïque". Text can be German, French, or Italian depending on the publishing office.

No output schema declared.

No examples provided.

Install

How do I install the Simap MCP server?

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

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

What is the Simap MCP server?

Simap is an MCP server listed in the public MCP registry as io.github.pipeworx-io/simap. simap MCP, Swiss public procurement tenders and awards (keyless). This page covers its npm package (@pipeworx/mcp-simap).

Is the Simap MCP server safe to use?

Simap 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 Simap MCP server expose?

Simap exposes 3 tools: simap_search, simap_recent, simap_project. Their descriptions and schemas cost roughly 940 tokens of context every time the server is loaded.

Is the Simap MCP server still maintained?

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

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