MCPNews

The Model Context Protocol ecosystem, verified

Current spec 2026-07-28

bray

Earlier Revision Publisher unverified Confidence: Good (0.85)

bray is an MCP server published by forgesworn.dev, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. Last verified 2026-08-20.

Does bray support the current MCP specification (2026-07-28)?

Not yet confirmed. bray is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.

Is bray a first-party (official) MCP server?

Undetermined. We have not verified the publisher relationship for bray (as of 2026-08-20).

How do I connect to bray?

bray is available via the package npm:nostr-bray, the official MCP Registry under dev.forgesworn/bray, the source repository at https://github.com/forgesworn/bray. Authentication: unknown. Transports: stdio.

Does bray support MCP revision 2025-11-25?

Yes. bray supports MCP revision 2025-11-25 (checked 2026-08-20).

Does bray support MCP revision 2026-07-28?

No. bray was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).

When were bray's facts last verified?

2026-08-20. Each fact on this page links to the sources used to verify it.

Trust-aware Nostr for AI agents -- 235 tools covering social, DMs, zaps, trust, and identity

Which MCP spec revisions does bray support?

bray has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.

Spec revision Status Last checked Evidence
MCP 2025-11-25 Supported Source
MCP 2026-07-28 Not supported Source

How widely adopted is bray?

Not ranked in The MCP 500: insufficient public data (coverage floor not met) (snapshot ). The Adoption Index measures public signals only; it says nothing about quality.

Repository and package signals for bray

Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.

Repository as of

Stars
0
Forks
0
Last pushed
(39 days ago)
Created
Open issues
2
Primary language
TypeScript
License (repository)
MIT
Continuous integration
Present
Tests
Present
Security policy
Present

Declared topics: ai-agent, attestations, bunker, dominion, identity, lightning, mcp, mcp-server, model-context-protocol, nip-46, nostr, nostr-wallet-connect, nwc, ring-signature, shamir, signet, trust, typescript, web-of-trust — author-declared on the repository, not our taxonomy.

Package (npm) as of

Latest version
3.3.0
Last published
First published
Releases
82
License (package)
MIT
Maintainers
1
Direct dependencies
19
Unpacked size
2.6 MB
Registry signature
Signed
Build provenance
Attested

How was this verified, and what are the sources?

Verified · method: sdk-protocol-constant · confidence 0.85 (Good).

  1. Official MCP Registry record for dev.forgesworn/bray at version 1.27.7 - lists package npm:nostr-bray and repository https://github.com/forgesworn/bray - accessed
  2. npm registry metadata for nostr-bray at published version 3.2.2, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.30.0 - accessed
  3. Published artifact of @modelcontextprotocol/sdk@1.30.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed