Skip to main content
Glama
ola-krutrim

@ola/buzz-mcp

Official
by ola-krutrim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to @ola/buzz-mcp

No user-submitted related servers found.

    Related Servers

    • buzz-mcp

      CedricConday
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to interact with a Buzz relay as a first-class member, allowing agents to read and write signed NIP-29 messages, coordinate via blocking replies, and manage channels with full attributed audit trails.
      1
      Apache 2.0

    • buzz-mcp

      SuperRibeiro
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude Desktop, Claude Code, and Claude.ai to interact with a Buzz relay, allowing users to list channels, read/search messages, and post chat events using NIP-98 authentication.
      -

    • agent-mailbox

      00cyre
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables any agent to send a message by name into a live chat or another agent's conversation, and to receive replies by long-polling an inbox cursor that yields each message exactly once, in order, in roughly a tenth of a second. Also lets agents discover reachable chats, threads, and registered agents, with unresolvable names optionally routed to a relay agent for delivery.
      4 npm
      MIT

    • salt-mcp

      0000F8
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable clients to act as a Salt agent identity to discover and create agents, delegate or consult, chat with humans, post interactive cards, sell products, send invoices, meter usage, manage wallets, and transact on the Salt network via local stdio credentials or hosted OAuth keyless access.
      52 npm
      1
      MIT

    • smithtalks-mcp

      mozzimorzam-sudo
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to read a pseudonymous message network's public feed, claims ledger, marketplace listings, and signed Merkle ledger chain, and — with a paid or proof-of-work pass — to post, claim, and trade capabilities with other agents. Every entry is chained into signed Merkle roots so clients can verify the record themselves with a standalone verifier instead of trusting the server.
      69 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

    A3.8/5.0

    Scored across 24 tools

    Disambiguation5/5

    Every tool maps to a distinct resource/action: channel reading/posting/reply/forward/react/delete are clearly separated, as are DMs, membership, status, auth, and diagnostics. The only mild adjacency is buzz_unread vs buzz_read, but their descriptions (digest counts vs actual messages) remove the ambiguity.

    Naming Consistency3/5

    Tool names share a buzz_ prefix but mix conventions: bare verbs (buzz_read, buzz_post, buzz_search), noun+verb (buzz_dm_read, buzz_status_set, buzz_attachment_read), verb+noun (buzz_setname, buzz_add_member), and noun-only (buzz_channels, buzz_agents). The inconsistency is readable but not predictable.

    Tool Count4/5

    24 tools is at the heavy end, but the breadth is justified by the domain: channels, DMs, attachments, reactions, membership, status, auth, and diagnostics each require distinct operations. No tool is redundant, so the count is slightly over the usual sweet spot rather than bloated.

    Completeness4/5

    The core message lifecycle (post/read/reply/forward/react/delete), attachments, DMs, membership, and status are well covered. Obvious gaps exist — no channel creation/deletion and no message edit — but these can be considered out-of-scope or worked around if channels are pre-provisioned.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources