Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Trust-aware Nostr for AI agents -- 235 tools covering social, DMs, zaps, trust, and identity
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
NOSTR_SECRET_KEY, NOSTR_RELAYS, NWC_URILos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en claude_desktop_config.json
{
"mcpServers": {
"bray": {
"command": "npx",
"args": [
"-y",
"nostr-bray"
],
"env": {
"NOSTR_SECRET_KEY": "your-value",
"NOSTR_RELAYS": "your-value",
"NWC_URI": "your-value"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add bray --env NOSTR_SECRET_KEY=your-value --env NOSTR_RELAYS=your-value --env NWC_URI=your-value -- npx -y nostr-brayCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"bray": {
"command": "npx",
"args": [
"-y",
"nostr-bray"
],
"env": {
"NOSTR_SECRET_KEY": "your-value",
"NOSTR_RELAYS": "your-value",
"NWC_URI": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"bray": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"nostr-bray"
],
"env": {
"NOSTR_SECRET_KEY": "your-value",
"NOSTR_RELAYS": "your-value",
"NWC_URI": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026
El nombre en el registro se verificó con el dominio forgesworn.dev (el registro comprueba quién es dueño del dominio)
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: NOSTR_SECRET_KEY, NOSTR_RELAYS, NWC_URI
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (1.27.7) llegó al registro hace 7 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Binggio
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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.
Governed answers from your data: approved meanings only, refusals instead of guesses.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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
Solo se muestra el principio; lee el resto en el repo