Skip to main content
Glama
Doucs91

Hivelore

by Doucs91
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Hivelore

Related Servers

  • corbat by corbat-tech

    corbatofficial

    corbat-tech
    A
    license
    A
    quality
    D
    maintenance
    Policy and quality engine for AI coding agents that enforces team coding standards and provides validation gates for agent-assisted software delivery.
    7
    32 npm
    4
    MIT

  • Laguarde

    FuturPanda
    F
    license
    Not graded
    quality
    B
    maintenance
    Enables AI coding agents to evaluate actions against team-defined policies, record decisions, and obtain human approvals for potentially risky operations.
    57 npm
    1
    -

  • MCP Policy Gatekeeper

    GILSMON
    F
    license
    A
    quality
    D
    maintenance
    Provides real-time policy enforcement for AI coding agents by intercepting and validating their actions against organizational standards like naming conventions, security policies, and compliance rules before execution. Prevents violations through immediate feedback and auto-correction suggestions.
    5
    -

  • MCP Memory Server

    keleshteri
    A
    license
    B
    quality
    D
    maintenance
    Gives AI coding assistants persistent memory, safety controls, and project awareness by tracking coding sessions, protecting critical files from modifications, and managing approval workflows with automatic changelog generation.
    19
    9 npm
    MIT

  • AgentShield

    shima78
    A
    license
    Not graded
    quality
    B
    maintenance
    Enforces configurable policies on AI agent tool calls, allowing, requesting review, or denying actions before they are executed.
    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

A4/5.0

Scored across 15 tools

Disambiguation4/5

Each tool has a distinguishable role: ingestion (mem_save, mem_tried, mem_session_end), retrieval (get_briefing, mem_search, mem_get, mem_relevant_to), and validation (mem_verify, pre_commit_check). The main friction is that mem_save accepts type 'attempt' while mem_tried exists for the same purpose, and the four retrieval tools occupy adjacent territory, though their descriptions mitigate the ambiguity well.

Naming Consistency4/5

Memory tools consistently use the mem_ prefix, code tools use code_, and remaining actions mostly follow verb_noun snake_case (propose_sensor, report_friction, scaffold_test). Minor deviations like get_briefing vs mem_get, mem_session_end, and code_map slightly break the pattern, but overall the naming is predictable and readable.

Tool Count4/5

Fifteen tools is at the upper edge of well-scoped and most tools earn their place. The set feels slightly heavy because retrieval is split across four overlapping entry points and staleness checking appears in both mem_verify and pre_commit_check, but it is not bloated.

Completeness4/5

The core memory lifecycle is covered: create, read, update, verify, session recap, plus code lookup and pre-commit protection. The main gaps are the lack of a delete/archive tool for memories or sensors and no in-server tool to build the code index, but these are workable minor gaps rather than critical missing operations.

Maintenance

ActivityActive
ResponsivenessNo issues

Resources