Skip to main content
Glama
crozzbite

SkullRender-Agents MCP Server

by crozzbite

Related Servers

Alternatives to SkullRender-Agents MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables agents and projects to register identities, publish and discover contract manifests (berths), resolve dependencies and check compatibility, and subscribe to or broadcast contract-change notifications over MCP tools and resources. It also supports isolated agent-to-agent messaging and an admin overview of participants, berths, subscriptions, and audit history.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP hosts to run a user-configurable agent with multi-engine orchestration, declarative connectors to third-party APIs, task-graph execution, audit ledger, and memory, without needing to clone or configure multiple repositories.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides a unified registry for discovering and managing agents that implement the A2A (Agent-to-Agent) protocol, enabling registration, querying, and CRUD operations on agent metadata through both REST API and MCP tools.
      3 npm
      3
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      A safety-first MCP operations cockpit for Hermes Agent installations, exposing typed, evidence-producing management primitives.
      73
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables managing a canonical library of agent skills and MCP servers, syncing them across multiple development harnesses, and adding, importing, or configuring them through MCP tools.
      14 npm
      MIT

    TDQS

    A4.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource and operation: listing/getting agents, listing/getting packs, resolving identities, and validating/retrieving schemas for briefs. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    All tools share the 'skflow_' prefix and mostly follow a resource_action pattern. The only deviations are 'skflow_brief_schema' lacking an explicit verb and the singular/plural inconsistency between list and get (e.g., 'agents_list' vs 'agent_get').

    Tool Count5/5

    With 7 tools, the server is well-scoped for its purpose—covering agent manifests, personality packs, identity resolution, and brief validation—without being bloated or too sparse.

    Completeness5/5

    The tool set provides a complete read-oriented workflow for the domain: list and get for both agents and packs, a resolution function, and validation with its accompanying schema. No obvious gaps or dead ends are apparent.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues