Send in your browser
Choose file or note, expiry, one-time access, and optional recipient verification in Muse. Add the content and recipient address in NexFade. The full link stays there for you to share.
NexFade for Muse
Secure sends and file requests, finished in NexFade.
Ask Muse to start a one-time file or note send, request files from a client, or check whether a link was opened. Muse hands creation to your NexFade browser, where you enter content and recipient details and receive the complete link.
Availability
Public Muse directory review is pending.
The connector will be installable from Muse only after Meta approves and lists it.
Request files securely
NexFade opens its request form. Your browser creates the owner keypair and displays the private management link. Muse never receives that link or key.
Manage a link
Muse can list your link IDs and minimal status. To revoke one, it opens a signed-in NexFade page where you review the link and confirm. Muse cannot revoke it directly.
Connector details
Existing MCP over HTTPS
The planned endpoint is https://mcp.nexfade.com/mcp. Connection uses user-scoped OAuth with PKCE. Muse can list and check owned links with nexfade.links.read, open browser handoffs with nexfade.links.create, and open a NexFade revocation confirmation page with nexfade.links.revoke. Creation tools accept choices only; the NexFade browser completes the send or request. The endpoint becomes available after deployment; Muse directory access follows Meta review.
Privacy boundary
Keep sensitive details in NexFade.
NexFade encrypts files and notes in your browser. Do not type files, notes, recipient addresses, passwords, keys, or complete share links into Muse. Anything you enter into Muse is processed in Meta's environment and may remain in Muse history after disconnecting the connector.