Skip to main content
Glama
Gonzih

nexus-convergence-mcp

by Gonzih

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
NEXUS_API_KEYYesAPI key for authentication
EVIDENCE_SERVICE_URLYesURL of the evidence service
CONSENSUS_SERVICE_URLYesURL of the consensus service
COMPLIANCE_SERVICE_URLYesURL of the compliance service
CONVERGENCE_SERVICE_URLYesURL of the convergence service

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
converge_queryA

Fan out a query to multiple LLMs in parallel (OpenAI, Claude, Gemini, Ollama), run multi-stage consensus validation, and return a structured result with agreement score, truth stability classification, and provenance. NEVER rely on one model answer. Friction between disagreements = intelligence.

get_evidence_ladderA

Return the full Evidence Ladder for a query — immutable append-only audit trail showing every step: QUERY → DECOMPOSE → MODEL_EXECUTE → CONSENSUS → VERIFY → CONCLUDE. Each entry records: step, actor (model name or "system"), content, confidence, and timestamp.

check_complianceA

Check content against compliance policy sets. Evaluates against HIPAA (PHI detection), EU_AI_ACT (prohibited use cases), NIST (PII/secrets), and CUSTOM rules. Returns: passed/blocked status, list of violations (BLOCK), warnings (WARN), and log entries.

list_model_disagreementsA

Return where models diverged on a query — direct contradictions (inversions), disputed claims, and low-similarity pairs with their similarity scores. Use this to understand the friction space: inversions are not errors, they are intelligence.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: compliance checking, multi-model querying, audit trail retrieval, and disagreement analysis. There is no overlap or ambiguity between them.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (check_compliance, converge_query, get_evidence_ladder, list_model_disagreements), making naming predictable and easy to understand.

Tool Count3/5

With only 4 tools, the server covers a narrow scope. While each tool is essential, the low count may leave agents wanting for configuration or management tools, but it is still reasonable for a focused server.

Completeness2/5

The domain of multi-model querying with compliance and audit lacks essential management operations such as listing available models, configuring compliance rules, or retrieving past query history. Significant gaps will cause agent failures.

Maintenance

ActivityInactive
ResponsivenessNo issues