Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

VerifiMind PEAS - RefleXion Trinity

REMOTE · VERIFIMIND.YSENSEAI.ORG

X-Z-CS AI validation with auditable reasoning. 8 active tools; 5 in maintenance. v0.5.68

0 this week 78 Trust /100

Last scanned (13 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2508 tokens (~147/item across 17 items; 13 tools + 4 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 63% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 13 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
    • Server version: 0.5.67 → 0.5.68 functional
  • 4 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 27 Oct 26 0
    • Tool “coordination_handoff_create” rewrote its description, which is the text the model reads security
    • Tool “coordination_handoff_read” rewrote its description, which is the text the model reads security
    • Tool “coordination_team_status” rewrote its description, which is the text the model reads security
    • Tool “get_template_statistics” rewrote its description, which is the text the model reads security
    • Server version: 0.5.66 → 0.5.67 functional
  • 18 Oct 26 0
    • Stability: 0.97 → pass security
    • Server version: 0.5.65 → 0.5.66 functional
  • 17 Oct 26 0
    • Stability: pass → 0.97 functional
Diagnostics

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 21 Nov 2026 · Probed https://verifimind.ysenseai.org/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=verifimind.ysenseai.org CN=WR3,O=Google Trust Services,C=US 14 Nov 2026 12 Feb 2027 RSA 2048 SHA256-RSA e223a6851170732f09021928f74219f0
SANs: verifimind.ysenseai.org
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

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of verifimind.ysenseai.org. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
org. DS published 725 8 Verified
ysenseai.org. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://verifimind.ysenseai.org/mcp/ Verified 200
http (plaintext) http://verifimind.ysenseai.org/mcp/ HTTPS enforced 302 https://verifimind.ysenseai.org/mcp/
MCP tools · 13 exposed · ~2,188 tokens

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 →

Tool Tokens
consult_agent_cs ~237

Consult CS Security agent for security validation and Socratic interrogation. CS Security specializes in: - Security vulnerability assessment - Attack vector identification - Data security review - System integrity analysis - Socratic questioning (challenging assumptions) BYOK (v0.4.5): Pass llm_provider and api_key to use your own LLM. If only api_key is provided, the provider is auto-detected from the key prefix. Keys are ephemeral (never stored) and garbage collected after the call.

NameTypeReqDescription
api_key––Optional API key for the provider (ephemeral, never stored)
concept_descriptionstringyesDetailed description of the concept
concept_namestringyesShort name or title of the concept
context––Optional additional context or background
detailstring––
llm_provider––Optional LLM provider override ('groq', 'anthropic', 'openai', 'gemini', 'mistral', 'ollama', 'mock')
prior_reasoning––Optional reasoning from X and Z agents to consider
user_uuid–––

Structured output declared, but exposes no named fields.

No examples provided.

consult_agent_x ~212

Consult X Intelligent agent for innovation and strategy analysis. X Intelligent specializes in: - Innovation potential assessment - Strategic value analysis - Market opportunity identification - Competitive positioning - Growth potential evaluation BYOK (v0.4.5): Pass llm_provider and api_key to use your own LLM. If only api_key is provided, the provider is auto-detected from the key prefix. Keys are ephemeral (never stored) and garbage collected after the call.

NameTypeReqDescription
api_key––Optional API key for the provider (ephemeral, never stored)
concept_descriptionstringyesDetailed description of the concept
concept_namestringyesShort name or title of the concept
context––Optional additional context or background
detailstring––
llm_provider––Optional LLM provider override ('groq', 'anthropic', 'openai', 'gemini', 'mistral', 'ollama', 'mock')
user_uuid–––

Structured output declared, but exposes no named fields.

No examples provided.

consult_agent_z ~262

Consult Z Guardian agent for ethical review and Z-Protocol enforcement. Z Guardian specializes in: - Ethical implications assessment - Privacy and data protection review - Bias and fairness analysis - Social impact evaluation - Z-Protocol compliance verification Z Guardian has VETO POWER. If veto_triggered is True, the concept should not proceed as it crosses ethical red lines. BYOK (v0.4.5): Pass llm_provider and api_key to use your own LLM. If only api_key is provided, the provider is auto-detected from the key prefix. Keys are ephemeral (never stored) and garbage collected after the call.

NameTypeReqDescription
api_key––Optional API key for the provider (ephemeral, never stored)
concept_descriptionstringyesDetailed description of the concept
concept_namestringyesShort name or title of the concept
context––Optional additional context or background
detailstring––
llm_provider––Optional LLM provider override ('groq', 'anthropic', 'openai', 'gemini', 'mistral', 'ollama', 'mock')
prior_reasoning––Optional reasoning from X agent to consider
user_uuid–––

Structured output declared, but exposes no named fields.

No examples provided.

coordination_handoff_create ~203

Create a structured MACP v2.5 handoff record. TEMPORARILY DISABLED — this tool is contained pending a security repair (incident VM-IR-2026-07-28-COORD-01) and always returns a denial. Handoff bodies written through this tool were stored in a shared namespace that any unauthenticated caller could read. Nothing is stored or returned while containment is in force. Coordination state belongs in your own repository until private, owner-scoped storage ships. All arguments are accepted for schema stability and are ignored; no supplied value is stored, logged, or echoed back.

NameTypeReqDescription
agent_idstringyes–
artifactsarrayyes–
blockersarrayyes–
completedarrayyes–
decisionsarrayyes–
next_agent–––
pendingarrayyes–
pioneer_key–––
session_typestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

coordination_handoff_read ~141

Read the most recent coordination handoff record(s). TEMPORARILY DISABLED — this tool is contained pending a security repair (incident VM-IR-2026-07-28-COORD-01) and always returns a denial. This read path returned complete handoff bodies from a caller-selected namespace with no authenticated ownership check. It is closed to every caller — with or without a key — while owner-scoped access control is rebuilt. No record body is returned. All arguments are accepted for schema stability and are ignored.

NameTypeReqDescription
agent_id–––
countinteger––
pioneer_key–––

Structured output declared, but exposes no named fields.

No examples provided.

coordination_team_status ~132

Return current team coordination state and session summary. TEMPORARILY DISABLED — this tool is contained pending a security repair (incident VM-IR-2026-07-28-COORD-01) and always returns a denial. This summary exposed agent identities, pending actions, open blockers, and a timestamped activity index from a caller-selected namespace with no authenticated ownership check — enough to enumerate a namespace before reading it. It is closed to every caller while owner-scoped access control is rebuilt. All arguments are accepted for schema stability and are ignored.

NameTypeReqDescription
pioneer_key–––

Structured output declared, but exposes no named fields.

No examples provided.

export_prompt_template ~62

Export a prompt template to Markdown or JSON format. v0.4.0 Unified Prompt Templates feature.

NameTypeReqDescription
formatstring–Export format ('markdown' or 'json')
template_idstringyesTemplate to export
user_uuid–––

Structured output declared, but exposes no named fields.

No examples provided.

get_prompt_template ~59

Get a specific prompt template by ID. v0.4.0 Unified Prompt Templates feature.

NameTypeReqDescription
include_contentboolean–Whether to include full template content
template_idstringyesUnique template identifier
user_uuid–––

Structured output declared, but exposes no named fields.

No examples provided.

get_template_statistics ~33

Get statistics about the template registry. v0.4.0 Unified Prompt Templates feature.

NameTypeReqDescription
user_uuid–––

Structured output declared, but exposes no named fields.

No examples provided.

import_template_from_url ~100

Import a prompt template from a URL (GitHub Gist, raw file, etc.). v0.4.0 Unified Prompt Templates feature. Supports: - GitHub Gist URLs - Raw GitHub file URLs - Any HTTPS URL pointing to JSON/YAML template

NameTypeReqDescription
urlstringyesURL to import template from
user_uuid–––
validateboolean–Whether to validate template content (default: True)

Structured output declared, but exposes no named fields.

No examples provided.

list_prompt_templates ~94

List available prompt templates with optional filtering. v0.4.0 Unified Prompt Templates feature.

NameTypeReqDescription
agent_id––Filter by agent (X, Z, CS, or 'all')
category––Filter by category (startup, security, ethics, etc.)
tags––Comma-separated tags to filter by (e.g., 'genesis:phase-1,default')
user_uuid–––

Structured output declared, but exposes no named fields.

No examples provided.

register_custom_template ~107

Register a new custom prompt template. v0.4.0 Unified Prompt Templates feature.

NameTypeReqDescription
agent_idstringyesTarget agent (X, Z, CS, or 'all')
categorystring–Template category (default: 'custom')
contentstringyesTemplate content with {variable} placeholders
description––Template description
namestringyesTemplate display name
tags––Comma-separated tags
user_uuid–––

Structured output declared, but exposes no named fields.

No examples provided.

run_full_trinity ~546

Run complete X → Z → CS Trinity validation with Chain of Thought. This tool orchestrates all three agents in sequence: 1. X Intelligent analyzes innovation and strategy 2. Z Guardian reviews ethics (sees X's reasoning) 3. CS Security validates security (sees X and Z reasoning) 4. Results are synthesized into a unified assessment Each agent sees the reasoning of previous agents, enabling true collaborative analysis with full transparency. BYOK (v0.4.5): Pass llm_provider/api_key for all agents, or use per-agent overrides (x_provider/x_api_key, z_provider/z_api_key, cs_provider/cs_api_key). Per-agent params take priority over global. Keys are ephemeral (never stored) and garbage collected after the call.

NameTypeReqDescription
api_key––Optional global API key for all agents (ephemeral, never stored)
concept_descriptionstringyesDetailed description of the concept
concept_namestringyesShort name or title of the concept
context––Optional additional context or background
cs_api_key––Optional API key override for CS agent only
cs_provider––Optional provider override for CS agent only
detailstring–Reasoning verbosity (v0.5.44) — "standard" (default) returns the auditable `reasoning` block (per-step reasoning, ethics scoring breakdown + framework citations, Socratic questions, threat assessment…
llm_provider––Optional global LLM provider for all agents
save_to_historyboolean–Whether to save the full result to validation history (default: False). The store is shared and instance-local, retains at most the 20 newest opt-in results, evicts oldest entries on every read/write…
user_uuid–––
x_api_key––Optional API key override for X agent only
x_provider––Optional provider override for X agent only
z_api_key––Optional API key override for Z agent only
z_provider––Optional provider override for Z agent only

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the VerifiMind PEAS - RefleXion Trinity MCP server?

VerifiMind PEAS - RefleXion Trinity is a hosted endpoint at https://verifimind.ysenseai.org/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 · verifimind.ysenseai.org

# add to Claude Code
claude mcp add --transport http creator35lwb-web-verifimind-genesis 'https://verifimind.ysenseai.org/mcp/'
Common questions

What is the VerifiMind PEAS - RefleXion Trinity MCP server?

VerifiMind PEAS - RefleXion Trinity is an MCP server listed in the public MCP registry as io.github.creator35lwb-web/verifimind-genesis. X-Z-CS AI validation with auditable reasoning. 8 active tools; 5 in maintenance. v0.5.68. This page covers its hosted endpoint (https://verifimind.ysenseai.org/mcp/).

Is the VerifiMind PEAS - RefleXion Trinity MCP server safe to use?

VerifiMind PEAS - RefleXion Trinity scores 78 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 VerifiMind PEAS - RefleXion Trinity MCP server expose?

VerifiMind PEAS - RefleXion Trinity exposes 13 tools: consult_agent_x, consult_agent_z, consult_agent_cs, run_full_trinity, list_prompt_templates, and 8 more. Their descriptions and schemas cost roughly 2,188 tokens of context every time the server is loaded.

Does the VerifiMind PEAS - RefleXion Trinity MCP server require authentication?

No. We connected to VerifiMind PEAS - RefleXion Trinity without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the VerifiMind PEAS - RefleXion Trinity MCP server still maintained?

VerifiMind PEAS - RefleXion Trinity is still listed as active in the MCP registry. We last reached this channel on 21 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 VerifiMind PEAS - RefleXion Trinity MCP server?

VerifyMCP ran 12 checks on VerifiMind PEAS - RefleXion Trinity, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about VerifiMind PEAS - RefleXion Trinity: Authorization. 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.