Nostr MCP Server

MCP server enabling AI agents to interact with the Nostr protocol — a decentralized, censorship-resistant social networking protocol. Enables agents to publish notes (posts), query events from Nostr relays, search profiles, follow/unfollow users, and interact with Nostr's decentralized social graph through MCP tool calls.

Evaluated Mar 07, 2026 (0d ago) vcurrent
Homepage ↗ Repo ↗ Other nostr decentralized social protocol mcp-server bitcoin web3 censorship-resistant
⚙ Agent Friendliness
67
/ 100
Can an agent use this?
🔒 Security
81
/ 100
Is it safe for agents?
⚡ Reliability
62
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
62
Documentation
63
Error Messages
60
Auth Simplicity
85
Rate Limits
72

🔒 Security

TLS Enforcement
85
Auth Strength
88
Scope Granularity
75
Dep. Hygiene
70
Secret Handling
82

Nostr nsec is cryptographic identity — protect absolutely. Published content is permanent and censorship-resistant. Decentralized model means no takedowns possible.

⚡ Reliability

Uptime/SLA
62
Version Stability
62
Breaking Changes
60
Error Recovery
62
AF Security Reliability

Best When

A developer or researcher interested in decentralized social protocols wants AI agents to interact with Nostr — for publishing, research, or building Nostr-based applications.

Avoid When

You need centralized social media management (Twitter/X, LinkedIn, etc.) — Nostr's decentralized model is fundamentally different. Niche tool for the Nostr/Bitcoin community.

Use Cases

  • Publishing content to the Nostr decentralized network from content agents
  • Querying Nostr events and profiles from research agents
  • Monitoring specific Nostr public keys for content from tracking agents
  • Integrating Nostr social publishing into AI-driven content workflows

Not For

  • Teams needing centralized social platform features (Nostr is decentralized with no central moderation)
  • Production social media management without understanding Nostr's decentralized model
  • Users without Nostr key pairs (npub/nsec)

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: api_key
OAuth: No Scopes: No

Nostr private key (nsec) required for publishing. Public key (npub) for read-only queries. NEVER expose nsec — it controls your Nostr identity. Use read-only where possible.

Pricing

Model: free
Free tier: Yes
Requires CC: No

Free open source protocol. MCP server is free. Some relays may charge fees for publishing; many free relays exist.

Agent Metadata

Pagination
none
Idempotent
Partial
Retry Guidance
Not documented

Known Gotchas

  • CRITICAL: Nostr nsec (private key) controls identity — never expose in logs or tool parameters
  • Nostr events are cryptographically signed and immutable — cannot delete published content
  • Relay availability varies — queries across multiple relays improve reliability
  • Nostr is niche (primarily Bitcoin/cypherpunk community) — limited mainstream adoption
  • AustinKelsay is a known Nostr/Bitcoin developer — community-credible implementation

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Nostr MCP Server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-03-07.

6470
Packages Evaluated
26150
Need Evaluation
173
Need Re-evaluation
Community Powered