nostr-bray (forgesworn/bray) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

Back to MCP Trust Indexm8ven
C
Emerging
74/100
2 months ago

nostr-bray

Trust-aware Nostr MCP server. 236 tools for identity, social, DMs, trust scoring, AI-to-AI dispatch, Lightning payments, privacy proofs, and encrypted vaults. NIP-46 bunker auth; keys never leave the signing device.

→ forgesworn/bray· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

forgesworn

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
244 tools verified — handlers match their declared behaviour
135 read-only tools verified — handlers contain no write/delete/exec
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 6 credentials: BRAY_HTTP_TOKEN, BRIDGE_SECRET, CLIENT_SECRET, NOSTR_NCRYPTSEC_PASSWORD, NOSTR_SECRET_KEY, PHOENIXD_PASSWORD
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

lowws@8.20.0GHSA-58qx-3vcg-4xpx

ws: Uninitialized memory disclosure

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configALLOW_CLEARNET_WITH_TOR
configBIND_ADDRESS
configBRAY_ALLOW_PRIVATE_RELAYS
configBRAY_CONFIGSearch order: env var > $XDG_CONFIG_HOME/bray/config.json > ~/.nostr/bray.json.
🔐 secretBRAY_HTTP_TOKEN
configBRAY_INPUT_DIRS
configBRAY_WALLETS_FILE
🔐 secretBRIDGE_SECRET
configBUNKER_URI"": "bunker://...",
configBUNKER_URI_FILEPath to bunker URI file
🔐 secretCLIENT_SECRET
configDISPATCH_IDENTITIES
configNIP04_ENABLEDSet 1 to enable legacy NIP-04 DMs
configNOSTR_BRAY_OUTPUT
configNOSTR_NCRYPTSECncryptsec NIP-49 encrypted key () Key encrypted at rest, decrypted in memory at startup.
configNOSTR_NCRYPTSEC_FILE
🔐 secretNOSTR_NCRYPTSEC_PASSWORDPassword for ncryptsec
configNOSTR_NCRYPTSEC_PASSWORD_FILE
configNOSTR_RELAYS"": "wss://relay.damus.io,wss://nos.lol"
🔐 secretNOSTR_SECRET_KEY"": "nsec1...",
configNOSTR_SECRET_KEY_FILEKey file File path () Key on disk, read once, env var deleted.
configNWC_URI
configNWC_URI_FILE
🔐 secretPHOENIXD_PASSWORD
configPHOENIXD_URL
configRELAY
configTOR_PROXYSOCKS5h proxy for Tor
configTRANSPORTstdio (default) or http
configTRUST_CACHE_MAX
configTRUST_CACHE_TTL
configTRUST_MODE
configVAULT_EPOCH_LENGTH
configVEIL_CACHE_MAX
configVEIL_CACHE_TTL
configXDG_CONFIG_HOMESearch order: BRAY_CONFIG env var > $/bray/config.json > ~/.nostr/bray.json.
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

235/244 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

244/244 tools missing one or more hints — search-actions (missing: destructiveHint, idempotentHint, openWorldHint); execute-action (missing: readOnlyHint, destructiveHint, idempotentHint); dispatch-send (missing: destructiveHint, idempotentHint, openWorldHint), +241 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

223/244 tool handlers declare input schemas (91%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 2/244 tool handlers wrap calls in try/catch (1%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

Only 44/244 tools referenced in tests (18%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

1 child_process call — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/forgesworn-bray-27gfti)](https://m8ven.ai/mcp/forgesworn-bray-27gfti)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 33eb25ecf273b9dcaba2b19fb0af2df51f377a36
code hash: ee7f76e2b79dd33ac73b4b3da2390ec8b351852692b51171363888e056bb24ac
verified: 6/13/2026, 10:52:29 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client