# GBU Compliance (remote · gbu-compliance.rowb.app)

German Gefaehrdungsbeurteilung: assess against the ArbSchG s5(3) checklist and build the s6 record.

- Trust score: 64/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `gbu-compliance.rowb.app`: 64/100 (this document), [markdown](https://verifymcp.io/servers/app-rowb-gbu-compliance-assessment/gbu-compliance.md), [page](https://verifymcp.io/servers/app-rowb-gbu-compliance-assessment/gbu-compliance)

## Channel facts

- Endpoint: `https://gbu-compliance.rowb.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-10-18.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 290 tokens (~72/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% 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 4 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**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the GBU Compliance MCP server?

GBU Compliance is a hosted endpoint at https://gbu-compliance.rowb.app/mcp, so there is nothing to install locally. 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 --transport http app-rowb-gbu-compliance-assessment 'https://gbu-compliance.rowb.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-rowb-gbu-compliance-assessment": {
      "url": "https://gbu-compliance.rowb.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-rowb-gbu-compliance-assessment": {
      "type": "http",
      "url": "https://gbu-compliance.rowb.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-rowb-gbu-compliance-assessment]
url = "https://gbu-compliance.rowb.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-rowb-gbu-compliance-assessment": {
      "type": "remote",
      "url": "https://gbu-compliance.rowb.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-rowb-gbu-compliance-assessment --url 'https://gbu-compliance.rowb.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-rowb-gbu-compliance-assessment:
    url: "https://gbu-compliance.rowb.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-rowb-gbu-compliance-assessment": {
      "Transport": "http",
      "Url": "https://gbu-compliance.rowb.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-rowb-gbu-compliance-assessment -t streamable-http -u 'https://gbu-compliance.rowb.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-rowb-gbu-compliance-assessment": {
      "type": "http",
      "url": "https://gbu-compliance.rowb.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-10-17 (score 64, +1)

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

### 2026-10-15 (score 63, +1)

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

### 2026-10-13 (score 62, +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-10-12 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 20. That category is still filling its 30-day observation window: 4 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.

### 2026-10-10 (score 60, +1)

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

### 2026-10-07 (score 59)

First indexed and scored.

## MCP tools (4)

### `list_hazards` (~51 tokens)

List the hazard checklist used for a Gefährdungsbeurteilung, grouped by the six categories of ArbSchG §5(3). Read this first, then pick IDs for assess_workplace.

### `assess_workplace` (~122 tokens)

Assess a workplace against the section 5(3) hazard checklist. Returns risk level per hazard, the gaps that are not low, and the next review date. Deterministic: same input gives the same output.

Input parameters:

- `employees` (integer): Number of employees (optional, stored in the record).
- `hazards` (array, required): Hazard IDs from list_hazards, e.g. ["H01","H02","H12"].
- `sector` (string): Free-text sector label, e.g. "Metallbau" or "Praxis".

### `documentation` (~74 tokens)

Build the section 6 ArbSchG documentation record for an assessment: result, measures and the review result field. Returns the three fields section 6 requires.

Input parameters:

- `employer` (string): Employer name to print on the record.
- `hazards` (array, required): Hazard IDs from list_hazards.
- `sector` (string)

### `review_due` (~43 tokens)

Return the next review date for a risk level (high 180 days, medium 365, low 730).

Input parameters:

- `risk` (string, required): high, medium or low

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-rowb-gbu-compliance-assessment/gbu-compliance#diagnostics

## Score history

- 2026-10-18: 64
- 2026-10-17: 64
- 2026-10-16: 63
- 2026-10-15: 63
- 2026-10-14: 62
- 2026-10-13: 62
- 2026-10-12: 61
- 2026-10-10: 60
- 2026-10-07: 59

## Common questions

### What is the GBU Compliance MCP server?

GBU Compliance is an MCP server listed in the public MCP registry as app.rowb.gbu-compliance/assessment. German Gefaehrdungsbeurteilung: assess against the ArbSchG s5(3) checklist and build the s6 record. This page covers its hosted endpoint (https://gbu-compliance.rowb.app/mcp).

### Is the GBU Compliance MCP server safe to use?

GBU Compliance scores 64 out of 100 on VerifyMCP. 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 GBU Compliance MCP server expose?

GBU Compliance exposes 4 tools: list_hazards, assess_workplace, documentation, review_due. Their descriptions and schemas cost roughly 290 tokens of context every time the server is loaded.

### Does the GBU Compliance MCP server require authentication?

No. We connected to GBU Compliance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the GBU Compliance MCP server still maintained?

GBU Compliance is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://gbu-compliance.rowb.app/mcp
- Website: https://gbu-compliance.rowb.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-rowb-gbu-compliance-assessment/gbu-compliance.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-rowb-gbu-compliance-assessment/gbu-compliance.json
- HTML version of this page: https://verifymcp.io/servers/app-rowb-gbu-compliance-assessment/gbu-compliance