nostr-bray@1.27.7
VERIFIED· not startedPublisher claims: "Trust-aware Nostr for AI agents -- 235 tools covering social, DMs, zaps, trust, and identity" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
NOSTR_NCRYPTSEC_PASSWORDNOSTR_SECRET_KEYNOSTR_SECRET_KEY_FILEConfiguration, not credentials: ALLOW_CLEARNET_WITH_TOR, BIND_ADDRESS, BRAY_CONFIG, BRAY_WALLETS_FILE, BUNKER_URI, BUNKER_URI_FILE, DISPATCH_IDENTITIES, NIP04_ENABLED, NOSTR_BRAY_OUTPUT, NOSTR_NCRYPTSEC, NOSTR_NCRYPTSEC_FILE, NOSTR_RELAYS, NWC_URI, NWC_URI_FILE, TOR_PROXY, TRANSPORT, TRUST_CACHE_MAX, TRUST_CACHE_TTL, TRUST_MODE, VAULT_EPOCH_LENGTH, VEIL_CACHE_MAX, VEIL_CACHE_TTL- Where it talks to
- no vendor host named in the codeAlso githubusercontent.com — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names githubusercontent.com as well as its own vendor. The guard injects NOSTR_NCRYPTSEC_PASSWORD, NOSTR_SECRET_KEY, NOSTR_SECRET_KEY_FILE only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-20 and scored it 93/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 15 s · 2 scenarios · 0 deviationsStatic findings
stdio_command: z.string().optional().describe('stdio transport command (e.g. "npx nostr-bray")'),Fix: Pin versions and sources; vendor anything fetched at install time.No other findings across 9,360 lines in 81 files.
Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for nostr-bray@1.27.7 as of 47 min ago. This is the package itself, not its dependencies.