Memoryoracle

io.tooloraclePublished by tooloracle.ioOfficial publisherv1.0.0Updated Oct 27, 2026

MemoryOracle - 10 agent memory tools: vector store, recall, summarization, redaction.

The publisher's own server: Accessoracle

VerifiedStreamable HTTPWeb executableDatabasesKnowledge & Memory

Overview

AI-generated overview

MemoryOracle is a remote MCP server giving AI agents persistent, searchable long-term memory: store, query, update, summarize and delete facts across sessions.

What you can do
  • Store, update and browse memories by category, importance, recency or access frequency, with automatic deduplication and version history
  • Search stored memories with full-text ranking and recency boost, isolated per namespace
  • Capture end-of-session summaries that extract facts, decisions and action items
  • Permanently delete memories by ID, category, age or everything, and export all memories as JSON
  • Check memory statistics and service health, and cross-reference a memory against an external trust layer
When to use it
Useful when an assistant should remember user preferences, project history, decisions or business rules between sessions and across clients, instead of losing context whenever the chat or app restarts.
Requirements
A remote endpoint reached over streamable HTTP; the README shows connecting through the mcp-remote bridge run with npx, so Node.js is needed for that route. No authentication, environment variables or headers are declared in the manifest.
Before you install
Stored memories persist on a third-party service and may include user preferences, decisions and portfolio data; deletion is permanent. The README also lists a separate pay-per-call endpoint with per-tool prices, so check which endpoint you connect to and whether calls incur charges.

Installation

In SourceWeft

  1. Open Memoryoracle in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.tooloracle%2Fmemoryoracle/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "memoryoracle": {
      "type": "http",
      "url": "https://tooloracle.io/memory/mcp/"
    }
  }
}

README

MemoryOracle

Persistent long-term memory for AI agents. Agents never forget.

10 tools. SQLite FTS5 full-text search. Per-namespace isolation. GDPR-compliant forget. Cross-references with FeedOracle Trust Layer.

npx -y mcp-remote https://mcp.feedoracle.io/memory/mcp/

The problem

Every MCP tool call is stateless. When Claude Desktop restarts, when Cursor closes, when the session ends — the agent forgets everything. No user preferences, no project history, no learned rules, no portfolio tracking.

MemoryOracle gives agents a persistent, searchable memory that survives restarts, works across clients, and gets more valuable over time.

Tools

ToolWhat it does
store_memoryStore a fact, preference, decision, or rule. Deduplicates automatically.
query_memoryFull-text search with BM25 ranking and recency boost
update_factUpdate a memory with new info. Preserves version history (last 10 changes)
forgetPermanently delete by ID, category, age, or everything. GDPR Art. 17
summarize_sessionEnd-of-session capture: summary + extracted facts, decisions, action items
list_memoriesBrowse with filters: category, importance, recency, access frequency
cross_referenceVerify a memory against FeedOracle Trust Layer evidence
memory_statsDashboard: count, storage, categories, most accessed, recent
export_memoriesExport all as JSON. GDPR Art. 20 data portability
health_checkService status

Memory categories

CategoryWhen to use
factVerified information: "USDC is MiCA authorized"
preferenceUser/agent preferences: "Conservative allocation, no USDT"
decisionDecisions made: "Blocked USDT for EU clients"
observationPatterns noticed: "RLUSD peg stable for 30 days"
ruleBusiness rules: "Never recommend assets with peg deviation > 2%"
sessionSession summaries with linked facts
portfolioPortfolio positions and allocations
action_itemOpen tasks: "Check RLUSD status in April"

Example: Compliance agent workflow

Session 1 — Agent does MiCA compliance checks:

json
{"name": "store_memory", "arguments": {  "content": "USDT blocked for EU — MiCA NOT AUTHORIZED. Preflight: STOP.",  "category": "decision", "importance": 10,  "tags": ["usdt", "mica", "blocked"],  "namespace": "compliance-bot"}}

Session 2 — Next day, agent remembers:

json
{"name": "query_memory", "arguments": {  "query": "USDT EU compliance status",  "namespace": "compliance-bot"}}

→ Instantly recalls the decision from yesterday. No re-checking needed.

End of session — Auto-capture:

json
{"name": "summarize_session", "arguments": {  "summary": "Reviewed stablecoin portfolio. USDT blocked. RLUSD pending.",  "key_facts": ["USDC authorized", "EURC authorized", "USDT blocked"],  "decisions": ["Block USDT for EU"],  "action_items": ["Check RLUSD in April 2026"],  "namespace": "compliance-bot"}}

Why this is different

FeatureMemoryOracleOthers
SearchFTS5 BM25 ranking + recency boostBasic keyword
Categories8 structured typesFlat key-value
Session captureAuto-extracts facts, decisions, actionsManual only
Trust LayerCross-reference with signed evidenceNone
GDPRArt. 17 forget + Art. 20 exportUsually missing
NamespacesPer-agent isolationShared global
HistoryVersion tracking (last 10 changes)Overwrite
TTLAuto-expiry with configurable hoursNone

x402 Pay-per-call

POST https://tooloracle.io/x402/memory/mcp/
ToolUnitsPrice
store_memory2$0.02
query_memory5$0.05
summarize_session8$0.08
cross_reference5$0.05
list_memories3$0.03
update_fact2$0.02
forget1$0.01

Connect

json
{  "mcpServers": {    "memory": {      "command": "npx",      "args": ["-y", "mcp-remote", "https://mcp.feedoracle.io/memory/mcp/"]    }  }}

Part of ToolOracle

MemoryOracle is part of ToolOracle — 50+ MCP servers, 530+ tools. Powered by FeedOracle compliance infrastructure.

The memory layer that makes Decision Preflight, Trust Layer, ISO 20022, and every other tool exponentially more valuable.

Read More

📝 We Built an AI Agent That Runs 24/7, Never Forgets, and Checks Its Own Work — How Memory + Scheduler + Decision Preflight work together as one integrated autonomous agent stack. Real tool outputs, no theory.

License

MIT

Source: README.md at commit 8e2873a

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Tooloracle integrations