Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Trust-aware Nostr for AI agents -- 235 tools covering social, DMs, zaps, trust, and identity
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
NOSTR_SECRET_KEY, NOSTR_RELAYS, NWC_URIAls geheim markierte Werte sind Schlüssel zu deinem Konto. Gib sie nie weiter und füge sie nie in einen Chat ein.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"bray": {
"command": "npx",
"args": [
"-y",
"nostr-bray"
],
"env": {
"NOSTR_SECRET_KEY": "your-value",
"NOSTR_RELAYS": "your-value",
"NWC_URI": "your-value"
}
}
}
}Führe das in deinem Terminal aus
claude mcp add bray --env NOSTR_SECRET_KEY=your-value --env NOSTR_RELAYS=your-value --env NWC_URI=your-value -- npx -y nostr-brayTrag die leeren Werte ein, bevor du ihn startest.
In .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"bray": {
"command": "npx",
"args": [
"-y",
"nostr-bray"
],
"env": {
"NOSTR_SECRET_KEY": "your-value",
"NOSTR_RELAYS": "your-value",
"NWC_URI": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"bray": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"nostr-bray"
],
"env": {
"NOSTR_SECRET_KEY": "your-value",
"NOSTR_RELAYS": "your-value",
"NWC_URI": "your-value"
}
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026
Der Registry-Name wurde über die Domain forgesworn.dev bestätigt (die Registry prüft, wem die Domain gehört)
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Das musst du eintragen: NOSTR_SECRET_KEY, NOSTR_RELAYS, NWC_URI
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (1.27.7) kam vor 7 Monaten in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Node.js auf deinem Computer.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, Safe Fetch
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
MCP server for fetching URLs, safe against SSRF, DNS rebinding, and redirect-to-internal attacks.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Trust-aware Nostr MCP server, CLI and TypeScript SDK for AI and humans. 261 tools across 29 groups. Model-agnostic. Works with Claude, ChatGPT, Gemini, Cursor, Windsurf, or any MCP client.
Requires Node.js 24 or later.
Install globally or run via npx:
npm install -g nostr-bray
New to Nostr? Mint a key first -- this works before anything is configured and prints your npub plus a 24-word mnemonic (write it down; it is the key):
npx nostr-bray create
Add to your MCP client config:
{
"mcpServers": { "nostr": { "command": "npx", "args": ["nostr-bray"], "env": { "NOSTR_SECRET_KEY": "nsec1...", "NOSTR_RELAYS": "wss://relay.damus.io,wss://nos.lol" } } } }
npx nostr-bray with no arguments starts the MCP server (stdio by default, HTTP with TRANSPORT=http); subcommands run the CLI.
Then ask your AI to call whoami to verify it works.
For production use, prefer Heartwood or any NIP-46 bunker (your key never leaves your signing device):
{
"mcpServers": { "nostr": { "command": "npx", "args": ["nostr-bray"], "env": { "BUNKER_URI": "bunker://...", "NOSTR_RELAYS": "wss://relay.damus.io,wss://nos.lol" } } } }
If your signer is an app such as Amber or nsec.app, let bray start the pairing instead of copying a bunker:// URI out of it:
npx nostr-bray bunker pair --relay wss://relay.nsec.app
bray prints a nostrconnect:// URI. Paste or scan it into the signer app and approve. bray shows the account the signer will sign as and asks you to confirm it, then saves the signer, and the MCP server, CLI and SDK (defaultBray()) sign through it with no BUNKER_URI or key in your config.
Treat the URI as a one-time credential: whoever answers it first becomes the signer bray uses, so do not paste it into a chat or leave it on a shared screen. Outside a terminal, pass --expect (the account you mean to sign as) or --yes. bunker status shows whether the saved signer was paired. If the app later forgets bray, run bunker pair again. With TOR_PROXY set, pairing goes through the proxy and accepts only .onion relays unless ALLOW_CLEARNET_WITH_TOR=1. Pick a relay your signer app can reach; --relay can be repeated; without it bray uses NOSTR_RELAYS, then the relays in your config file. bray waits up to five minutes for the signer to answer, or --timeout . The pairing secret is single-use and is not saved. A BUNKER_URI or key you configure still takes precedence over the saved signer, and bunker connect replaces it.
Start the MCP server with no key or bunker and it runs read-only: it holds no signer and loads no wallet, so it cannot post, sign, send or read DMs, decrypt or pay. Only lookup tools are offered (feeds, profiles, search, relay and trust checks), and asking for anything else returns an error saying bray is read-only. Set NOSTR_PUBKEY to an npub to read from that account's perspective, for example its notifications. Set BRAY_READ_ONLY=1 to force this mode even when a key or bunker is configured; a key file is then never opened. The CLI and SDK still require a signer.
{
"mcpServers": { "nostr": { "command": "npx", "args": ["nostr-bray"], "env": { "NOSTR_PUBKEY": "npub1...", "NOSTR_RELAYS": "wss://relay.damus.io,wss://nos.lol" } } } }
| Tier | Method | Key exposure |
|---|---|---|
| Heartwood | Dedicated signing appliance (BUNKER_URI) | Key never leaves the signing device. Supports nsec-tree derivation, per-client permissions, and device-backed attestations. |
| Software bunker | Any NIP-46 bunker (BUNKER_URI, or bunker pair for signer apps) | Key held by a separate process. Never seen by bray. |
| ncryptsec | NIP-49 encrypted key (NOSTR_NCRYPTSEC) | Key encrypted at rest, decrypted in memory at startup. |
| Key file | File path (NOSTR_SECRET_KEY_FILE) | Key on disk, read once, env var deleted. |
| Env var | Inline secret (NOSTR_SECRET_KEY) | Key visible in process environment. Use only for development. |
Of the 261 registered tools, 50 are promoted: callable directly from the MCP tool list. Everything else is catalogued, so find it with search-actions and run it with execute-action (both are always available). Nothing that spends is promoted.
whoami, identity-switch, social-post, social-reply, social-feed, social-profile-get, dm-send, dm-read, dm-conversationzap-balance, relay-query, signet-badge, trust-score, verify-person, vault-readarticle-publish, article-read, article-list, search-notes, search-profiles, hashtag-feedbadge-create, badge-award, badge-accept, badge-list, community-create, community-feed, community-post, community-approve, community-list, calendar-create, calendar-read, calendar-rsvplisting-create, listing-read, listing-search, listing-closedispatch-send, dispatch-check, dispatch-reply, dispatch-ack, dispatch-status, dispatch-cancel, dispatch-refuse, dispatch-failure, dispatch-query, dispatch-propose, dispatch-capability-publish, dispatch-capability-discover, dispatch-capability-readThe dispatch tools are registered only when DISPATCH_IDENTITIES points at an identities file; without it 37 tools are promoted.
| Group | Tools | Key examples |
|---|---|---|
| Identity | 16 | whoami, identity-derive-persona, identity-switch, identity-prove, nip05-lookup |
| Social | 15 | social-post, social-reply, social-feed, contacts-follow, social-notifications |
| Direct Messages | 4 | dm-send, dm-read, dm-conversation |
| Trust | 22 | trust-attest, trust-ring-prove, trust-spoken-challenge, trust-attest-chain |
| Dispatch | 13 | dispatch-send, dispatch-check, dispatch-reply, dispatch-capability-discover |
| Relay | 13 | relay-query, relay-set, relay-discover, cast-spell, relay-health |
| Moderation | 16 | label-create, list-mute, list-bookmark, list-followset-create, moderation-filter |
| Marketplace | 16 | marketplace-discover, marketplace-call, listing-create, listing-search |
| Safety | 14 | canary-session-create, canary-group-create, canary-duress-signal, safety-activate |
| Blossom | 10 | blossom-upload, blossom-mirror, blossom-verify, blossom-repair |
| Privacy | 10 | privacy-commit, privacy-prove-range, privacy-prove-age, privacy-publish-proof |
| Zap | 9 | zap-send, zap-balance, zap-make-invoice, zap-decode |
| Wallet service | 5 | wallet-grant, wallet-grants, wallet-revoke, wallet-refill, wallet-serve |
| Vault | 9 | vault-create, vault-encrypt, vault-share, vault-rotate |
| Workflow | 7 | trust-score, verify-person, identity-setup, relay-health, feed-discover |
| Signet | 7 | signet-badge, signet-vouch, signet-credentials, signet-challenge |
| Communities | 5 | community-create, community-feed, community-post, community-approve |
| Badges | 4 | badge-create, badge-award, badge-accept, badge-list |
| Groups (NIP-29) | 20 | group-inspect, group-invite-create, group-forum-comment, group-delete |
| Articles | 3 | article-publish, article-read, article-list |
| Calendar | 3 | calendar-create, calendar-read, calendar-rsvp |
| Wiki | 3 | wiki-publish, wiki-read, wiki-list |
| Search | 3 | search-notes, search-profiles, hashtag-feed |
| Scheduling | 4 | post-schedule, post-queue-list, post-queue-cancel, publish-event |
| Community NIPs | 2 | nip-publish, nip-read |
| Utility | 23 | decode, validate-event, verify-event, gift-wrap, gift-unwrap, kind-info, nip44-encrypt, tombstone |
| Sync (NIP-77) | 1 | sync-plan (pull/push are explicit CLI and SDK operations) |
| Handler | 2 | handler-publish, handler-discover |
| Catalog | 2 | search-actions, execute-action |
Use search-actions to find tools by keyword, then execute-action to run them.
Protocol foundations: semantic event validation, NIP-77 reconciliation, and relay-scoped NIP-29 groups.
Dispatch lets AI agents collaborate over encrypted Nostr DMs. Any MCP-capable client can send structured tasks to other agents and receive results back.
13 message types: send, check, reply, ack, status, cancel, refuse, failure, query, propose, capability-publish, capability-discover, capability-read.
NIP-89 capability discovery: Agents publish what they can do. Other agents discover capabilities by topic, then route tasks to the right collaborator automatically.
dispatch-send("alice", "think", "Analyse the trade-offs of NIP-44 vs NIP-04")
dispatch-check() → inbox with pending tasks dispatch-reply(taskId, result) → send results back encrypted
All messages are NIP-44 encrypted. Recipients are resolved by name, NIP-05, npub, or hex.
Every tool that accepts a recipient uses universal identity resolution. You never need to look up hex pubkeys manually.
Accepted formats:
"alice" (resolved from your dispatch contacts)"alice@example.com" (HTTP lookup)"npub1abc..." (NIP-19 decode)"a1b2c3..." (64-character passthrough)Sign events now, publish later. Events are signed immediately with your current key, then held in a queue until the scheduled time.
post-schedule("Good morning!", "2026-04-01T08:00:00Z")
post-queue-list() → view pending scheduled posts post-queue-cancel(id) → cancel before it publishes
nostr-bray implements or integrates the following NIPs:
| NIP | What |
|---|---|
| NIP-01 | Events, signing, relay protocol |
| NIP-02 | Follow lists |
| NIP-05 | DNS identity (lookup, verify, relay hints) |
| NIP-09 | Event deletion |
| NIP-11 | Relay information |
| NIP-17 | Private DMs (gift wrap, default) |
| NIP-19 | bech32 encoding (npub, nsec, nprofile, nevent, naddr) |
| NIP-23 | Long-form articles (kind 30023) |
| NIP-22 | Schema-correct comments for group forums |
| NIP-29 | Relay-scoped groups, chat, forums, invitations and administration |
| NIP-32 | Labels |
| NIP-40 | Expiration tags |
| NIP-42 | Relay auth |
| NIP-44 | Encrypted payloads v2 |
| NIP-45 | Event counts |
| NIP-46 | Nostr Connect (bunker) |
| NIP-47 | Nostr Wallet Connect: pay BOLT-11 invoices, balance, invoices, and scoped spending connections over one wallet. NIP-44 v2 only |
| NIP-49 | Private key encryption (ncryptsec) |
| NIP-50 | Search |
| NIP-51 | Lists (mute, pin, follow sets, bookma
Nur der Anfang wird gezeigt; den Rest findest du im Repo