Germany Tenders
NPM · @PIPEWORX/MCP-GERMANY-TENDERS · 2 COMPONENTS
Germany public procurement MCP — official German government tenders (keyless).
Available components
Last scanned (1 hour ago)
Scores higher than 72% of npm servers
Category Finance and Payments
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-germany-tenders). 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 Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 867 tokens (~289/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
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 78
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-germany-tenders@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-germany-tenders |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-germany-tenders/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637324140 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d91153909aeb5bb62b0cab1b96eb8194983bd1abfee17104a416d5d7dd2fbb4545ff41e28398cfd38e396f47bd152f4abd545a513e14d633a1efc4281 |
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 →
germany_buyer_spend_history ~257
Procurement spend history for a GERMAN government buyer (Vergabestelle) — e.g. a city, a ministry, a university hospital — across German OCDS tender notices (oeffentlichevergabe.de, CC0). Matches the buyer name (case-insensitive substring, e.g. "Universitätsklinikum Halle", "Stadt Angermünde"). Returns process count, how many of those disclosed a EUR value (German notices below the EU publication threshold frequently omit contract value — this is reported, not hidden), total disclosed spend in EUR, top procurement categories, and a sample of recent processes. Spans up to 12+ months (see data_as_of in the response for the current coverage).
| Name | Type | Req | Description |
|---|---|---|---|
| buyer | string | yes | Buyer name, partial match, e.g. "Universitätsklinikum Halle", "Stadt Angermünde", "Ministerium". |
| date_from | string | – | Earliest publish date, YYYY-MM-DD. Omit for no lower bound. |
| date_to | string | – | Latest publish date, YYYY-MM-DD. Omit for no upper bound. |
| sample_limit | number|string | – | How many example processes to include (default 10, max 25). |
No output schema declared.
No examples provided.
germany_search_tenders ~316
Search official GERMAN government public-procurement tenders (Öffentliche Vergabe / Ausschreibungen) from the federal Bekanntmachungsservice open-data feed (oeffentlichevergabe.de), Open Contracting Data Standard (OCDS, CC0). Returns each notice shaped: ocid, title, buyer/Vergabestelle, contract value in EUR, procurement category, CPV code, procurement method, submission deadline, and publish date. Filter by publish-date range and/or a keyword (matched against title, description, buyer, and CPV description — German text). Defaults to the most recent days if no dates given. Can answer wide date ranges (months) as well as very recent days. Data covers Germany only.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Earliest PUBLISH date to include, YYYY-MM-DD. Defaults to ~30 days ago. A very old date may only partly be covered; see the response for how much of the range came back. |
| date_to | string | – | Latest PUBLISH date to include, YYYY-MM-DD. Defaults to today. |
| limit | number|string | – | Max number of tenders to return (default 25, max 100). Results are newest-first. |
| query | string | – | Optional keyword to filter on (case-insensitive substring match against title, description, buyer name, and CPV description — German). Omit to return all notices in the date range. E.g. "Bauarbeiten"… |
No output schema declared.
No examples provided.
germany_supplier_win_history ~239
Contract-win history for a GERMAN supplier/contractor (e.g. "Uniola AG", "System Strobel GmbH") across German OCDS tender notices (oeffentlichevergabe.de, CC0) — which buyers they won work from, award dates, and disclosed EUR values where published. COVERAGE IS GENUINELY PARTIAL: the winning supplier and award value are disclosed on only a small minority of German notices (below-threshold contracts routinely omit both) — the response reports won_count vs. value_disclosed_count so that gap is visible rather than read as "no data". See data_as_of in the response for the current coverage.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Earliest publish date, YYYY-MM-DD. Omit for no lower bound. |
| date_to | string | – | Latest publish date, YYYY-MM-DD. Omit for no upper bound. |
| sample_limit | number|string | – | How many example awards to include (default 10, max 25). |
| supplier | string | yes | Supplier/company name, partial match, e.g. "Uniola AG", "System Strobel". |
No output schema declared.
No examples provided.
How do I install the Germany Tenders MCP server?
Germany Tenders runs locally as an npm package, launched with npx -y @pipeworx/mcp-germany-tenders. 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-germany-tenders
claude mcp add pipeworx-io-germany-tenders -- npx -y @pipeworx/mcp-germany-tenders
What is the Germany Tenders MCP server?
Germany Tenders is an MCP server listed in the public MCP registry as io.github.pipeworx-io/germany-tenders. Germany public procurement MCP, official German government tenders (keyless). This page covers its npm package (@pipeworx/mcp-germany-tenders).
Is the Germany Tenders MCP server safe to use?
Germany Tenders 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 Germany Tenders MCP server expose?
Germany Tenders exposes 3 tools: germany_search_tenders, germany_buyer_spend_history, germany_supplier_win_history. Their descriptions and schemas cost roughly 812 tokens of context every time the server is loaded.
Is the Germany Tenders MCP server still maintained?
Germany Tenders 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 Germany Tenders MCP server under?
Germany Tenders declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.