# Germany Tenders (npm · @pipeworx/mcp-germany-tenders)

Germany public procurement MCP — official German government tenders (keyless).

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-germany-tenders/germany-tenders-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-germany-tenders/germany-tenders-mcp)
- npm · `@pipeworx/mcp-germany-tenders`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-germany-tenders/pipeworx-mcp-germany-tenders.md), [page](https://verifymcp.io/servers/pipeworx-io-germany-tenders/pipeworx-mcp-germany-tenders)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-germany-tenders`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-germany-tenders).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-germany-tenders -- npx -y @pipeworx/mcp-germany-tenders
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-germany-tenders": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-germany-tenders"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-germany-tenders": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-germany-tenders"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-germany-tenders -- npx -y @pipeworx/mcp-germany-tenders
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-germany-tenders": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-germany-tenders"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-germany-tenders --command npx --arg -y --arg @pipeworx/mcp-germany-tenders
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-germany-tenders:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-germany-tenders"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-germany-tenders": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-germany-tenders"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-germany-tenders -t stdio -c npx -a -y @pipeworx/mcp-germany-tenders
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-germany-tenders": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-germany-tenders"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 82, +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.

### 2026-11-03 (score 81, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-02 (score 80, 0)

- [functional regression] Security disclosure: fail → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-01 (score 80, +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.

### 2026-10-30 (score 79, +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.

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (3)

### `germany_search_tenders` (~316 tokens)

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.

Input parameters:

- `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"…

### `germany_buyer_spend_history` (~257 tokens)

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).

Input parameters:

- `buyer` (string, required): 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).

### `germany_supplier_win_history` (~239 tokens)

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.

Input parameters:

- `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, required): Supplier/company name, partial match, e.g. "Uniola AG", "System Strobel".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-germany-tenders/pipeworx-mcp-germany-tenders#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 78

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-germany-tenders
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-germany-tenders
- Repository: https://github.com/pipeworx-io/mcp-germany-tenders
- Website: https://pipeworx.io/packs/germany-tenders
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-germany-tenders/pipeworx-mcp-germany-tenders.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-germany-tenders/pipeworx-mcp-germany-tenders.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-germany-tenders/pipeworx-mcp-germany-tenders