GMCA Certainty Matrix Validate
REMOTE · VALIDATE.GMCA.BE
GMCA Certainty Matrix Validate: 11 vragen om een project te screenen vóór investering.
Available components
Last scanned (23 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 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 3 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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 23 Oct 26 +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.
- 21 Oct 26 +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.
- 19 Oct 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.
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 4 Nov 2026 · Probed https://validate.gmca.be/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=validate.gmca.be | CN=WR3,O=Google Trust Services,C=US | 18 Oct 2026 | 16 Jan 2027 | RSA 2048 | SHA256-RSA | 6b17dc25b0a1f97c0a0bb7d446a5cbf9 |
| SANs: validate.gmca.be | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
| CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 1 Sept 1998 | 28 Jan 2028 | RSA 2048 | SHA1-RSA | 40000000001154b5ac394 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of validate.gmca.be. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| be. | present | 45588 | 13 | Verified |
| gmca.be. | present | 12124 | 13 | Verified |
| validate.gmca.be. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31556926 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://validate.gmca.be/mcp | Verified | 200 | |
| http (plaintext) | http://validate.gmca.be/mcp | HTTPS enforced | 301 | https://validate.gmca.be/mcp |
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 →
explain_validate_question Licht een Validate-vraag toe met een voorbeeld ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| questionId | string | yes | Het question-id uit get_validate_questions, bv. 'psf-1a' |
No output schema declared.
No examples provided.
get_validate_questions Haal de GMCA Certainty Matrix Validate-vragen op ~100
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_validate_answers Dien Validate-antwoorden in en ontvang het resultaat ~313
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.
| Name | Type | Req | Description |
|---|---|---|---|
| aiUsage | string | – | Rol van AI in dit project, indien de gebruiker dat wil delen |
| answers | object | yes | 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 | yes | 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 |
No output schema declared.
No examples provided.
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.
remote · validate.gmca.be
claude mcp add --transport http tridevils-gmca-certainty-matrix-validate 'https://validate.gmca.be/mcp'
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 79 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.