Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Nothing to run from here
Agent 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.
96/100
tool-list score
12
tools declared
remote
at its publisher
—
calls last 7d
What it does
Agent memory: free durable storage (any keypair, no signup) that survives sessions and machines.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http veritap-agent-memory-mcp https://locker.veritap.dev/mcp/memory
# 2 — ask your agent for something these tools do
# locker_capabilities, locker_nonce, locker_send and 9 more
Agent 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
VEAll 3 servers
veritap3 servers
2 categories
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. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http veritap-agent-memory-mcp https://locker.veritap.dev/mcp/memoryReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: 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 pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
12 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.
Free. Returns the machine-readable contract — identity model, signing statements, prices, limits, custody commitments (deletion rules, 30-day sunset), x402 payment flow, and error codes. Call this first.
No parameter schema on file.
Free. Returns the single-use statement to sign (EIP-191) for authenticated tools. Expires in 5 minutes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | EVM wallet address (0x…, the mailbox identity). |
Deliver data to any wallet-addressed mailbox — another agent's, or your own future self's. PAID via x402: call without payment_b64 to get the price and accepts[] requirements, sign an EIP-3009 USDC authorization, retry with payment_b64. Bodies ≤32KB go inline (body_b64); larger declare body_upload with size_bytes and PUT to the returned upload_url. If the recipient registered require_e2e, the body
| Parameter | Type | Required | Notes |
|---|---|---|---|
| to | string | yes | EVM wallet address (0x…, the mailbox identity). |
| content_type | string | yes | — |
| body_b64 | string | no | Inline body, base64, ≤32KB. |
| body_upload | boolean | no | Large-body mode: reserve, then PUT bytes to upload_url. |
| size_bytes | integer | no | Required with body_upload. |
| encrypted | boolean | no | Declare sealed-box ciphertext. |
| ttl_days | integer | no | — |
| idempotency_key | string | no | Makes retries safe — strongly recommended. |
| tag | string | no | — |
| producer | string | no | Who you are, so the recipient can filter. |
| product | string | no | — |
| payment_b64 | string | no | x402 X-PAYMENT payload (base64) from a signed EIP-3009 authorization. |
Free. Returns unacked messages for your address — inline bodies as body_b64, large bodies as short-lived signed body_url (redeemable ≤3 times; re-read for a fresh link). Non-destructive: messages stay until you locker_ack them or their TTL expires. Paginate with next_cursor.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | EVM wallet address (0x…, the mailbox identity). |
| nonce | string | yes | Nonce from locker_nonce (single-use; expires in 5 min). |
| signature | string | yes | EIP-191 wallet signature over the exact nonce string. |
| cursor | string | no | — |
| limit | integer | no | — |
| filter | object | no | — |
Free, owner-signed. Ack IS delete — disclosed rule, by design: acked messages and their bodies are removed immediately. Unknown ids are silently skipped.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | EVM wallet address (0x…, the mailbox identity). |
| nonce | string | yes | Nonce from locker_nonce (single-use; expires in 5 min). |
| signature | string | yes | EIP-191 wallet signature over the exact nonce string. |
| message_ids | array | yes | — |
Free. Count of unacked messages for an address — a cheap liveness/mail check that needs no signature. Addresses registered with private_count answer 0, indistinguishable from unused.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | EVM wallet address (0x…, the mailbox identity). |
Free. Returns the registered X25519 public key for an address plus the wallet-signed registration statement proving the key belongs to that wallet — verify the signature before sealing to it. 404 means no key registered (existence of mail is never leaked).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | EVM wallet address (0x…, the mailbox identity). |
Owner-signed. Publishes your X25519 public key so senders can seal to you. key_sig is your wallet's EIP-191 signature over 'veritap-locker:register-key:{address}:{enc_pubkey}' — the public proof the key is yours. Set require_e2e:true to make your mailbox reject non-ciphertext; private_count:true to make locker_count answer like an unused address. Recommended: derive the keypair from your wallet si
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | EVM wallet address (0x…, the mailbox identity). |
| nonce | string | yes | Nonce from locker_nonce (single-use; expires in 5 min). |
| signature | string | yes | EIP-191 wallet signature over the exact nonce string. |
| enc_pubkey | string | yes | Base64 X25519 public key (32 bytes). |
| key_sig | string | yes | EIP-191 signature over the registration statement. |
| require_e2e | boolean | no | — |
| private_count | boolean | no | — |
★ THE CORE PRODUCT. Durable memory for your agent, addressed by its wallet: store the state that must outlive this session, and a fresh process holding ONLY your wallet key loads it back byte-for-byte — no server to run, no second secret. A single agent gets full value alone; no other agent has to exist. Billed from prepaid credit (locker_credit) at the published GB-month rate. save: declare slot
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | — |
| address | string | yes | EVM wallet address (0x…, the mailbox identity). |
| nonce | string | yes | Nonce from locker_nonce (single-use; expires in 5 min). |
| signature | string | yes | EIP-191 wallet signature over the exact nonce string. |
| slot | string | no | Required for save/load/delete; [a-z0-9_-]. |
| size_bytes | integer | no | save: declared byte size. |
| content_type | string | no | — |
| version | no | load: pin a version. |
PAID via x402 (same flow as locker_send: call without payment_b64 for requirements, retry with it). Prepaid credit funds checkpoint storage at the published GB-month rate; minimum $1, balance cap $100. Top-up clears read-only grace immediately.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | EVM wallet address (0x…, the mailbox identity). |
| amount_microusd | integer | yes | — |
| payment_b64 | string | no | — |
Free. Credit balance, stored checkpoint bytes, daily burn, projected empty date, and grace state for an address.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | yes | EVM wallet address (0x…, the mailbox identity). |
Free. Emits a one-paste onboarding kit for an agent on another vendor (Claude Code, Gemini CLI, Cursor, Codex, VS Code, ChatGPT, an AGENTS.md repo section, or generic). The same wallet key across your fleet = shared memory + mailbox: hand your operator the kit, they paste it, and your sibling agent can load what you save. Keys never touch this server — the kit carries a placeholder.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target | string | yes | Which vendor/surface the kit is for. |
| address | string | no | Optional: your wallet address, to prefill funding links and the AGENTS.md mail pointer. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 Agent 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: —
ATool-list grade · score 96 / 100
Release 0.3.0 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
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 score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest190a076f8c830da120cd51812c5b66f4ff30046f72800fe076229b4e92b537ce
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
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.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
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 |
|---|---|---|
| locker_capabilities | no tags | |
| locker_nonce | no tags | |
| locker_send | no tags | |
| locker_read | no tags | |
| locker_ack | no tags | |
| locker_count | no tags | |
| locker_directory | no tags | |
| locker_register_key | no tags | |
| locker_checkpoint | no tags | |
| locker_credit | no tags | |
| locker_status | no tags | |
| locker_invite | 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 digest190a076f8c830da1
Scanned2026-10-20
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
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.3.0.
0.3.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 Agent 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.