Creation
Local input stays out of model-facing tools.
Claude surfaces with approved MCP App capabilities show the NexFade local-encryption interface. Mobile or unsupported clients use a browser handoff.
NexFade for Claude
Create and manage encrypted links without putting readable content in tool arguments.
NexFade creates revocable, expiring links for files and notes. Choose an expiration, optionally burn after the first intentional open or require recipient-email verification, then check or revoke links later.
Availability
Connectors Directory submission is pending production beta and review.
The remote MCP server and cross-platform MCP App are prepared for Claude.ai and Claude Desktop directory review.
Management
Minimal operational metadata only.
The connector exposes minimal owned-link status and revocation tools through scoped OAuth; it does not read Claude memory or unrelated attachments.
Fallback
Browser handoff preserves the boundary.
If the host cannot render the NexFade interface or run local encryption, it opens the NexFade website with nonsensitive defaults only. Content is never copied into a fallback tool call.
Trust boundary
What local encryption does—and does not—mean.
NexFade encrypts content in its interface before ciphertext upload and does not receive the AES key or complete fragment-bearing link. The interface is displayed by Claude, so that host platform's privacy terms also apply.
Restricted data is not allowed in marketplace integrations.
Do not use the integration for payment-card data, protected health information, government IDs, passwords, API keys, MFA or one-time codes, or other authentication secrets.
Policies and support