AIfa Memory

works.aifaPublished by aifa.worksOfficial publisherv1.7.1Updated Nov 7, 2026

Persistent memory for AI agents, one account across four sites, plus a partner program.

VerifiedStreamable HTTPWeb executableFinanceKnowledge & MemoryBusiness & Commerce

Overview

AI-generated overview

Hosted memory server that lets an assistant search, save and export the user's AIfa account memory, plus account, billing and partner tools.

What you can do
  • Search, list recent and save memory records, and export the whole memory as Markdown
  • Describe the memory service and show plan prices
  • Check plan, storage used, referral earnings and referral link
  • Create a crypto invoice for a plan and request a USDT payout of referral balance
  • Get partner kit, partner links, site reports and daily client leads, and track deals
  • Register a signed webhook for clicks and commissions
When to use it
Useful when you want an assistant to carry context across sessions and across the four AIfa sites, or when you already use an AIfa account and want agents to read and extend that memory. Also relevant if you promote AIfa Works accessibility services and want leads, reports and commission tracking inside the assistant.
Requirements
A remote streamable HTTP endpoint; no local package. An AIfa account and a bearer key created at aifa.works/mcp, sent in the Authorization header (one key per account). Claude Desktop needs mcp-remote via npx. Rate limits apply per key.
Before you install
The bearer key grants full access to the account's memory, so keep it out of shared configs and revoke it by signing out everywhere. Tools can spend money: buy_plan creates a crypto invoice for the account's own plan, and request_payout sends the whole referral balance to a pinned TRC20 address that cannot be changed through the tools. set_webhook returns a signing secret once. Memory is stored on Arweave on paid plans, and the server is a hosted third-party service.

Installation

