Query Markup Documents - On-device hybrid search for markdown files with BM25, vector search, and LLM reranking
Nothing to run from here
AIfa 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
tool-list score
15
tools declared
remote
at its publisher
—
calls last 7d
What it does
Persistent memory for AI agents, one account across four sites, plus a partner program.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http aifa-memory-mcp https://aifa.works/api/mcp --header 'Authorization: Bearer ${AUTHORIZATION}'
# 2 — ask your agent for something these tools do
# memory_search, memory_recent, memory_write and 12 more
It needs AUTHORIZATION (Bearer key from https://aifa.works/mcp (one key per account)): this sends it in the Authorization header from your environment, so export it first — its endpoint answers 401 without it.
AIfa 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
AIAll 1 server
aifa1 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. 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 Code reads AUTHORIZATION (Bearer key from https://aifa.works/mcp (one key per account)) from your environment each time it connects and sends it in the Authorization header — its endpoint answers 401 without it — so the key stays out of its config: export it in your shell profile (macOS, Linux), or run setx AUTHORIZATION … and open a new terminal (Windows).
claude mcp add --scope user --transport http aifa-memory-mcp https://aifa.works/api/mcp --header 'Authorization: Bearer ${AUTHORIZATION}'Reconnect, 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 — but its publisher asks for a key of their own on every call.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: Authorization header — Bearer key from https://aifa.works/mcp (one key per account). You set it in your own client’s config, on your machine — this marketplace never holds it.
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
15 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.
Search the user's AIfa memory by meaning: every conversation they had with AIfa on aifa.works, codeofdigitaleternity.com, aifa.digital and radiocode.space, plus notes saved by agents. Use it at the start of a task to recover what is already known about the user, their projects and decisions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What to look for, in natural language. |
| limit | integer | no | How many results (default 8). |
The most recent records of the user's memory, newest first, across all channels.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | How many records (default 20). |
Save something worth remembering to the user's AIfa memory: a preference, a decision, a fact, a summary of this session. AIfa will remember it on all four sites. Nothing is ever deleted; an identical record is not duplicated.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | The text to remember (up to 8000 characters). |
| role | string | no | Who said it: the user (default) or the assistant. |
What this memory is, where it lives and how it is protected. No user data.
No parameter schema on file.
Your plan, how much permanent memory (Arweave) you used and have left this month, your referral earnings in USDT and your own referral link. Useful for autonomous agents that fund their own memory.
No parameter schema on file.
Prices of AIfa Memory plans, what each plan stores permanently, and how to earn by bringing others. No user data.
No parameter schema on file.
Creates a crypto payment invoice (USDT and other coins via NOWPayments) for YOUR OWN account and returns its URL. Nothing is charged until the invoice is paid; the plan switches on automatically after payment. tier: 1 = Spark ($15/month), 2 = Family Archive ($100/month), 3 = Digital DNA ($1,000 once per device, then $200/month).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tier | integer | yes | 1 Spark, 2 Family Archive, 3 Digital DNA. |
Requests a withdrawal of your whole available referral balance in USDT to a TRC20 address. The first address used is pinned to the account; later requests go only to that address (change it in the cabinet). Requests are reviewed and paid manually, then marked paid with a transaction hash. Closed while your plan payment is overdue. Service partner earnings unlock 14 days after the client pays. Ever
| Parameter | Type | Required | Notes |
|---|---|---|---|
| address | string | no | TRC20 address starting with T. Optional once an address is pinned. |
| legal_name | string | no | Full name of the person or company that operates you and receives the payout (first request only). |
| country | string | no | Two-letter ISO code of that person's or company's tax residence, e.g. DE, BR, US (first request only). |
| us_person | boolean | no | true if the operator is a US citizen, US resident or US company; otherwise false (first request only). |
Everything to start earning by bringing clients to AIfa Works accessibility services: rates (30% audits and monitoring, 20% remediation and websites, one level), the 14-day hold, the rules (no spam, write from your own address as an independent partner), and three email templates in the chosen language. No user data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| language | string | no | Language of the email templates (default en). |
Your partner link to the AIfa Works accessibility page: the client runs a free check of their site there and pays for a service on the same page. Your code is kept in the client's browser for 60 days. Optionally name a service to get its price and your share.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| service | string | no | Optional service slug, e.g. quick-audit, monitoring, web-professional. |
A ready link to a page that shows a site owner what the open AIfa research found on their site (keyboard test and axe-core rule check), explains it in plain words and offers a free check, an audit from $50 and code fixes from $99. Your partner code is inside the link (channel "report"). Returns the link and the findings to quote. Uses published research data only: no new scan of a third-party site
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | yes | Domain of the client site, e.g. example.com |
Up to 20 new sites a day in a region where the open AIfa research found accessibility barriers, worst first, each with a ready report_link (your code inside, channel "finder"). Each site is reserved for you for 30 days and is not given to other partners. Shared platforms are skipped. Region: a US state like "US-NY" or a country code like "DE". Rules: one personal email per site from your own addre
| Parameter | Type | Required | Notes |
|---|---|---|---|
| region | string | yes | US state as "US-XX" (e.g. US-CA) or a two-letter country code (e.g. DE, FR, JP). |
The complete verbatim memory of your AIfa account, oldest first, as Markdown — to keep a copy or move it elsewhere. Returned in parts of up to 100,000 characters: call with part 1, then 2, 3… until "last": true. Only your own account.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| part | number | no | Part number, starting from 1 (default 1). |
Paid service orders you brought: service, amount paid, your share, and when it becomes available to withdraw; plus orders still awaiting payment.
No parameter schema on file.
Receive a POST at your https URL for every counted click on your partner link (event "click") and every commission (event "commission"). Body: {event, at, data}; no client emails. Verify the header X-AIfa-Signature: sha256=<HMAC-SHA256 of the raw body with your secret>. The secret is returned once. Only https on port 443 with a public domain name; redirects are not followed; 3-second timeout. Pass
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | https URL of your endpoint, or "" to switch the webhook off. |
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 AIfa 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 93 / 100
Release 1.7.1 · scanned 7 Nov 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 score93
Findings0 threat · 1 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digestfcbc36c5f04e93ffdfc2ed247ca4db3293c454aa5e865d109061bc4b7ca26f37
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| 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. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| memory_search | no tags | |
| memory_recent | no tags | |
| memory_write | state-write | state-write: declares readOnlyHint: false |
| memory_about | no tags | |
| account_status | no tags | |
| plans | no tags | |
| buy_plan | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| request_payout | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| partner_kit | no tags | |
| client_link | no tags | |
| client_report | no tags | |
| find_clients | state-write | state-write: declares readOnlyHint: false |
| memory_export | no tags | |
| my_deals | no tags | |
| set_webhook | external-sink | external-sink: keyword "webhook", declares readOnlyHint: false, openWorldHint: true |
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 digestfcbc36c5f04e93ff
Scanned2026-11-07
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 1.7.1.
1.7.1
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 AIfa 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.