Nostr MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Nostr MCP Server?

Nostr MCP Server is a Model Context Protocol (MCP) server that provides Nostr capabilities to large language models (LLMs) like Claude, enabling them to interact with the Nostr network.

How to use Nostr MCP Server?

To use the Nostr MCP Server, clone the repository, install dependencies, and configure it with applications like Claude for Desktop or Cursor. After configuration, you can make requests to interact with the Nostr network.

Key features of Nostr MCP Server?

  • Implements seven tools for Nostr network interaction, including fetching user profiles, notes, and zaps.
  • Supports both hex public keys and npub format for user identifiers.
  • User-friendly display of results with automatic format conversion.

Use cases of Nostr MCP Server?

  1. Fetching user profile information from the Nostr network.
  2. Retrieving text and long-form notes authored by users.
  3. Accessing detailed payment information for zaps sent and received.
  4. Searching through Nostr Implementation Possibilities (NIPs).

FAQ from Nostr MCP Server?

  • Can I use Nostr MCP Server with any LLM?

Yes! It is designed to work with LLMs like Claude and Cursor.

  • Is there a limit on the number of queries?

Yes, the server has a default 8-second timeout for queries to prevent hanging.

  • What formats are supported for user identifiers?

Both hex public keys and npub format are supported.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

14 hours ago