Privacy & Security Standards
The Memolink MCP server is designed to provide your AI assistants with secure, context-aware access to your personal intelligence layer while maintaining absolute data sovereignty.
Secure Auth
Encrypted communication using standard Bearer tokens or OAuth 2.0 flow.
Zero Data Persistence
The MCP server does not store any of your profile or memo data locally.
Full Sovereignty
You control exactly which AI clients can connect to your workspace.
What information is accessed?
When you connect an AI assistant via Memolink MCP, the following resources become available to the model for reasoning purposes:
- Memos: Search results and full content of your research notes.
- Goals: Your active and completed research objectives.
- Tags: Organizational categories used for context mapping.
- Daily Summaries: Aggregated journal data for temporal context.
Security & Transmissions
All data transmitted between your AI client and the Memolink MCP server is encrypted via TLS/SSL. We never transmit your authentication credentials in plain text.
The MCP server acts strictly as a stateless proxy. It fetches your data from the Memolink API on demand and passes it to your local LLM runtime (e.g., Claude Desktop, Cursor). No cache of your personal data is maintained on the MCP server infrastructure.
User Consent & Revocation
By adding the Memolink MCP server to your AI environment, you explicitly consent to allowing the specified AI model to read the data provided by our tools for the purpose of assisting you in your tasks.
You may revoke this consent at any time by simply removing the Memolink MCP server configuration from your IDE or Claude Desktop application.
© 2026 Opstin Technologies. All rights reserved.