Skip to main content
Glama
bhind

Frontispice

by bhind
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Frontispice

No user-submitted related servers found.

    Related Servers

    • bot-relay-mcp

      Maxlumiere
      A
      license
      A
      quality
      A
      maintenance
      MCP coordination primitive for multi-agent workflows. Lets multiple AI coding agents (Claude Code, Cursor, n8n, custom clients) discover each other and exchange messages and tasks via a shared SQLite-backed message bus.
      37
      106 npm
      4
      MIT

    • zero-trust-mcp

      Harmaien17
      F
      license
      Not graded
      quality
      B
      maintenance
      A lightweight, local-first MCP server that enforces zero-trust data privacy for AI agents by encrypting tool call payloads locally using AES-256-GCM and persisting them to a local SQLite database.
      -

    • agentbus

      onicarps
      A
      license
      B
      quality
      A
      maintenance
      Local MCP event log for multi-agent workspaces, enabling structured event publishing, cursor-based polling, and status checks via SQLite-backed sidecar.
      10
      137 PyPI
      MIT

    • LLM Bus

      danieldoderlein
      A
      license
      B
      quality
      C
      maintenance
      MCP server that provides a live coordination layer for AI agents, including attributable handoffs, a shared event ledger, atomic work-claiming, and advisory file leases to prevent collisions.
      27
      9
      AGPL 3.0
    • hive-memory by hivemem-dev

      hive-memoryofficial

      hivemem-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for personal and shared memory with full-text search (SQLite FTS5) and outcome tracking, compatible with any MCP agent like Claude Code, Cursor, and Codex CLI.
      7 npm
      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 8 tools

    Disambiguation5/5

    Each tool targets a distinct operation in the handoff lifecycle—publishing, reading, listing, routing, tracking, cursor management, and status. There is no overlap between tool purposes.

    Naming Consistency5/5

    All tools follow the consistent `frontispice_<verb>_<object>` pattern (e.g., publish_handoff, list_updates, advance_cursor), with clear verbs and nouns. The naming is perfectly uniform.

    Tool Count5/5

    Eight tools is well-scoped for a handoff management system, covering publishing, reading, routing, listing, and cursor state without redundancy. The count feels appropriate for the domain.

    Completeness5/5

    The surface covers the full lifecycle of handoffs: creation (publish), retrieval (read/list), routing metadata, application tracking, and consumer state management. No obvious gaps exist in the workflow.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources