Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Nothing to run from here
Vayl 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.
100/100
trust score
32
tools declared
local
runs on your machine
—
downloads a day
What it does
Reconciling memory for AI agents: a changed fact retires the old value, with history and approval.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user vayl-mcp '--' uvx vayl-mcp
# 2 — ask your agent for something these tools do
# remember, recall, recall_related and 29 more
Vayl costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ACAll 1 server
ac126441 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 Vayl 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 uv (docs.astral.sh/uv): uvx 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 vayl-mcp '--' uvx vayl-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
Nothing is required, but it can take OPENAI_API_KEY (OpenAI key for extraction and embeddings. Leave unset to use a local Ollama model.), VAYL_DB (Absolute path of the SQLite memory database.) if you want to set them.
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
32 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.
Store fact(s) from a statement. Reconciles automatically: a new value SUPERSEDES the old one (not appended), removals are RETRACTED, and multiple facts in one message are all captured.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
| user_id | string | no | — |
| agent_id | string | no | — |
| run_id | string | no | — |
| metadata | object | no | — |
| source | string | no | — |
Answer a question from CURRENT memory — the active value ('what state library do we use?') or a multi-hop question over current facts. Returns 'I don't know' rather than guessing, and NEVER answers from a retired/retracted fact. For the timeline of a subject, use history.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | — |
| user_id | string | no | — |
| agent_id | string | no | — |
| run_id | string | no | — |
| explain | boolean | no | — |
| include_history | boolean | no | — |
| critical_categories | string | no | — |
Answer a DEEP / RELATIONAL / multi-hop question using the entity graph ('who owns the company Bob works for?', 'which services depend on the auth module?').
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | — |
| user_id | string | no | — |
| agent_id | string | no | — |
| run_id | string | no | — |
Retract a fact — a removal with no replacement. Unlike additive stores, this actually retires it so it stops being returned as current (kept in history for audit). Examples:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | — |
| user_id | string | no | — |
| agent_id | string | no | — |
| run_id | string | no | — |
Fetch one memory by its id (the #id shown by list_memories) — its value, status, scope, confidence, what it supersedes, and any metadata.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| memory_id | integer | yes | — |
| user_id | string | no | — |
| agent_id | string | no | — |
| run_id | string | no | — |
Correct a memory by id (the #id from list_memories). Audit-preserving: the old value is retired to history and the new value becomes active — so the change still shows up in history.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| memory_id | integer | yes | — |
| new_value | string | yes | — |
| user_id | string | no | — |
| agent_id | string | no | — |
| run_id | string | no | — |
The change-log for a subject — every value it has held, oldest → newest, with status.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subject | string | yes | — |
| user_id | string | no | — |
| agent_id | string | no | — |
| run_id | string | no | — |
Log a decision an agent is about to take, bound to the EXACT facts it consulted. Atomically recalls question with provenance and snapshots those beliefs (value, source, confidence, what they superseded) alongside action_summary. The snapshot is immutable and signed, so 'why did the agent do…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action_summary | string | yes | — |
| question | string | yes | — |
| user_id | string | no | — |
| agent_id | string | no | — |
| run_id | string | no | — |
Reconstruct why an agent acted: the recorded action and the exact beliefs it held at that moment — even if those facts have since been superseded, retracted, or erased. Also verifies the decision's signed receipt so you know the record itself wasn't altered.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| decision_id | integer | yes | — |
| user_id | string | no | — |
Ask whether it's SAFE to take an autonomous action based on what memory knows about subject.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subject | string | yes | — |
| user_id | string | no | — |
| agent_id | string | no | — |
| run_id | string | no | — |
| min_confidence | number | no | — |
| require_active | boolean | no | — |
| block_on_flagged | boolean | no | — |
| max_staleness_days | number | no | — |
| block_on_recent_change_days | number | no | — |
Like recall, but for when the agent will ACT on the answer. It answers only if every current fact behind the answer passes the safety policy; otherwise it withholds the answer and returns the reasons (disputed value, low confidence, stale, or nothing current). Use this instead of recall on the…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | — |
| user_id | string | no | — |
| agent_id | string | no | — |
| run_id | string | no | — |
| min_confidence | number | no | — |
| require_active | boolean | no | — |
| block_on_flagged | boolean | no | — |
| max_staleness_days | number | no | — |
| block_on_recent_change_days | number | no | — |
| critical_categories | string | no | — |
PERMANENTLY erase every record of a subject — including history and tombstones — for a user.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subject | string | yes | — |
| user_id | string | no | — |
| agent_id | string | no | — |
| run_id | string | no | — |
PERMANENTLY erase memory (history included). With no agent_id/run_id, erases ALL of the user's memory across every space (account deletion / GDPR); pass them to erase just one space.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| user_id | string | no | — |
| agent_id | string | no | — |
| run_id | string | no | — |
Issue a signed, third-party-verifiable attestation of what memory currently holds for subject — 'as of now, the active value is X', anchored to the tamper-evident audit-log head.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| subject | string | yes | — |
| user_id | string | no | — |
| agent_id | string | no | — |
| run_id | string | no | — |
Verify a persisted erasure receipt or knowledge attestation: recompute its canonical body and check the Ed25519 signature. Confirms the artifact is authentic and unaltered — the same check a third party can run with only the public key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| receipt_id | integer | yes | — |
Verify the tamper-evident audit chain end-to-end. Recomputes every row's hash and (if signed) signature; reports INTACT, or the exact row where the chain breaks — so you can prove the accountability log wasn't edited, reordered, or truncated.
Takes no parameters.
Return Vayl's Ed25519 public key (hex). Anyone can use it to verify erasure receipts, attestations, and the signed audit chain WITHOUT the secret key or access to the database.
Takes no parameters.
Configure how a SHARED space resolves conflicts between DIFFERENT contributors (sources).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mode | string | no | — |
| authority | object | no | — |
| user_id | string | no | — |
| agent_id | string | no | — |
| run_id | string | no | — |
Show the source-aware reconciliation policy configured for a space (default RECENCY if unset).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| user_id | string | no | — |
| agent_id | string | no | — |
| run_id | string | no | — |
List proposed changes to confirm-required slots that have NOT been applied.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| user_id | string | no | — |
| agent_id | string | no | — |
| run_id | string | no | — |
Approve a proposed change to a confirm-required slot, applying it. Needs the approve capability (admin and member roles; agents lack it, so an agent can't approve its own proposal).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| memory_id | integer | yes | — |
| user_id | string | no | — |
| agent_id | string | no | — |
| run_id | string | no | — |
| decided_by | string | no | — |
Discard a proposed change. The current value stands. The proposal is kept as history — that someone proposed it is itself worth being able to audit. Needs approve, like
| Parameter | Type | Required | Notes |
|---|---|---|---|
| memory_id | integer | yes | — |
| user_id | string | no | — |
| agent_id | string | no | — |
| run_id | string | no | — |
| decided_by | string | no | — |
Admin only. Create a principal (a human user, agent, or service) and issue its API key. Roles:
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
| role | string | no | — |
| kind | string | no | — |
| scopes | string | no | — |
| tenant | string | no | — |
Admin only. List your tenant's principals — id, name, roles, and whether disabled (the deployment operator sees every tenant's). Never shows API keys (only their hashes are stored).
Takes no parameters.
Show the deployment's edition and entitlements — Community or a licensed edition, seats used vs allowed, expiry, and unlocked features. If a license was rejected (tampered/expired/wrong key), this says so and reports the Community fallback it's running under.
Takes no parameters.
Admin only. Disable a principal — its API key stops working immediately. Irreversible (create a new principal to restore access). With erase=True, the principal row is HARD-deleted (Art. 17 for team members) instead of retained as disabled. A tenant admin can only revoke its own tenant's…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| principal_id | string | yes | — |
| erase | boolean | no | — |
List the current active facts (the reconciled current beliefs) for a user, plus a history block of what was superseded / retracted / archived. Active rows show the #id for get/update.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| user_id | string | no | — |
| agent_id | string | no | — |
| run_id | string | no | — |
Export everything held about a user/space as machine-readable JSON — data-subject access & portability (GDPR Art. 15/20). A complete DSAR answer: statements (active + full history), PLUS what the append-only records hold about them — decision snapshots, audit entries, and receipts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| user_id | string | no | — |
| agent_id | string | no | — |
| run_id | string | no | — |
Retention / storage-limitation (GDPR Art. 5(1)(e)): permanently delete records written more than older_than_days ago. Statements are scoped to the user/space. The optional flags extend the same window to the append-only tables — NOTE these are not per-user: include_decisions and…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| older_than_days | integer | yes | — |
| user_id | string | no | — |
| agent_id | string | no | — |
| run_id | string | no | — |
| include_audit | boolean | no | — |
| include_decisions | boolean | no | — |
| include_receipts | boolean | no | — |
The accountability trail (GDPR Art. 5(2)) — recent data operations: who / what / when.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
| user_id | string | no | — |
Operational KPIs for this Vayl instance — on-device, nothing leaves the machine:
Takes no parameters.
Check that Vayl is configured and its dependencies are reachable — database, embedder, LLM, and graph (if enabled). Run this to diagnose setup before relying on memory; it makes one small LLM/embed call, so it costs a few tokens.
Takes no parameters.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- 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 Vayl 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 100 / 100
Release 0.10.0 · scanned 28 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 score100
Findings1 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digest09246dc997b585068731469c3443ac80cd22f75632e69bfbe876ad78840908b3
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| 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 (32 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. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| remember | no tags | |
| recall | no tags | |
| recall_related | no tags | |
| forget | no tags | |
| get_memory | untrusted-input | untrusted-input: keyword "fetch" |
| update_memory | no tags | |
| history | no tags | |
| record_decision | no tags | |
| explain_decision | no tags | |
| check_before_act | no tags | |
| safe_recall | no tags | |
| delete | no tags | |
| delete_all | no tags | |
| attest | no tags | |
| verify_receipt | no tags | |
| verify_audit | no tags | |
| export_public_key | no tags | |
| set_reconcile_policy | no tags | |
| get_reconcile_policy | no tags | |
| pending_changes | no tags | |
| confirm_change | no tags | |
| reject_change | no tags | |
| create_principal | no tags | |
| list_principals | no tags | |
| license_status | no tags | |
| revoke_principal | no tags | |
| list_memories | no tags | |
| export_memory | no tags | |
| purge_expired | no tags | |
| audit_log | no tags | |
| stats | no tags | |
| health | 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 digest09246dc997b58506
Scanned2026-10-28
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.10.0. Pin a release below and the command asks for exactly that one.
0.10.0
undated
latestNo release note was published with this version.
—
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 Vayl 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.