AIfa Memory is listed as active in the registry but did not answer our last check. It exposes 15 tools. Last commit 6 Nov 2026.
Persistent memory for AI agents, one account across four sites, plus a partner program.
Uptime history
42 hours of history · worst hour 0%
42 hours agonow
0.0%
Uptime 24h
0 of 91 checks
15
Tools
read from the server
107 ms
Response time
average over 24h
0
Stars
last commit 6 Nov 2026
AIfa Memory does not always answer
Over the last week it answered 30.3% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.
run in your terminal
claude mcp add aifa-memory --transport http https://aifa.works/api/mcpSettings → Connectors → Add custom connector, then paste this address
https://aifa.works/api/mcp~/.codex/config.toml
[mcp_servers.aifa-memory]
url = "https://aifa.works/api/mcp".cursor/mcp.json
{
"mcpServers": {
"aifa-memory": {
"url": "https://aifa.works/api/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"aifa-memory": {
"type": "http",
"url": "https://aifa.works/api/mcp"
}
}
}Available tools 15
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
memory
memory_about
What this memory is, where it lives and how it is protected. No user data.
memory_export
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.
memory_recent
The most recent records of the user's memory, newest first, across all channels.
memory_search
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.
memory_write
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.
client
client_link
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.
client_report
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 is made.
account
account_status
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.
buy
buy_plan
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).
clients
find_clients
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 address, at most one follow-up, no bulk mailing.
deals
my_deals
Paid service orders you brought: service, amount paid, your share, and when it becomes available to withdraw; plus orders still awaiting payment.
partner
partner_kit
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.
plans
plans
Prices of AIfa Memory plans, what each plan stores permanently, and how to earn by bringing others. No user data.
request
request_payout
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. Every address is checked against the US Treasury (OFAC) sanctions list. First request: also pass the one-time tax self-certification of the person or company that operates you (legal_name, country, us_person).
webhook
set_webhook
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 an empty url to switch off.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://aifa.works/api/mcp | streamable-http | answering | 107 ms | 15 min ago |
Alternatives to AIfa Memory
same job, measured the same wayBrain Memory
by brainmemory
Persistent memory for AI agents: one brain shared across Claude, Cursor, Codex and more.
Memoir
by bighippoman
Structured session journals for AI agents. Persistent memory across sessions.
Mifactory Agent Memory
by mifactory-bot
Persistent memory for AI agents across Claude, ChatGPT and any MCP client.
Goldhold
by jerrysrodz
Persistent memory for AI agents. Search, store, and recall across sessions.
Engram
by getengram
Persistent, verbatim, searchable memory for AI assistants — one memory across every MCP client.
Agentram MCP
by seanmarkwei
Model Context Protocol server for AgentRAM. Persistent memory for AI agents.
Nucleus
by eidetic-works
Persistent memory for AI agents — shared .brain across Claude Code, Cursor & Codex
MCP Memory
by infoinlet-marketplace
Persistent searchable memory for AI agents — save/get/search across sessions, tags.
AIfa Memory — questions
Answers built from our own checks of this server.
What can AIfa Memory do?
It exposes 15 tools, read directly from the server on our last check. Among them: account_status, buy_plan, client_link, client_report, find_clients, memory_about and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is AIfa Memory mostly used for?
Its tools cluster around memory and client. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is AIfa Memory working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 107 ms. The bar chart above shows every period we have measured.
The registry lists AIfa Memory as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect AIfa Memory?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does AIfa Memory need an API key?
No. AIfa Memory completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.
Is AIfa Memory open source?
The code is open source: it is published under the MIT licence and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at aifa.works, which runs on its operator's own terms.