Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Nothing to run from here
Memex 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
9
downloads a day
local
runs on your machine
86
downloads in 30d
What it does
Tiered memory MCP server for Claude and AI agents — FTS5 search, dedup, export/import, auto-snapshot
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user memex-mcp '--' npx -y memex-mcp-server
# 2 — ask your agent for something these tools do
# memory_append, memory_search, memory_read and 84 more
Memex costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
AMAll 1 server
amduwcwt1 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 Memex 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. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user memex-mcp '--' npx -y memex-mcp-serverReconnect, 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 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
87 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.
Add a new memory. L1=short-term events (auto-expires 72h), L2=session summaries (90d), L3=permanent knowledge. Deduplicates identical content.
No parameter schema on file.
Full-text search across all memories. Returns ranked results with highlighted snippets. Supports prefix matching with trailing *. Special characters are safely handled.
No parameter schema on file.
Read a specific memory by ID.
No parameter schema on file.
List memories with optional filters. Returns paginated results.
No parameter schema on file.
Update an existing memory
No parameter schema on file.
Delete a memory by ID.
No parameter schema on file.
Get overview statistics: count per tier, per project, database size.
No parameter schema on file.
Batch delete memories by filter. Requires at least one condition. Use to clean up polluted or outdated data.
No parameter schema on file.
Export memories as JSON for backup. Optionally filter by tier, project, or tags.
No parameter schema on file.
Progressive disclosure search: queries L3 first (permanent knowledge), expands to L2 (session summaries) if needed, then L1 (recent events). Stops as soon as enough results are found. Use this instead of memory_search when you want context-aware recall that respects memory importance.
No parameter schema on file.
Import memories from a JSON export. Skips duplicates by content hash.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
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 Memex 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 2.7.0 · scanned 14 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
Findings10 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digest09ea86980893d5d025ae976b1d0502088db2a274dc7f78607e0f0e2e61d014ae
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 (87 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>".
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/analysis-tools.js:71) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/analysis-tools.js:87) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "full-only") holds (dist/tools/analysis-tools.js:98) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "full-only") holds (dist/tools/analysis-tools.js:187) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/analysis-tools.js:204) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/analysis-tools.js:226) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/analysis-tools.js:250) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/analysis-tools.js:283) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/analysis-tools.js:297) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterNamedTool(profile, "core", "memory_handoff") holds (dist/tools/analysis-tools.js:323) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/canonicalization-tools.js:14) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/canonicalization-tools.js:28) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/canonicalization-tools.js:43) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/canonicalization-tools.js:57) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/canonicalization-tools.js:70) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/canonicalization-tools.js:86) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/canonicalization-tools.js:100) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/canonicalization-tools.js:120) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "full-only") holds (dist/tools/canvas-tools.js:9) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "full-only") holds (dist/tools/canvas-tools.js:27) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "full-only") holds (dist/tools/canvas-tools.js:51) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "full-only") holds (dist/tools/canvas-tools.js:65) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "core") || shouldRegisterTool(profile, "admin") holds (dist/tools/capability-tools.js:5) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/capability-tools.js:28) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/capability-tools.js:63) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/evidence-tools.js:5) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/evidence-tools.js:25) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/evidence-tools.js:41) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/evidence-tools.js:55) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/evidence-tools.js:70) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/evidence-tools.js:79) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/evidence-tools.js:93) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/evidence-tools.js:105) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/evidence-tools.js:134) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/evidence-tools.js:148) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/memory-record-tools.js:6) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/memory-record-tools.js:48) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/memory-record-tools.js:91) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/memory-record-tools.js:106) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/memory-record-tools.js:147) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/memory-record-tools.js:185) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/memory-record-tools.js:201) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/memory-record-tools.js:210) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/memory-record-tools.js:235) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "full-only") holds (dist/tools/memory-record-tools.js:254) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/memory-record-tools.js:278) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/pattern-tools.js:6) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/pattern-tools.js:47) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/pattern-tools.js:85) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/pattern-tools.js:100) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/pattern-tools.js:141) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/pattern-tools.js:168) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/pattern-tools.js:193) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/refine-tools.js:8) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/refine-tools.js:24) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/refine-tools.js:40) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/refine-tools.js:54) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/refine-tools.js:69) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/team-tools.js:59) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/team-tools.js:131) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/team-tools.js:160) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/team-tools.js:217) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/team-tools.js:278) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/team-tools.js:339) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/team-tools.js:362) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:5) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:16) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:31) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:45) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:60) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:75) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:87) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:102) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:121) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:133) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:147) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:159) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:174) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:191) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:210) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:222) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:237) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "full-only") holds (dist/tools/workflow-tools.js:141) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "full-only") holds (dist/tools/workflow-tools.js:208) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterNamedTool(profile, "core", "memory_capture") holds (dist/tools/workflow-tools.js:281) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterNamedTool(profile, "core", "memory_session_close") holds (dist/tools/workflow-tools.js:355) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 87 recovered tools are registered only when shouldRegisterTool(profile, "full-only") holds (dist/tools/workflow-tools.js:420) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
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.
No tool is registered unconditionally · (1) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/analysis-tools.js:71) · (2) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/analysis-tools.js:87) · (3) 1 only when shouldRegisterTool(profile, "full-only") holds (dist/tools/analysis-tools.js:98) · (4) 1 only when shouldRegisterTool(profile, "full-only") holds (dist/tools/analysis-tools.js:187) · (5) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/analysis-tools.js:204) · (6) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/analysis-tools.js:226) · (7) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/analysis-tools.js:250) · (8) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/analysis-tools.js:283) · (9) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/analysis-tools.js:297) · (10) 1 only when shouldRegisterNamedTool(profile, "core", "memory_handoff") holds (dist/tools/analysis-tools.js:323) · (11) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/canonicalization-tools.js:14) · (12) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/canonicalization-tools.js:28) · (13) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/canonicalization-tools.js:43) · (14) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/canonicalization-tools.js:57) · (15) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/canonicalization-tools.js:70) · (16) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/canonicalization-tools.js:86) · (17) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/canonicalization-tools.js:100) · (18) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/canonicalization-tools.js:120) · (19) 1 only when shouldRegisterTool(profile, "full-only") holds (dist/tools/canvas-tools.js:9) · (20) 1 only when shouldRegisterTool(profile, "full-only") holds (dist/tools/canvas-tools.js:27) · (21) 1 only when shouldRegisterTool(profile, "full-only") holds (dist/tools/canvas-tools.js:51) · (22) 1 only when shouldRegisterTool(profile, "full-only") holds (dist/tools/canvas-tools.js:65) · (23) 1 only when shouldRegisterTool(profile, "core") || shouldRegisterTool(profile, "admin") holds (dist/tools/capability-tools.js:5) · (24) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/capability-tools.js:28) · (25) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/capability-tools.js:63) · (26) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/evidence-tools.js:5) · (27) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/evidence-tools.js:25) · (28) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/evidence-tools.js:41) · (29) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/evidence-tools.js:55) · (30) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/evidence-tools.js:70) · (31) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/evidence-tools.js:79) · (32) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/evidence-tools.js:93) · (33) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/evidence-tools.js:105) · (34) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/evidence-tools.js:134) · (35) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/evidence-tools.js:148) · (36) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/memory-record-tools.js:6) · (37) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/memory-record-tools.js:48) · (38) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/memory-record-tools.js:91) · (39) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/memory-record-tools.js:106) · (40) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/memory-record-tools.js:147) · (41) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/memory-record-tools.js:185) · (42) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/memory-record-tools.js:201) · (43) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/memory-record-tools.js:210) · (44) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/memory-record-tools.js:235) · (45) 1 only when shouldRegisterTool(profile, "full-only") holds (dist/tools/memory-record-tools.js:254) · (46) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/memory-record-tools.js:278) · (47) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/pattern-tools.js:6) · (48) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/pattern-tools.js:47) · (49) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/pattern-tools.js:85) · (50) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/pattern-tools.js:100) · (51) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/pattern-tools.js:141) · (52) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/pattern-tools.js:168) · (53) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/pattern-tools.js:193) · (54) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/refine-tools.js:8) · (55) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/refine-tools.js:24) · (56) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/refine-tools.js:40) · (57) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/refine-tools.js:54) · (58) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/refine-tools.js:69) · (59) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/team-tools.js:59) · (60) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/team-tools.js:131) · (61) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/team-tools.js:160) · (62) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/team-tools.js:217) · (63) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/team-tools.js:278) · (64) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/team-tools.js:339) · (65) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/team-tools.js:362) · (66) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:5) · (67) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:16) · (68) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:31) · (69) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:45) · (70) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:60) · (71) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:75) · (72) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:87) · (73) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:102) · (74) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:121) · (75) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:133) · (76) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:147) · (77) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:159) · (78) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:174) · (79) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:191) · (80) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:210) · (81) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:222) · (82) 1 only when shouldRegisterTool(profile, "admin") holds (dist/tools/wiki-tools.js:237) · (83) 1 only when shouldRegisterTool(profile, "full-only") holds (dist/tools/workflow-tools.js:141) · (84) 1 only when shouldRegisterTool(profile, "full-only") holds (dist/tools/workflow-tools.js:208) · (85) 1 only when shouldRegisterNamedTool(profile, "core", "memory_capture") holds (dist/tools/workflow-tools.js:281) · (86) 1 only when shouldRegisterNamedTool(profile, "core", "memory_session_close") holds (dist/tools/workflow-tools.js:355) · (87) 1 only when shouldRegisterTool(profile, "full-only") holds (dist/tools/workflow-tools.js:420) — typically when a key or option is configured. All 87 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| memory_governance_review conditional (1) | no tags | |
| memory_trace conditional (2) | no tags | |
| memory_brief_with_evidence conditional (3) | no tags | |
| memory_entity_map conditional (4) | no tags | |
| memory_patterns conditional (5) | no tags | |
| memory_guardrails conditional (6) | no tags | |
| memory_repair_plan conditional (7) | no tags | |
| memory_repair_execute conditional (8) | no tags | |
| memory_repair_route conditional (9) | no tags | |
| memory_handoff conditional (10) | no tags | |
| project_alias_upsert conditional (11) | no tags | |
| project_alias_list conditional (12) | no tags | |
| project_alias_read conditional (13) | no tags | |
| tag_vocabulary_upsert conditional (14) | no tags | |
| tag_vocabulary_list conditional (15) | no tags | |
| tag_vocabulary_read conditional (16) | no tags | |
| memory_write_audit_list conditional (17) | no tags | |
| memory_write_audit_read conditional (18) | no tags | |
| session_canvas_open conditional (19) | no tags | |
| session_canvas_node_add conditional (20) | no tags | |
| session_canvas_get conditional (21) | no tags | |
| session_canvas_record_use conditional (22) | no tags | |
| capability_search conditional (23) | no tags | |
| capability_draft_card conditional (24) | no tags | |
| capability_capture_card conditional (25) | no tags | |
| evidence_ingest conditional (26) | no tags | |
| evidence_query conditional (27) | no tags | |
| evidence_get conditional (28) | untrusted-input | untrusted-input: keyword "fetch" |
| evidence_multi_get conditional (29) | untrusted-input | untrusted-input: keyword "fetch" |
| evidence_status conditional (30) | no tags | |
| evidence_embedding_backfill conditional (31) | no tags | |
| evidence_embedding_status conditional (32) | no tags | |
| evidence_promote conditional (33) | no tags | |
| memory_embedding_backfill conditional (34) | no tags | |
| memory_embedding_status conditional (35) | no tags | |
| memory_append conditional (36) | no tags | |
| memory_search conditional (37) | no tags | |
| memory_read conditional (38) | no tags | |
| memory_list conditional (39) | no tags | |
| memory_update conditional (40) | no tags | |
| memory_delete conditional (41) | no tags | |
| memory_stats conditional (42) | no tags | |
| memory_purge conditional (43) | no tags | |
| memory_export conditional (44) | no tags | |
| memory_recall conditional (45) | no tags | |
| memory_import conditional (46) | no tags | |
| pattern_candidate_upsert conditional (47) | no tags | |
| pattern_candidate_list conditional (48) | no tags | |
| pattern_candidate_read conditional (49) | no tags | |
| pattern_candidate_promote conditional (50) | no tags | |
| pattern_candidate_import_strategic_compact conditional (51) | no tags | |
| pattern_candidate_validate_profile_summary conditional (52) | no tags | |
| pattern_candidate_import_profile_summary conditional (53) | no tags | |
| memory_refine_history conditional (54) | no tags | |
| memory_refine_import conditional (55) | no tags | |
| memory_refine_batch_list conditional (56) | no tags | |
| memory_refine_batch_read conditional (57) | no tags | |
| memory_refine_canonicalize_projects conditional (58) | no tags | |
| team_memory_search conditional (59) | no tags | |
| team_memory_read conditional (60) | no tags | |
| team_memory_context conditional (61) | no tags | |
| team_memory_brief conditional (62) | no tags | |
| team_memory_handoff conditional (63) | no tags | |
| team_memory_promote conditional (64) | no tags | |
| team_memory_promote_ready conditional (65) | no tags | |
| wiki_workspace_init conditional (66) | no tags | |
| wiki_ingest_source conditional (67) | no tags | |
| wiki_batch_list conditional (68) | no tags | |
| wiki_batch_read conditional (69) | no tags | |
| wiki_review_list conditional (70) | no tags | |
| wiki_review_summary conditional (71) | no tags | |
| wiki_review_read conditional (72) | no tags | |
| wiki_review_update conditional (73) | no tags | |
| wiki_index conditional (74) | no tags | |
| wiki_page_list conditional (75) | no tags | |
| wiki_page_read conditional (76) | no tags | |
| wiki_search conditional (77) | no tags | |
| wiki_query conditional (78) | no tags | |
| wiki_analysis_write conditional (79) | no tags | |
| wiki_export_manifest conditional (80) | no tags | |
| wiki_publish_bundle conditional (81) | no tags | |
| wiki_lint conditional (82) | no tags | |
| memory_context conditional (83) | no tags | |
| memory_session_open conditional (84) | no tags | |
| memory_capture conditional (85) | no tags | |
| memory_session_close conditional (86) | no tags | |
| memory_brief conditional (87) | 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 digest09ea86980893d5d0
Scanned2026-10-14
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 2.7.0. Pin a release below and the command asks for exactly that one.
2.7.0
10 Sep 2026
latestNo release note was published with this version.
1.1.2
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 Memex 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.