GMCA Certainty Matrix Validate MCP server
io.github.tridevils/gmca-certainty-matrix-validatetridevilsstreamable-httpv1.0.7Scanned
GMCA Certainty Matrix Validate: 11 vragen om een project te screenen vóór investering.
3 tools: 1 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the GMCA Certainty Matrix Validate MCP server can do
The GMCA Certainty Matrix Validate MCP server is published by the GitHub account tridevils. It has 3 tools. It can create or change data (1 tool: submit_validate_answers), but cannot delete data. 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 1.0.7.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 1Claude Code: ask
submit_validate_answersVerwerkt 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 statusl…No findings
Why it is in this group
- The name "submit_validate_answers" says "submit": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 2Show 2 read-only tools
explain_validate_questionGeeft een korte, neutrale toelichting en een concreet voorbeeld bij één specifieke Validate-vraag.No findings
Why it is in this group
- The name "explain_validate_question" says "explain": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_validate_questionsGeeft de 11 officiële Validate-vragen terug, elk met een neutrale toelichting en voorbeeld.No findings
Why it is in this group
- The name "get_validate_questions" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:12 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://validate.gmca.be/mcp: tools/list returned 3 tools to an anonymous client, including submit_validate_answers (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 changed.~3 changedView diff
- Changed:explain_validate_questionOnly readsinputSchemaannotations
- Changed:get_validate_questionsOnly readsannotations
- Changed:submit_validate_answersChanges thingsinputSchemaannotations
Install
Pinned to version 1.0.7. Values in angle brackets are yours to fill in.
claude mcp add --transport http gmca-certainty-matrix-validate https://validate.gmca.be/mcpclaude mcp add --transport http gmca-certainty-matrix-validate https://validate.gmca.be/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__gmca-certainty-matrix-validate__get_validate_questions",
"mcp__gmca-certainty-matrix-validate__explain_validate_question"
],
"ask": [
"mcp__gmca-certainty-matrix-validate__submit_validate_answers"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as gmca-certainty-matrix-validate. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.tridevils/gmca-certainty-matrix-validate/verify?hash=c0d501d5ac25de2d1ce9fef086cffc412fa224429280ac0255d9b7b2eb626b9b" | jq -e '.changed == false'Pinned hash c0d501d5ac25, from Nov 13, 2026, 10:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.tridevils/gmca-certainty-matrix-validate/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.tridevils/gmca-certainty-matrix-validate)Source: MCP Registry. Synced Nov 13, 2026, 11:17 UTC.
GMCA Certainty Matrix Validate MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the GMCA Certainty Matrix Validate MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the GMCA Certainty Matrix Validate MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the GMCA Certainty Matrix Validate MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the GMCA Certainty Matrix Validate MCP server have?
- 3 tools: 1 write, 2 read. submit_validate_answers, get_validate_questions and explain_validate_question.
Does the GMCA Certainty Matrix Validate MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the GMCA Certainty Matrix Validate MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the GMCA Certainty Matrix Validate MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.