# RPV Calculator (remote · www.rpv-calculator.be)

Belgian procedural indemnity (rechtsplegingsvergoeding) amounts, indexed to the CPI for any date.

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

## Components

- remote · `www.rpv-calculator.be`: 87/100 (this document), [markdown](https://verifymcp.io/servers/pieterjanscheir-rpv-calculator/www.md), [page](https://verifymcp.io/servers/pieterjanscheir-rpv-calculator/www)

## Channel facts

- Endpoint: `https://www.rpv-calculator.be/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-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1049 tokens (~262/item across 4 items; 3 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 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 5 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.
  - Supports UI / widget rendering.

## Install

### How do I install the RPV Calculator MCP server?

RPV Calculator is a hosted endpoint at https://www.rpv-calculator.be/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 pieterjanscheir-rpv-calculator 'https://www.rpv-calculator.be/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "pieterjanscheir-rpv-calculator": {
      "url": "https://www.rpv-calculator.be/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pieterjanscheir-rpv-calculator": {
      "type": "http",
      "url": "https://www.rpv-calculator.be/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.pieterjanscheir-rpv-calculator]
url = "https://www.rpv-calculator.be/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pieterjanscheir-rpv-calculator": {
      "type": "remote",
      "url": "https://www.rpv-calculator.be/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pieterjanscheir-rpv-calculator --url 'https://www.rpv-calculator.be/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  pieterjanscheir-rpv-calculator:
    url: "https://www.rpv-calculator.be/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "pieterjanscheir-rpv-calculator": {
      "Transport": "http",
      "Url": "https://www.rpv-calculator.be/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add pieterjanscheir-rpv-calculator -t streamable-http -u 'https://www.rpv-calculator.be/mcp'
```

### Other

```json
{
  "mcpServers": {
    "pieterjanscheir-rpv-calculator": {
      "type": "http",
      "url": "https://www.rpv-calculator.be/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-11-05 (score 87, +1)

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

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

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

### 2026-11-01 (score 85, +1)

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

### 2026-10-30 (score 84, +1)

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

### 2026-10-27 (score 83, +1)

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

### 2026-10-25 (score 82, +1)

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

### 2026-10-23 (score 81, +1)

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

### 2026-10-21 (score 80, +1)

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

## MCP tools (3)

### `calculate_rpv` (~435 tokens)

Calculate rechtsplegingsvergoeding

Calculates the Belgian procedural indemnity (rechtsplegingsvergoeding / indemnité de procédure) for a claim: the minimum, base and maximum amounts in EUR, indexed for the given date. The result includes an explanation: the calculation steps (tariff, bracket, unindexed Royal Decree amounts, indexation), the judge's discretion under Article 1022 Judicial Code and, for a partly non-monetary claim, how the two tariffs compare. Use it to explain how and why the amount was reached.

Input parameters:

- `amount`: Amount in dispute in EUR. A number, or a Belgian-formatted string such as "2.500,50". Omit for a claim that cannot be valued in money.
- `court_type` (string, required): Court/procedure type: "general" = General rate (art. 2 KB 26/10/2007): all courts and tribunals, including labour courts for e.g. employment-contract disputes. "voorzitter" = President of the Labour…
- `date` (string): Optional reference date (YYYY-MM-DD), usually the date of the judgment. Defaults to today. Uses the indexation in force on that date.
- `locale` (string): Language of the card and the calculator link. Always set it to the language the user writes in (nl, fr, de or en; use "en" for any other language). Defaults to "nl".
- `no_monetary_value` (boolean): True when (part of) the claim cannot be valued in money. If an amount is also given, both the non-monetary amount and the amount bracket are returned.

### `get_rate_table` (~325 tokens)

Get indexed rate table

Returns every bracket of the procedural indemnity table for a court type (min/base/max in EUR), indexed for the given date. Pass the amount in dispute when the user mentions one, so the card can highlight its bracket.

Input parameters:

- `amount`: Optional amount in dispute in EUR, to highlight its bracket. A number, or a Belgian-formatted string such as "12.500".
- `court_type` (string, required): Court/procedure type: "general" = General rate (art. 2 KB 26/10/2007): all courts and tribunals, including labour courts for e.g. employment-contract disputes. "voorzitter" = President of the Labour…
- `date` (string): Optional reference date (YYYY-MM-DD), usually the date of the judgment. Defaults to today. Uses the indexation in force on that date.
- `locale` (string): Language of the card and the calculator link. Always set it to the language the user writes in (nl, fr, de or en; use "en" for any other language). Defaults to "nl".

### `get_indexation_status` (~146 tokens)

Get indexation status

Returns the CPI indexation currently in force for the procedural indemnity amounts, the latest Belgian CPI (base 2004), the estimated date of the next indexation, and the monthly CPI of the last five years. A new multiplier is the CPI of the month that reaches the threshold divided by the start index 105.78, so it is at least next_indexation_minimum_multiplier; do not derive it from the current multiplier.

Input parameters:

- `locale` (string): Language of the card and the calculator link. Always set it to the language the user writes in (nl, fr, de or en; use "en" for any other language). Defaults to "nl".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/pieterjanscheir-rpv-calculator/www#diagnostics

## Score history

- 2026-11-05: 87
- 2026-11-04: 86
- 2026-11-03: 86
- 2026-11-02: 85
- 2026-11-01: 85
- 2026-10-31: 84
- 2026-10-30: 84
- 2026-10-29: 83
- 2026-10-28: 83
- 2026-10-27: 83
- 2026-10-26: 82
- 2026-10-25: 82
- 2026-10-24: 81
- 2026-10-23: 81
- 2026-10-22: 80
- 2026-10-21: 80
- 2026-10-20: 79
- 2026-10-19: 79
- 2026-10-18: 78
- 2026-10-17: 78
- 2026-10-16: 77
- 2026-10-15: 77
- 2026-10-14: 76
- 2026-10-13: 76
- 2026-10-12: 76
- 2026-10-10: 75

## Common questions

### What is the RPV Calculator MCP server?

RPV Calculator is an MCP server listed in the public MCP registry as io.github.pieterjanscheir/rpv-calculator. Belgian procedural indemnity (rechtsplegingsvergoeding) amounts, indexed to the CPI for any date. This page covers its hosted endpoint (https://www.rpv-calculator.be/mcp).

### Is the RPV Calculator MCP server safe to use?

RPV Calculator scores 87 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 RPV Calculator MCP server expose?

RPV Calculator exposes 3 tools: calculate_rpv, get_rate_table, get_indexation_status. Their descriptions and schemas cost roughly 906 tokens of context every time the server is loaded.

### Does the RPV Calculator MCP server require authentication?

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

### Is the RPV Calculator MCP server still maintained?

RPV Calculator 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 did VerifyMCP test on the RPV Calculator MCP server?

VerifyMCP ran 14 checks on RPV Calculator, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://www.rpv-calculator.be/mcp
- Website: https://www.rpv-calculator.be/
- Changelog RSS feed: https://verifymcp.io/servers/pieterjanscheir-rpv-calculator/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/pieterjanscheir-rpv-calculator/www/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pieterjanscheir-rpv-calculator/www.json
- HTML version of this page: https://verifymcp.io/servers/pieterjanscheir-rpv-calculator/www