Skip to main content
Glama
rzazo24

nostrclaw

by rzazo24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to nostrclaw

No user-submitted related servers found.

    Related Servers

    • 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.
      -

    • nostr-bray

      forgesworn
      A
      license
      Not graded
      quality
      A
      maintenance
      Trust-aware Nostr MCP server. 236 tools for identity, social, DMs, trust scoring, AI-to-AI dispatch, Lightning payments, privacy proofs, and encrypted vaults. NIP-46 bunker auth; keys never leave the signing device.
      1,245 npm
      1
      MIT

    • Nostr Signer

      hudhaifahz
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables ChatGPT and Codex to request public keys, prepare and sign exact Nostr events, encrypt or decrypt NIP-04/NIP-44 payloads, and publish with per-relay acknowledgement, while the private key stays in the user's Alby, nos2x, or remote NIP-46 signer. Every operation is queued for local browser approval, with one-use signing intents and verification before anything is broadcast.
      Apache 2.0

    • nostr-mcp

      DiegoYegros
      A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server for safely exploring Nostr, enabling agents to resolve identifiers, fetch profiles and events, query notes, and inspect relay metadata. It does not accept private keys or publish events.
      5
      12 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.9/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have clearly distinct scopes: relay configuration/metadata, event fetching/counting, aggregate reports, single-entity analysis, and multi-relay comparison. Potential confusion remains between event_engagement and review_interactions, which both inspect interactions around one event/note, and between account_triage and trust_score, which both score keys from different evidence, but their descriptions differentiate them well.

    Naming Consistency4/5

    All tool names use lower snake_case, which is consistent and readable. However the pattern mixes noun-first names such as activity_report and trust_score with verb-first names such as count_events and compare_relays, and nostrclaw_status carries a server prefix, so it is not a strict verb_noun convention.

    Tool Count5/5

    12 tools is well within the ideal 3-15 range for a multi-purpose relay analysis server. Each tool appears to serve a distinct investigative function, including status, relay metadata, event retrieval/counting, aggregate reports, single-author/event/relay analysis, and trust/triage.

    Completeness4/5

    The surface covers the apparent read-only Nostr investigation domain comprehensively: configuration, relay metadata, event retrieval/counting, activity/author reports, triage, engagement, relay comparison, trust scoring, interaction review, and event location checks. Minor gaps include no dedicated single-event content retrieval by id and no standalone profile lookup beyond author_report.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources