memory MCP server
com.borisinc/memoryborisinc.comstreamable-httpv1.0.0Scanned
Persistent agent memory paid per call via x402 USDC. Your wallet is your private memory namespace.
8 tools: 1 can delete or cancel things, 5 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the memory MCP server can do
The memory MCP server is published by borisinc.com, a domain the MCP Registry verified. It has 8 tools. It can delete or cancel things (1 tool: memory_forget) and create or change data (5 tools: memory_write, memory_export, memory_import, memory_write_free and 1 more). 2 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 17, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Deletes or cancels 1Claude Code: deny
memory_forgetDelete memories by id from YOUR namespace (or a namespace you hold a write/rw grant for).No findings
Why it is in this group
- The description's first verb is "delete": a word for removing or ending something.
Description, as the server wrote it Delete memories by id from YOUR namespace (or a namespace you hold a write/rw grant for). Max 100 ids per call. Paid: $0.001 per call via x402.
Changes things 5Claude Code: ask
memory_exportExport memories in YOUR payer-wallet namespace (up to 1000/call, newest first; use offset to page through namespaces >1000).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Export memories in YOUR payer-wallet namespace (up to 1000/call, newest first; use offset to page through namespaces >1000). Your data is yours. Includes superseded_by so history is exportable. Paid: $0.01 via x402.
memory_importBulk-write memories into YOUR namespace (max 200/call, content <=8k chars each).No findings
Why it is in this group
- The name "memory_import" says "import": a word for a change.
Description, as the server wrote it Bulk-write memories into YOUR namespace (max 200/call, content <=8k chars each). Accepts the exact shape memory_export emits, so a whole namespace can move in with one paid call. Embeds best-effort; missing embeddings are backfilled hourly. Paid: $0.01 flat via x402.
memory_statsFREE: count + last-write timestamp for any wallet namespace.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it FREE: count + last-write timestamp for any wallet namespace. Content is never returned on the free tier.
memory_writeStore a memory permanently.No findings
Why it is in this group
- The name "memory_write" says "write": a word for a change.
Description, as the server wrote it Store a memory permanently. Namespaced to YOUR paying wallet — your wallet is your private memory store. Semantic-indexed for later search. Optional supersedes=[ids] marks prior memories in your namespace as superseded by this one (excluded from search, still visible in export with their superseded_by id) — a Zep-style update-in-place without ever losing history. Paid: $0.001 per write via x402 (payment in _meta['x402/payment']).
memory_write_freeFREE (no payment): store a memory in YOUR namespace, proven by an EIP-191 personal_sign instead of an x402 payment.No findings
Why it is in this group
- The name "memory_write_free" says "write": a word for a change.
Description, as the server wrote it FREE (no payment): store a memory in YOUR namespace, proven by an EIP-191 personal_sign instead of an x402 payment. wallet_auth = base64 JSON {address,ts,signature} where signature = personal_sign of 'borismem-free:<address>:<ts>' (ts within 600s). Writes to the SAME namespace paid calls use. Capped at 1000 writes / rolling 30 days per wallet; over cap returns an error pointing to the paid tier.
Only reads 2Show 2 read-only tools
memory_searchSemantic search over YOUR stored memories (payer-wallet namespace).No findings
Why it is in this group
- The name "memory_search" says "search": a word for reading.
Description, as the server wrote it Semantic search over YOUR stored memories (payer-wallet namespace). Returns top-k by embedding similarity. Paid: $0.002 per search via x402.
memory_search_freeFREE (no payment): semantic search over YOUR namespace, proven by an EIP-191 personal_sign.No findings
Why it is in this group
- The name "memory_search_free" says "search": a word for reading.
Description, as the server wrote it FREE (no payment): semantic search over YOUR namespace, proven by an EIP-191 personal_sign. Same wallet_auth scheme as memory_write_free. Capped at 500 searches / rolling 30 days per wallet.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:22 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (1 destructive, 5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mem.borisinc.com/mcp: tools/list returned 8 tools to an anonymous client, including memory_forget (destructive), memory_write (write), memory_export (write), memory_import (write), memory_write_free (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http memory https://mem.borisinc.com/mcpclaude mcp add --transport http memory https://mem.borisinc.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__memory__memory_search",
"mcp__memory__memory_search_free"
],
"ask": [
"mcp__memory__memory_write",
"mcp__memory__memory_export",
"mcp__memory__memory_import",
"mcp__memory__memory_write_free",
"mcp__memory__memory_stats"
],
"deny": [
"mcp__memory__memory_forget"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as memory. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.borisinc/memory/verify?hash=e690f3b8eedba42edf05aca0fb6bf2bdf12a9f982c5c8f5171f58001374456f5" | jq -e '.changed == false'Pinned hash e690f3b8eedb, from Nov 17, 2026, 02:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.borisinc/memory/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.borisinc/memory)Source: MCP Registry. Synced Oct 21, 2026, 17:52 UTC.
memory MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the memory MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the memory MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: memory_forget.
Can the memory MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the memory MCP server have?
- 8 tools: 1 destructive, 5 write, 2 read. memory_forget, memory_write, memory_export, memory_import, memory_write_free, memory_stats, memory_search and memory_search_free.
Does the memory MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the memory MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the memory MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.