MemoryPlugin
REMOTE · WWW.MEMORYPLUGIN.COM · 2 COMPONENTS
Give every AI you use one shared, permanent memory. Store once, recall in whichever AI you open.
Available components
Last scanned (4 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Memory and Knowledge
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1823 tokens (~130/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 8 Aug 26 0
- Transport: unverified → pass ▲ security
- Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://www.memoryplugin.com/api/mcp/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.memoryplugin.com | CN=YR2,O=Let's Encrypt,C=US | 12 Oct 2026 | 10 Jan 2027 | RSA 2048 | SHA256-RSA | 5db353bbe60823907ec16f6e86a84d80158 |
| SANs: www.memoryplugin.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.memoryplugin.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| memoryplugin.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://www.memoryplugin.com/.well-known/oauth-protected-resource"
Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://www.memoryplugin.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-frame-options | SAMEORIGIN |
Protected resource metadata
| Document | https://www.memoryplugin.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://www.memoryplugin.com |
| Authorisation server | https://www.memoryplugin.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.memoryplugin.com/api/mcp/mcp | Verified | 200 | |
| http (plaintext) | http://www.memoryplugin.com/api/mcp/mcp | HTTPS enforced | 308 | https://www.memoryplugin.com/api/mcp/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
chat_history_overview Chat history overview ~68
Returns an AI-generated overview of the user, built from the chat history they have synced into their MemoryPlugin account. Use when the user asks what you know about them or asks you to load their background. If no overview exists yet, the user can generate one from their MemoryPlugin dashboard.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_bucket Create bucket ~52
Create a new bucket to organize memories. Buckets are folders like 'Work', 'Personal', 'Health'. Ask the user for a name if not specified.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Name for the new bucket |
No output schema declared.
No examples provided.
export_conversation Export conversation ~126
Download the complete transcript of a past conversation as a machine-readable JSON file. Returns a temporary download URL (expires in 15 minutes, no auth needed) that you fetch yourself to get the full conversation as structured messages (role, content, timestamp). Use when a transcript is too long to read inline, or when you need it as a file for analysis or scripting. To read a short transcript directly, use get_full_conversation instead. Requires the conversationId from recall_chat_history's sources array.
| Name | Type | Req | Description |
|---|---|---|---|
| conversationId | string | yes | Conversation ID from the recall_chat_history sources array |
No output schema declared.
No examples provided.
get_conversation_summary Get conversation summary ~86
Get details of a specific past conversation. For short conversations (<5K tokens), returns the full transcript. For longer conversations, returns an AI-generated summary. Use when the user wants to dive deeper into a conversation returned by recall_chat_history. Requires the conversationId from that tool's sources array.
| Name | Type | Req | Description |
|---|---|---|---|
| conversationId | string | yes | Conversation ID from the recall_chat_history sources array |
No output schema declared.
No examples provided.
get_full_conversation Get full conversation ~68
Get the complete transcript of a specific past conversation. Returns all messages in the conversation without summarization. Use when you need the raw conversation content. Requires the conversationId from recall_chat_history's sources array.
| Name | Type | Req | Description |
|---|---|---|---|
| conversationId | string | yes | Conversation ID from the recall_chat_history sources array |
No output schema declared.
No examples provided.
get_memories_and_buckets Get memories and buckets ~118
Retrieve the user's saved memories from MemoryPlugin, optionally filtered by bucket. Also returns the list of available buckets. Use when the user asks what you know about them or refers to something they saved earlier.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Whether to fetch all memories |
| bucketId | number | – | Optional bucket ID to filter memories |
| count | number | – | Number of memories to retrieve (default: 10) |
| latest | boolean | – | Whether to fetch only latest memories |
| query | string | – | Optional search query |
No output schema declared.
No examples provided.
list_bucket_categories List bucket categories ~145
List AI-generated categories within a bucket. When users activate Smart Memory, their memories are automatically organized into topic-based categories. Returns for each category: - name: Category title - summary: Dense overview of core facts, preferences, current projects, key context (~200 words) - additionalInfo: Lists specific topics available in this category and suggests when to load the full memories - memoryCount: Number of memories in category Also returns recentMemories: the 30 most recent memories in the bucket. Use the summary and additionalInfo to decide if/when to load full memories via list_category_memories.
| Name | Type | Req | Description |
|---|---|---|---|
| bucketId | string | yes | Bucket ID to get categories for |
No output schema declared.
No examples provided.
list_buckets List buckets ~35
List the user's memory buckets. Buckets are organizational folders for memories (e.g., 'Work', 'Personal', 'Health').
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_category_memories List category memories ~91
Get all memories within a specific Smart Memory category. Use when a category's summary (from list_bucket_categories) indicates it's relevant to the current conversation. The categoryId persists across conversations.
| Name | Type | Req | Description |
|---|---|---|---|
| bucketId | string | yes | Bucket ID containing the category |
| categoryId | string | yes | Category ID to get memories from |
| limit | number | – | Number of memories to retrieve (default: 20) |
No output schema declared.
No examples provided.
recall_chat_history Recall chat history ~474
Search and synthesize context from the user's past AI conversations that they have synced into their MemoryPlugin account. WHEN TO USE: When the user asks about their past decisions, patterns, preferences, relationships, projects, or a specific earlier conversation. HOW TO USE: - For simple lookups: a single query is fine - For complex/multifaceted topics: use parallel queries (via 'queries' array) approaching from different angles - timeline, emotions, people, decisions, outcomes, etc. - Set maxTokens per query (300-1000) to control how much context is returned. More tokens = richer detail but consumes more conversation window. - Use 'before'/'after' (ISO 8601 dates like "2025-01-15" or "2025-01-15T10:30:00Z") to constrain results to a date range. Bare dates are interpreted in UTC and are inclusive on both ends. - Use 'mode: "quality"' for slower but more thorough recall on hard or ambiguous queries; defaults to 'speed'. - If unclear how much context to fetch, ask the user. Returns synthesized summaries (not raw conversation logs) with source metadata for citations.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Optional ISO 8601 date lower bound (inclusive). Bare dates like "2025-01-15" mean start-of-day UTC. |
| before | string | – | Optional ISO 8601 date upper bound (inclusive). Bare dates like "2025-01-15" mean end-of-day UTC. |
| conversationContext | string | – | Optional one-sentence summary of what the user is currently working on, to focus retrieval. Do not pass message text. |
| maxTokens | number | – | Maximum tokens to allocate for injected context (defaults to 600, hard cap 2000). |
| mode | string | – | Retrieval mode. 'speed' (default) uses the fast path. 'quality' uses GPT-OSS planning, temporal exploration, and DeepSeek evidence judgment for more thorough recall at higher latency. |
| platform | string | – | Optional hint about the downstream chat platform. |
| queries | array | – | Array of query objects to process in parallel (max 15). |
| query | string | – | Natural-language description of what the assistant is currently helping with. |
No output schema declared.
No examples provided.
search_memories Search memories ~90
Search the user's saved memories using hybrid semantic + keyword search. Returns matching memories ranked by relevance. MemoryPlugin stores memories the user wants to persist across AI conversations. Use when looking for specific saved information.
| Name | Type | Req | Description |
|---|---|---|---|
| bucketId | string | – | Optional bucket ID to limit search scope |
| limit | number | – | Number of memories to retrieve (default: 10) |
| query | string | yes | Search query |
No output schema declared.
No examples provided.
search_uploaded_files Search uploaded files ~155
Search documents the user has uploaded to their MemoryPlugin document library (not files uploaded directly to this conversation). MemoryPlugin file buckets store documents persistently across all AI chats. Returns relevant text passages with source file and page info. Use when: - User explicitly mentions their MemoryPlugin documents - User asks about "my files" or "my documents" and there are no files in the current conversation - If unsure whether they mean MemoryPlugin files or conversation files, ask to clarify
| Name | Type | Req | Description |
|---|---|---|---|
| bucketId | number | – | Optional file bucket ID to limit search scope |
| query | string | yes | Search query text |
| topK | number | – | Number of results to return (default: 5, max: 20) |
No output schema declared.
No examples provided.
store_memory Store memory ~124
Save information to the user's MemoryPlugin account. MemoryPlugin lets users build persistent memory across AI conversations. WHEN TO USE: When the user asks to remember something, or confirms that a specific fact, preference, decision, or project detail from the conversation should be kept for later. Save only that item. Ask the user which bucket to save to if unclear. Buckets are organizational folders (e.g., 'Work', 'Personal', 'Health').
| Name | Type | Req | Description |
|---|---|---|---|
| bucketId | number | – | Optional bucket ID to store the memory in |
| text | string | yes | The memory text to store |
No output schema declared.
No examples provided.
update_or_move_memories Update or move memories ~191
Edit a single memory's text or bucket, or move multiple memories to a different bucket. WHEN TO USE: When the user wants to correct, update, or reorganize their saved memories. Single memory: provide memoryId with optional text and/or bucketId/bucketName. Bulk move: provide memoryIds array with bucketId or bucketName. Bucket can be specified by ID (number) or name (string). If a name is given and no bucket exists with that name, one is created automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| bucketId | number | – | Target bucket ID |
| bucketName | string | – | Target bucket name (auto-creates if missing) |
| memoryId | string | – | Encoded memory ID for single edit/move |
| memoryIds | array | – | Array of encoded memory IDs for bulk move (max 100) |
| text | string | – | New text content (single memory only) |
No output schema declared.
No examples provided.
How do I install the MemoryPlugin MCP server?
MemoryPlugin is a hosted endpoint at https://www.memoryplugin.com/api/mcp/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.memoryplugin.com
claude mcp add --transport http com-memoryplugin-memory 'https://www.memoryplugin.com/api/mcp/mcp'
What is the MemoryPlugin MCP server?
MemoryPlugin is an MCP server listed in the public MCP registry as com.memoryplugin/memory. Give every AI you use one shared, permanent memory. Store once, recall in whichever AI you open. This page covers its hosted endpoint (https://www.memoryplugin.com/api/mcp/mcp).
Is the MemoryPlugin MCP server safe to use?
MemoryPlugin scores 93 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MemoryPlugin MCP server expose?
MemoryPlugin exposes 14 tools: store_memory, list_buckets, create_bucket, get_memories_and_buckets, list_bucket_categories, and 9 more. Their descriptions and schemas cost roughly 1,823 tokens of context every time the server is loaded.
Does the MemoryPlugin MCP server require authentication?
Yes. MemoryPlugin asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the MemoryPlugin MCP server still maintained?
MemoryPlugin is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.