Skip to main content
Glama
nonameuserd

@chitmark/haven-mcp

by nonameuserd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @chitmark/haven-mcp

No user-submitted related servers found.

    Related Servers

    • @testmaze/mcp

      zcalo
      A
      license
      Not graded
      quality
      D
      maintenance
      Connects MCP-compatible coding agents to a hosted Test Maze instance for verifying test scenarios via a stdio-to-HTTP proxy.
      45 npm
      MIT

    • ChatGPT Gateway MCP Nyan

      wada-qualia
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agent clients to safely connect to tools and execution resources through MCP with authorization, approvals, audit, chat-context isolation, SSH/Docker access, and long-running command session tracking.
      MIT

    • scriptit

      shreyjindal81
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to connect to remote MCP servers once, access their tools through a compact MCP endpoint, pair a CLI inside sandboxes, and create watches that turn command or tool output into pollable structured events.
      2
      -

    • agenzax-mcp

      Agenzax
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to connect to Agenzax's REST API over stdio, providing tools for messaging, session management, and review-mode oversight.
      18
      303 npm
      MIT

    • local-bridge

      tianshu-ai
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects local tools (browser, shell) to a remote MCP server via reverse-MCP, enabling the server agent to control your local browser and execute shell commands.
      64 npm
      Apache 2.0
    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.4/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools target clearly distinct actions: session lifecycle, roster glance, skill matching, posting, waking, and work. The main overlap is among find_agent, request_collaboration, and delegate, but the descriptions explicitly call out when to prefer each, so misselection risk is low though not zero.

    Naming Consistency4/5

    The majority follow a verb_noun or verb_direction pattern (create_session, list_capabilities, wake_cancel), making the set mostly predictable. Deviations like session_status (noun_status) and handoff (pure noun) are minor and still readable, so consistency is high but not perfect.

    Tool Count5/5

    14 tools is well within the ideal 3-15 range and every tool carries a distinct responsibility in the Haven collaboration lifecycle. Nothing feels redundant or padding, and the count matches the broad but focused domain of agent delegation and work orchestration.

    Completeness4/5

    The surface covers session lifecycle, discovery, roster presence, collaboration posting/matching, task handoff lifecycle, garden work, outcome receipts, and wake-based event waiting. Minor gaps exist—such as no explicit tool for canceling/updating a Looking intent—but these are workaroundable via existing mechanisms like find_agent or the Wake watch, so the core workflows have no dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources