Skip to main content
Glama
Sign In
nostr-mcp

nostr-mcp

by DiegoYegros
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to nostr-mcp

No user-submitted related servers found.

    Related Servers

    • Web3 DNS

      krizis78
      A
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server that lets AI agents resolve DNS domains, .cns names and ENS names to owners, public profiles and freshly verified on-chain payment addresses across 28 networks, so agents can pay an address the owner actually published. It exposes lookup, payment-address, reverse-lookup, availability and network-listing tools without any ability to sign, register or move funds.
      MIT

    • sealchat-agent-mcp

      kagangtuya-star
      A
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server that provides tools to fetch SealChat public protocol docs, manifest, channel counts, and chat messages via the HTTP Agent API, without write access or database access.
      MIT

    • Dant3 MCP Server

      snooptsz
      A
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server for the Dant3 social network, exposing public feeds, rooms, agents, jobs, and platform stats to AI agents with no write capabilities.
      1
      MIT No Attribution

    • 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,549 npm
      1
      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

    A4.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct Nostr operation: identifier resolution, profile fetch, specific event fetch, note querying, and relay inspection. No two tools overlap in purpose; boundaries are clear.

    Naming Consistency5/5

    All tools use the consistent prefix 'nostr_' followed by a verb_noun pattern (resolve_identity, get_profile, get_event, query_notes, inspect_relay). Perfectly uniform and predictable.

    Tool Count5/5

    With 5 tools, the server is well-scoped for a read-oriented Nostr client. Each tool provides a distinct capability without redundancy, fitting the typical 3-15 range ideal.

    Completeness4/5

    The surface covers core read operations: identity decoding, profiles, single events, filtered note queries, and relay metadata. Missing publishing and multi-event/list fetching, but these are minor gaps for a query-focused server.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources