Skip to main content
Glama
Gonzih

nexus-convergence-mcp

by Gonzih

Related Servers

Alternatives to nexus-convergence-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Exposes RAG and document intelligence pipelines as 8 composable tools for MCP-compatible clients, enabling querying, indexing, classifying, extracting, and assessing documents.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Audits decisions for cognitive biases through an adversarial framework, exposing tools like analyze_decision, list_biases, and get_bias via MCP.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables users to query, compare, and synthesize responses from multiple local and cloud LLMs simultaneously using existing subscriptions. It provides tools for parallel model evaluation, consensus polling with an LLM-as-judge, and response synthesis across different model providers.
      8
      15 npm
      16
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server that exposes governance, trust-scoring, compliance, guardrail, cost, drift, and supply-chain scanning tools and resources to any MCP client over stdio, Streamable HTTP, or legacy HTTP+SSE. It lets agents route every tool call through a deterministic five-way decision (allow, redact, require approval, deny, or quarantine) with hash-chained evidence, human approval workflows, and in-agent trust gates for LangChain, LangGraph, and Google ADK.
      30
      44 PyPI
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Exposes TELOS governance primitives—action scoring, receipt verification, Purpose Anchor inspection, audit-chain queries, and CCRS counterfactual replay—as MCP tools, resources, and prompts for any MCP-compatible client.
      5
      Apache 2.0

    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