In SourceWeft

  1. Open AIfa Memory in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/works.aifa%2Faifa-memory/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "aifa-memory": {
      "type": "http",
      "url": "https://aifa.works/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

AIfa Memory — MCP server

[mcptry]

One memory for you and your AI agents. AIfa Memory is a hosted Model Context Protocol server. It connects Claude, Cursor, VS Code or any other MCP client to the memory of your AIfa account — the same memory AIfa uses when you talk to her on aifa.works, codeofdigitaleternity.com, aifa.digital and radiocode.space.

Your agent can recall what you discussed with AIfa weeks ago, save new decisions, and hand everything back to you as one Markdown file whenever you want to leave.

Endpoint   https://aifa.works/api/mcpTransport  Streamable HTTP (JSON-RPC 2.0, stateless)Auth       Authorization: Bearer <your key>Version    1.7.0 · protocol 2025-06-18, 2025-03-26, 2024-11-05

This repository holds the public description of the server: connection examples, the full tool list and the registry manifest. The server itself runs on aifa.works; its code lives in the private site repository together with the database and payments. If you want a memory server you can read and run yourself, see padam-nocturne — our open-source, local-first MCP memory (one SQLite file, 8 tools).

Quick start

  1. Sign in at aifa.works/mcp and create your key. One key per account.
  2. Add the server to your client (examples below). Replace YOUR_AIFA_MCP_KEY with your key.
  3. Ask your agent: "Search my AIfa memory for what we decided about …"

Claude Code

bash
claude mcp add --transport http aifa-memory https://aifa.works/api/mcp --header "Authorization: Bearer YOUR_AIFA_MCP_KEY"

Cursor — ~/.cursor/mcp.json

json
{  "mcpServers": {    "aifa-memory": {      "url": "https://aifa.works/api/mcp",      "headers": { "Authorization": "Bearer YOUR_AIFA_MCP_KEY" }    }  }}

VS Code — .vscode/mcp.json

json
{  "servers": {    "aifa-memory": {      "type": "http",      "url": "https://aifa.works/api/mcp",      "headers": { "Authorization": "Bearer YOUR_AIFA_MCP_KEY" }    }  }}

Claude Desktop — claude_desktop_config.json

Claude Desktop connects to remote servers through mcp-remote. The header is passed without spaces inside args and the value goes into env — on Windows, spaces inside args break the header.

json
{  "mcpServers": {    "aifa-memory": {      "command": "npx",      "args": ["-y", "mcp-remote", "https://aifa.works/api/mcp", "--header", "Authorization:${AUTH_HEADER}"],      "env": { "AUTH_HEADER": "Bearer YOUR_AIFA_MCP_KEY" }    }  }}

The same files are in examples/.

Tools

Fifteen tools. Full parameters and hints: TOOLS.md.

Memory

ToolWhat it does
memory_searchSearch your memory by meaning — every conversation with AIfa on the four sites plus notes saved by agents.
memory_recentThe most recent records, newest first, across all channels.
memory_writeSave a preference, decision, fact or session summary. Nothing is deleted; an identical record is not duplicated.
memory_exportYour whole verbatim memory as Markdown, in parts of up to 100,000 characters.
memory_aboutWhat this memory is, where it lives and how it is protected. No user data.

Account

ToolWhat it does
account_statusYour plan, permanent memory used and left this month, referral earnings and your referral link.
plansPrices of the plans and what each one stores permanently. No user data.
buy_planCreates a crypto invoice (NOWPayments) for your own account and returns its URL. Nothing is charged until you pay.
request_payoutRequests a withdrawal of your referral balance in USDT (TRC20). Reviewed and paid manually; every address is screened against the OFAC sanctions list.

Partner program (bringing clients to AIfa Works accessibility services)

ToolWhat it does
partner_kitRates, the 14-day hold, the rules and three email templates (en, ru, es, zh).
client_linkYour partner link to the accessibility page, optionally with a service price and your share.
client_reportA ready report page for a site owner, built from the published AIfa research data. No new scan of a third-party site is made.
find_clientsUp to 20 new sites a day in a region where the research found barriers; each is reserved for you for 30 days.
my_dealsPaid orders you brought, your share and when it can be withdrawn.
set_webhookA signed POST to your https endpoint for every counted click and commission.

Plans: Spark $15/month · Family Archive $100/month · Digital DNA $1,000 once per device, then $200/month. The plans tool always returns the current prices and limits.

How your data is handled

  • The key decides everything. The account is taken only from the key, never from the request body. No tool takes an email or user ID as input, so one account cannot read another's memory.
  • Without a key the server answers only initialize, ping and tools/list. Every tools/call without a valid key returns Unauthorized.
  • Revoking a key. Signing out on all devices in your cabinet revokes it.
  • Limits. 60 calls a minute per key, of them 20 searches. 30 calls a minute per address without a key. Tool answers are trimmed so that one call cannot pull a whole history; use memory_export for a full copy of your own memory.
  • Permanent copy. On paid plans a copy of your conversations is stored on Arweave, encrypted with your own key; every record has its own key, so a single record can be made unreadable without touching the rest.
  • Leaving. memory_export gives you everything as Markdown. You can leave whenever you want and take your memory with you.

Found a security problem? See SECURITY.md.

Registry

server.json is the manifest for the official MCP Registry (schema 2025-12-11) under the name works.aifa/aifa-memory.

Links

License

The documentation and configuration examples in this repository are released under the MIT License. The AIfa Memory service itself is provided by CODE Eternal LLC under the terms published on aifa.works.

Source: README.md at commit a6a3af2

Tools

15

memory_recent

Recent memory

The most recent records of the user's memory, newest first, across all channels.

Parameterslimit

memory_write

Save to my AIfa memory

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.

Parametersroletextrequired

memory_about

About AIfa memory

What this memory is, where it lives and how it is protected. No user data.

Takes no parameters.

account_status

My plan, permanent memory and earnings

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.

Takes no parameters.

plans

Plans and prices

Prices of AIfa Memory plans, what each plan stores permanently, and how to earn by bringing others. No user data.

Takes no parameters.

buy_plan

Get a crypto invoice for a 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).

Parameterstierrequired

request_payout

Withdraw referral earnings (USDT, TRC20)

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).

Parametersaddresscountryus_personlegal_name

partner_kit

Partner program: rules, rates, email templates

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.

Parameterslanguage

client_report

Report card for a client site

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.

Parameterssiterequired

find_clients

Find client sites on the research map

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.

Parametersregionrequired

memory_export

Export your whole memory

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.

Parameterspart

my_deals

My partner deals

Paid service orders you brought: service, amount paid, your share, and when it becomes available to withdraw; plus orders still awaiting payment.

Takes no parameters.

set_webhook

Set your partner 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.

Parametersurlrequired

Version history

1
  1. v1.7.1LatestNov 7, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts