Skip to main content
Glama
jorgenclaw

Nostr Tools for AI Agents

by jorgenclaw
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Nostr Tools for AI Agents

No user-submitted related servers found.

    Related Servers

    • 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.
      268 npm
      1
      MIT

    • Agentry MCP Server

      cthulhutoo
      A
      license
      Not graded
      quality
      F
      maintenance
      Provides a trust layer for AI agents with identity, reputation, payments, and discovery via 92 API endpoints as MCP tools, leveraging Nostr-native infrastructure.
      MIT

    • nostr-auth

      dyegolara
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM coding agents to sign in with Nostr by generating NIP-07 signatures and exposing public keys, without requiring a wallet or browser extension.
      9 npm
      MIT

    • nwc-mcp

      llmops-pro
      A
      license
      A
      quality
      D
      maintenance
      MCP server exposing a Lightning wallet to LLM agents over Nostr Wallet Connect (NIP-47): balance, invoices, LN address/LNURL payments, batch pay, and keysend. All spend tools are wrapped in a defense-in-depth safety stack — budget caps, allowlist, two-step confirmation, audit log.
      13
      32 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

    C2.8/5.0

    Scored across 23 tools

    Disambiguation2/5

    Many tools overlap conceptually: e.g., 'createNostrEvent' vs 'createNote', 'postNote' vs 'createNote'+'signNote'+'publishNote', and 'publishNostrEvent' vs 'publishNote'. The distinction between generic and specific tools is unclear, causing potential confusion for agents.

    Naming Consistency3/5

    All names use camelCase, but patterns are mixed: some are verb+object ('createNote'), others verb+protocol ('decryptNip04'), and some use prepositions ('reactToEvent', 'replyToEvent'). While readable, the inconsistency in verb choice and structure reduces predictability.

    Tool Count4/5

    With 23 tools, the server covers many Nostr operations. While slightly high, most tools have distinct roles in sending, receiving, and managing events. A few could be merged (like generic vs specific event creation), but overall the count is reasonable for a comprehensive Nostr toolset.

    Completeness2/5

    The server focuses exclusively on writing and event creation operations (create, sign, publish, encrypt). There are no tools for reading or querying events (e.g., subscribe, fetch filters), which is a major gap for an agent to usefully interact with Nostr. The set is severely one-sided.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources