# GMCA Certainty Matrix Validate (remote · validate.gmca.be)

GMCA Certainty Matrix Validate: 11 vragen om een project te screenen vóór investering.

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

## Components

- remote · `validate.gmca.be`: 80/100 (this document), [markdown](https://verifymcp.io/servers/tridevils-gmca-certainty-matrix-validate/validate.md), [page](https://verifymcp.io/servers/tridevils-gmca-certainty-matrix-validate/validate)

## Channel facts

- Endpoint: `https://validate.gmca.be/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.5`

## 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**: 66/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 3 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 is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 509 tokens (~169/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**: 80/100
  - Stability observed for 24 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 3 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 GMCA Certainty Matrix Validate MCP server?

GMCA Certainty Matrix Validate is a hosted endpoint at https://validate.gmca.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 tridevils-gmca-certainty-matrix-validate 'https://validate.gmca.be/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tridevils-gmca-certainty-matrix-validate": {
      "url": "https://validate.gmca.be/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tridevils-gmca-certainty-matrix-validate": {
      "type": "http",
      "url": "https://validate.gmca.be/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tridevils-gmca-certainty-matrix-validate]
url = "https://validate.gmca.be/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tridevils-gmca-certainty-matrix-validate": {
      "type": "remote",
      "url": "https://validate.gmca.be/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tridevils-gmca-certainty-matrix-validate --url 'https://validate.gmca.be/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tridevils-gmca-certainty-matrix-validate:
    url: "https://validate.gmca.be/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tridevils-gmca-certainty-matrix-validate": {
      "Transport": "http",
      "Url": "https://validate.gmca.be/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tridevils-gmca-certainty-matrix-validate -t streamable-http -u 'https://validate.gmca.be/mcp'
```

### Other

```json
{
  "mcpServers": {
    "tridevils-gmca-certainty-matrix-validate": {
      "type": "http",
      "url": "https://validate.gmca.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 80, +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-11-03 (score 79, +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-11-01 (score 78, +1)

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

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

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

### 2026-10-28 (score 76, +1)

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

### 2026-10-26 (score 75, +1)

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

### 2026-10-23 (score 74, +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-21 (score 73, +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.

## MCP tools (3)

### `get_validate_questions` (~100 tokens)

Haal de GMCA Certainty Matrix Validate-vragen op

Geeft de 11 officiële Validate-vragen terug, elk met een neutrale toelichting en voorbeeld. BELANGRIJK: stel elke vraag individueel en letterlijk aan de eindgebruiker en verzamel per vraag een antwoord Ja/Deels/Nee. Vul de vragen NOOIT zelf in op basis van een projectbeschrijving. De toelichting/voorbeeld mag je meegeven als de gebruiker twijfelt, maar mag het antwoord nooit sturen.

### `explain_validate_question` (~96 tokens)

Licht een Validate-vraag toe met een voorbeeld

Geeft een korte, neutrale toelichting en een concreet voorbeeld bij één specifieke Validate-vraag. Roep dit ENKEL aan wanneer de gebruiker zelf aangeeft de vraag niet te begrijpen of twijfelt over de betekenis — nooit standaard, en nooit om zelf een antwoord te suggereren of in te vullen.

Input parameters:

- `questionId` (string, required): Het question-id uit get_validate_questions, bv. 'psf-1a'

### `submit_validate_answers` (~313 tokens)

Dien Validate-antwoorden in en ontvang het resultaat

Verwerkt de Ja/Deels/Nee-antwoorden van de gebruiker op alle 11 vragen uit get_validate_questions en geeft het voorzichtige, kwalitatieve resultaat terug (geen scores, geen statuslabels). Vraag de gebruiker EERST expliciet om toestemming voor dataopslag (consent=true/false) vóórdat je dit tool aanroept — sla nooit stilzwijgend data op. Vraag ook sector/companySize/projectType/investmentRange als grove categorie (nooit bedrijfs- of projectnaam) — dit is vereist voor toekomstige publicatie per Rules v1.1 sectie 2, maar blijft optioneel als de gebruiker het niet wil delen.

Input parameters:

- `aiUsage` (string): Rol van AI in dit project, indien de gebruiker dat wil delen
- `answers` (object, required): Map van question-id naar 'ja' | 'deels' | 'nee', voor alle 11 vragen uit get_validate_questions
- `companySize` (string): Aantal werknemers als bucket, optioneel
- `consent` (boolean, required): Heeft de gebruiker expliciet ingestemd met anonieme opname in de GMCA-dataset? Verplicht vooraf te vragen aan de gebruiker.
- `investmentRange` (string): Geschatte investeringsomvang als bucket, optioneel
- `projectType` (string): Brede categorie van het type project, optioneel, nooit een projectnaam
- `sector` (string): Brede sector-categorie van de organisatie, optioneel, nooit een bedrijfsnaam

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tridevils-gmca-certainty-matrix-validate/validate#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 77
- 2026-10-30: 77
- 2026-10-29: 76
- 2026-10-28: 76
- 2026-10-27: 75
- 2026-10-26: 75
- 2026-10-25: 74
- 2026-10-24: 74
- 2026-10-23: 74
- 2026-10-22: 73
- 2026-10-21: 73
- 2026-10-20: 72
- 2026-10-19: 72
- 2026-10-18: 71
- 2026-10-17: 71
- 2026-10-16: 70
- 2026-10-15: 70
- 2026-10-14: 69
- 2026-10-13: 69
- 2026-10-12: 68

## Common questions

### What is the GMCA Certainty Matrix Validate MCP server?

GMCA Certainty Matrix Validate is an MCP server listed in the public MCP registry as io.github.tridevils/gmca-certainty-matrix-validate. GMCA Certainty Matrix Validate: 11 vragen om een project te screenen vóór investering. This page covers its hosted endpoint (https://validate.gmca.be/mcp).

### Is the GMCA Certainty Matrix Validate MCP server safe to use?

GMCA Certainty Matrix Validate scores 80 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 GMCA Certainty Matrix Validate MCP server expose?

GMCA Certainty Matrix Validate exposes 3 tools: get_validate_questions, explain_validate_question, submit_validate_answers. Their descriptions and schemas cost roughly 509 tokens of context every time the server is loaded.

### Does the GMCA Certainty Matrix Validate MCP server require authentication?

No. We connected to GMCA Certainty Matrix Validate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the GMCA Certainty Matrix Validate MCP server still maintained?

GMCA Certainty Matrix Validate 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.

## Links

- Remote endpoint: https://validate.gmca.be/mcp
- Website: https://gmca.be/
- Changelog RSS feed: https://verifymcp.io/servers/tridevils-gmca-certainty-matrix-validate/validate.xml
- Changelog JSON feed: https://verifymcp.io/servers/tridevils-gmca-certainty-matrix-validate/validate.json
- HTML version of this page: https://verifymcp.io/servers/tridevils-gmca-certainty-matrix-validate/validate