Skip to main content
Glama
sushiHex

hardline-mcp

by sushiHex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to hardline-mcp

No user-submitted related servers found.

    Related Servers

    • agent-bus-mcp

      tulong66
      A
      license
      B
      quality
      B
      maintenance
      Enables AI agents from different frameworks to communicate asynchronously via a persistent SQLite-backed bus, with doorbell wakeups for sub-second notifications and full message history.
      6
      MIT

    • mcp-comms

      ahmeda14960
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables multiple AI agents to communicate and coordinate via a shared SQLite-backed message log, supporting directed messages, broadcasts, and session discovery.
      -

    • agent-mailbox

      polaris-smart
      A
      license
      B
      quality
      B
      maintenance
      Enables local AI agents on the same machine to exchange messages asynchronously through mailboxes, with tools for registering, sending, replying, checking, broadcasting, and waiting for messages without polling or cloud services.
      9
      1
      MIT

    • agent-handoff-mcp

      SarutobiSasuke8
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to exchange structured work items with an auditable lifecycle, supporting send, acknowledge, block, complete, and cancel operations via a shared SQLite-backed inbox.
      2
      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.3/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: mailbox operations (send, inbox, ack, history) are separate from asking agents (ask_hermes, ask_codex, ask_claude), and sync vs async variants are clearly differentiated by name. The only potential overlap is among the three ask_* tools, but they target different agents and the descriptions name them explicitly.

    Naming Consistency4/5

    Mostly consistent: mailbox tools are single verbs/nouns (send, ack, inbox, history) and query tools follow 'ask_<agent>' with '_async' suffix for background variants. Minor inconsistency is the mix of verb and noun forms for mailbox tools and the absence of 'ask_hermes_async' (which is a completeness gap, not naming), but the overall pattern is readable and predictable.

    Tool Count5/5

    Nine tools is well-scoped for a messaging and agent-query server. Each tool covers a distinct function without redundancy, and the count is within the ideal 3-15 range.

    Completeness4/5

    The core lifecycle is covered: send, read, ack, and history for the mailbox; synchronous ask for all three agents; asynchronous for two of them. Missing async for Hermes and no delete/clear operations are minor gaps that don't severely hamper workflows, but a fully complete surface would include ask_hermes_async and maybe message deletion.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources