$ loading_
Enable AI agents to safely publish, query, and send DMs on Nostr.
This MCP tool is intended for Nostr publishing, queries, and DMs, and it requires sensitive signing credentials or a remote signing URI while also having code-execution capability. However, it comes from the official registry, is open source, and has recent maintenance; no clear red flags for overreach or suspicious exfiltration are evident from the provided materials, so the overall posture is caution rather than high risk.
It requires NOSTR_PRIVATE_KEY and NOSTR_NIP46_URI, which are highly sensitive credentials that can authorize identity-bound signing and messaging. If exposed, they could be abused to impersonate the user for posting, direct messages, or other allowed Nostr actions. The mentioned allowlists and rate limits may reduce abuse scope, but they do not eliminate private-key exposure risk.
Although no fixed remote host is listed, NOSTR_RELAYS indicates it will connect to user-specified Nostr relays, and its stated functions include publishing, querying, and direct messaging, so related content will be sent to those external relays as configured. There is no evidence here of exfiltration to unrelated or unknown endpoints.
The system checks indicate executes-code capability, meaning the MCP service or related code runs locally. For an MCP tool, this is a normal capability; the provided material does not show requests for unusually high system privileges unrelated to Nostr operations or any suspicious command-execution path.
Based on the description, it at least accesses configured secrets/environment variables and handles data such as posts, query results, direct messages, and an audit log. The materials do not specify filesystem scope, and there is no indication of broad access to local directories, system databases, or other resources unrelated to its function.
It comes from the official registry, has an open-source repository, and shows updates within the past year, which are meaningful risk-reducing signals for auditability and maintenance. Although community stars are low and no license is declared, the current materials do not show clear supply-chain red flags.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "io.github.llmops-pro/nostr-ops-mcp" MCP server from askskill: Run: claude mcp add 'io-github-llmops-pro-nostr-ops-mcp' -- npx -y nostr-ops-mcp
Use the Nostr Ops MCP to publish an announcement to my Nostr account: "A new version is live today, fixing login issues and improving performance." Check allowlists and rate limits before sending, then return the event ID and an audit log summary.
Returns the published Nostr event ID, delivery status, and the allowlist and audit log check results.
Use the Nostr Ops MCP to query public posts from the last 24 hours containing the keyword "AI agent", summarize them in a list, sort by engagement, and include the posting time and author for each.
Outputs a summarized list of relevant Nostr posts with author, time, engagement, and topic overview.
Use the Nostr Ops MCP to send a direct message to a specified contact: "We received your feedback and will follow up shortly." Confirm the recipient is on the allowlist before sending; if not, stop and explain why, and record an audit log for this action.
Returns the DM send result, or the reason it was blocked by security policy, along with an audit log summary.
Publish Nostr marketplace listings so agents can operate an automated store.
Connect AI agents to a Lightning wallet with budgets, approvals, and audit logs.
Read Nostr profiles, notes, searches, and relay lists without accounts or keys.
Search team knowledge bases, answer questions with citations, and open related pages.
Coordinate AI agents through negotiation for more efficient automated workflows.
Enable AI agents to send messages, read history, and collaborate in public chat.