Skip to main content
Glama
novyxlabs

novyx-mcp

Official
by novyxlabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to novyx-mcp

No user-submitted related servers found.

    Related Servers

    • GoodMemory

      hjqcan
      A
      license
      B
      quality
      A
      maintenance
      Local-first, auditable memory for Codex, Claude Code, and MCP clients. It stores scoped user/project memory in SQLite or Postgres, serves read-only recall and inspection tools by default, and supports opt-in governed writeback with review and forget controls.
      8
      145 npm
      18
      MIT

    • Memclaw

      caura-ai
      A
      license
      Not graded
      quality
      A
      maintenance
      Governed shared memory platform for AI agents and agent fleets. Provides persistent memory, cross-agent knowledge sharing, permissions, audit trails, and multi-tenant isolation through a Model Context Protocol (MCP) server.
      4 npm
      531
      Apache 2.0

    • flaiwheel

      dl4rce
      A
      license
      A
      quality
      A
      maintenance
      Self-hosted memory and governance layer for AI coding agents. 28 MCP tools with hybrid search, structured knowledge capture, behavioral nudges, and git-native storage. Zero cloud dependencies.
      30
      6
      Business Source 1.1

    • agentos-mcp-server

      imran-siddique
      A
      license
      Not graded
      quality
      F
      maintenance
      Governance kernel for AI agents — policy enforcement, code safety verification, multi-model hallucination detection (CMVK), trust attestation (IATP), and immutable audit trails. Works with Claude Desktop, Cursor, and any MCP client.
      74
      MIT

    • uacos

      caotiensinh
      A
      license
      Not graded
      quality
      C
      maintenance
      Local-first code intelligence and safety layer for AI coding agents. MCP server exposes dependency graph, impact analysis, and AST-compressed repo context, backed by typed local memory, patch-scope safety gates, and git-independent transaction rollback.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 120 tools

    Disambiguation5/5

    Each tool has a clearly defined purpose with detailed descriptions. Even within large categories (defense, replay, threat), tools are distinct (e.g., replay_diff vs replay_recall) and cross-category overlaps are negligible.

    Naming Consistency4/5

    The majority of tools follow a verb_noun pattern (create_, list_, delete_), but some deviate with noun-first names (action_history, cortex_status) or single verbs (forget, remember). This is a minor inconsistency in an otherwise predictable scheme.

    Tool Count2/5

    120 tools is excessive for any single MCP server. While the scope is broad (memory, agents, threat intelligence, etc.), many tools could be consolidated (e.g., multiple replay variants). The high count risks overwhelming agents and increasing selection errors.

    Completeness5/5

    The tool surface covers all major operations: full CRUD for entities, missions, agents, policies, memory, knowledge graph; plus advanced features like replay, evaluation, threat intelligence, and introspection. No obvious gaps for the intended domain.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources