Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Nothing to run from here
Memory is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
trust score
14
downloads a day
local
runs on your machine
278
downloads in 30d
What it does
Persistent memory for AI agents - save once, recall in every session, project and tool.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'RAGIONEX_MEMORY_API_KEY=${RAGIONEX_MEMORY_API_KEY}' --transport stdio ragionex-memory-mcp '--' npx -y @ragionex/memory-mcp
# 2 — ask your agent for something these tools do
# ragionex_memory_connection, ragionex_save_memory, ragionex_recall_memory and 8 more
It needs RAGIONEX_MEMORY_API_KEY: this reads it from your environment, so export it first.
Memory costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
RAAll 1 server
ragionex1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Memory as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads RAGIONEX_MEMORY_API_KEY (Ragionex Memory API key. Get one at https://app.ragionex.com/keys) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx RAGIONEX_MEMORY_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'RAGIONEX_MEMORY_API_KEY=${RAGIONEX_MEMORY_API_KEY}' --transport stdio ragionex-memory-mcp '--' npx -y @ragionex/memory-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: RAGIONEX_MEMORY_API_KEY — Ragionex Memory API key. Get one at https://app.ragionex.com/keys. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Show the selected Vault, every Vault this account can use with its name and ID, permissions, the project file path (config_file), and local pending or blocked save IDs. Use it to find a Vault ID before writing the project file at the user's request. Recovery paths contain local data that needs…
No parameter schema on file.
Save one durable topic as a new record in the selected Vault. Requires create permission. Recall the topic first: when a related record exists, update it with ragionex_update_memory instead of saving a copy. Content is English. The priority rule in the user's agent rules file defines save and…
No parameter schema on file.
Search records in the selected Vault. Requires read permission. Use it whenever you need a fact about the user or their work, before you ask the user, and before every save to find a related record. Send one complete English question in query, written from the whole conversation; full questions…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | One complete English question for one need, written from the whole conversation, 5-512 characters: 'which code editor does the user prefer?' matches far better than 'user editor'. Separate needs get s |
| page | integer | no | Which results page to return for this query and dates. Omit or pass null for the first page. |
| start_date | yes | — | |
| end_date | yes | — |
Browse records in the selected Vault, most recently created first. Requires read permission. Use it when there is no topic, including requests to browse a date window. Optional start_date and end_date use ISO 8601 creation dates. limit is the page size, up to 100; pass next_cursor as cursor with…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_date | yes | — | |
| end_date | yes | — | |
| limit | integer | no | Maximum records per page, most recent first. Default 50, maximum 100. Use next_cursor to continue with the same filters. |
| cursor | string | no | The next_cursor from the previous page. Omit or pass null for the first page; keep the same date filters when continuing. |
Read full records by ID within the selected Vault. Requires read permission. Returns id, vault_id, content, created_at, updated_at, status, revision, created_by and updated_by (account IDs). Use the returned revision as expected_revision for an update, and read again after a revision_conflict. A…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ids | array | yes | Record IDs from recall or list in the selected Vault. |
Replace the content of a record in the selected Vault. Requires update permission. Send the record ID, the complete new English content and expected_revision, the revision from your latest read. The new content replaces the old, so keep every detail that still holds. Changed content is processed…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | yes | Record ID in the selected Vault. | |
| expected_revision | integer | yes | The revision from your latest read of this record. Reread after a conflict; never guess. |
| content | yes | The complete replacement content in English. It replaces the current content, so include every detail that still holds. |
Move the specified record IDs to trash in the selected Vault. Requires delete permission. Use it for records that are wrong, repeated or no longer true, and for records the user asks to remove. Records can be restored for 30 days. Returns the number moved; it does not delete or select a Vault.…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ids | array | yes | Record IDs to move to trash. |
List records in the selected Vault's trash, most recently deleted first. Requires read permission. Records are restorable for 30 days. Content is a preview; use ragionex_memory_versions with the record ID and revision to read it in full. This tool cannot permanently delete records or empty the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Records per page, up to 100. Omit or pass null for 50. |
| cursor | string | no | The previous page's next_cursor. Omit or pass null for the first page. |
View retained versions of a live or trashed record in the selected Vault. Requires read permission. Without revision, returns a page of previews, newest version first. With revision, returns that version's full content. Old versions are kept for 30 days after replacement. Read the chosen version…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | yes | Record ID in the selected Vault, from a live record or the trash. | |
| revision | integer | no | Version number to read in full. Omit or pass null to list versions. |
| limit | integer | no | Versions per page when listing, up to 100. Omit or pass null for 25. |
| cursor | string | no | The version list's next_cursor. Omit or pass null for the first page or a full version read. |
Restore a trashed record or a retained older version in the selected Vault. Requires update permission. Send the current revision from the trash or version history as expected_revision. For a live record, choose revision after reading that version's full content. For a trashed record, omit…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | yes | Record ID in the selected Vault to restore. | |
| expected_revision | integer | yes | The current record revision from the trash or version history. Never guess or increment it yourself. |
| revision | integer | no | The retained version to restore. Required for a live record; omit or pass null to restore a trashed record's last content. |
Check a record's processing status in the selected Vault. Requires read permission. Returns processing, ready, or failed and any public guidance. Use for an accepted save with a record ID. For a locally queued operation ID, use ragionex_memory_connection.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | yes | Record ID to check. |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Memory or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 93 / 100
Release 0.7.0 · scanned 31 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings1 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digest0c8ae4081129e33a943b81391636d24de97a291b93bdace0115ff2b5ea70f5ba
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (11 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| ragionex_memory_connection | no tags | |
| ragionex_save_memory | state-write | state-write: declares readOnlyHint: false |
| ragionex_recall_memory | no tags | |
| ragionex_list_memories | untrusted-input | untrusted-input: keyword "browse" |
| ragionex_view_memory | no tags | |
| ragionex_update_memory | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| ragionex_delete_memory | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| ragionex_list_trash | no tags | |
| ragionex_memory_versions | no tags | |
| ragionex_restore_memory | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| ragionex_memory_status | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest0c8ae4081129e33a
Scanned2026-10-31
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.7.0. Pin a release below and the command asks for exactly that one.
0.7.0
31 Oct 2026
latestNo release note was published with this version.
0.6.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Memory can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.