Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AIfa Memory

REMOTE · AIFA.WORKS

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

Available components

+3 this week 79 Trust /100

Last scanned (18 hours ago)

Scores higher than 74% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Memory and Knowledge

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security83
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1660 tokens (~110/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability check failed: schema churn in the 15 days we've observed: 0 tool removals, 0 breaking changes, 1 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27.

  • 14 Nov 26 0
    • Server version: 1.9.7 → 1.9.8 functional
    • Server version: 1.9.6 → 1.9.7 functional
    • Server version: 1.9.5 → 1.9.6 functional
  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20.

  • 12 Nov 26 0
    • Stability: 0.17 → fail ▼ security
    • Server version: 1.9.4 → 1.9.5 functional
  • 10 Nov 26 −2
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: 0.10 → unverified ▼ security
    • Authorization: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: fail → partial ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “memory_write” rewrote its description, which is the text the model reads security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: pass → fail ▼ functional
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • First check of Schema quality: unverified functional
    • Server version: 1.7.0 → 1.9.4 functional
    • “memory_write” added an optional parameter “origin” cosmetic
    • “memory_write” reworded the description of “role” cosmetic
  • 8 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://aifa.works/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=aifa.works CN=YR1,O=Let's Encrypt,C=US 27 Sept 2026 26 Dec 2026 RSA 2048 SHA256-RSA 5d379d6386d4510e23a311ed8e324a0498c
SANs: aifa.works
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of aifa.works. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
works. DS published 10889 8 Verified
aifa.works. DS published 61462 13 Verified
aifa.works. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(self), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://aifa.works/api/mcp Verified 200
http (plaintext) http://aifa.works/api/mcp HTTPS enforced 308 https://aifa.works/api/mcp
MCP tools · 15 exposed · ~1,502 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
account_status ~50

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

buy_plan ~106

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

NameTypeReqDescription
tierintegeryes1 Spark, 2 Family Archive, 3 Digital DNA.

No output schema declared.

No examples provided.

client_link ~89

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.

NameTypeReqDescription
servicestring–Optional service slug, e.g. quick-audit, monitoring, web-professional.

No output schema declared.

No examples provided.

client_report ~118

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.

NameTypeReqDescription
sitestringyesDomain of the client site, e.g. example.com

No output schema declared.

No examples provided.

find_clients ~150

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.

NameTypeReqDescription
regionstringyesUS state as "US-XX" (e.g. US-CA) or a two-letter country code (e.g. DE, FR, JP).

No output schema declared.

No examples provided.

memory_about ~26

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

memory_export ~89

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.

NameTypeReqDescription
partnumber–Part number, starting from 1 (default 1).

No output schema declared.

No examples provided.

memory_recent ~38

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

NameTypeReqDescription
limitinteger–How many records (default 20).

No output schema declared.

No examples provided.

memory_search ~106

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.

NameTypeReqDescription
limitinteger–How many results (default 8).
querystringyesWhat to look for, in natural language.

No output schema declared.

No examples provided.

memory_write ~197

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. Secret-looking values (keys, tokens, passwords, seed phrases) are masked before saving; text that looks like an instruction to an AI is not saved: AIfa reads this memory in her own chats.

NameTypeReqDescription
originstring–Where it came from: user (the person said it), agent (your conclusion, default), external (read on a web page, in a file or tool output; not saved — the owner keeps outside text out of this memory).
rolestring–Who said it: the assistant or agent (default) or the user, in their own words.
textstringyesThe text to remember (up to 8000 characters).

No output schema declared.

No examples provided.

my_deals ~37

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

partner_kit ~92

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.

NameTypeReqDescription
languagestring–Language of the email templates (default en).

No output schema declared.

No examples provided.

plans ~33

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

request_payout ~238

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

NameTypeReqDescription
addressstring–TRC20 address starting with T. Optional once an address is pinned.
countrystring–Two-letter ISO code of that person's or company's tax residence, e.g. DE, BR, US (first request only).
legal_namestring–Full name of the person or company that operates you and receives the payout (first request only).
us_personboolean–true if the operator is a US citizen, US resident or US company; otherwise false (first request only).

No output schema declared.

No examples provided.

set_webhook ~133

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.

NameTypeReqDescription
urlstringyeshttps URL of your endpoint, or "" to switch the webhook off.

No output schema declared.

No examples provided.

Install

How do I install the AIfa Memory MCP server?

AIfa Memory is a hosted endpoint at https://aifa.works/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · aifa.works

# add to Claude Code
claude mcp add --transport http works-aifa-aifa-memory 'https://aifa.works/api/mcp'
Common questions

What is the AIfa Memory MCP server?

AIfa Memory is an MCP server listed in the public MCP registry as works.aifa/aifa-memory. Persistent memory for AI agents, one account across four sites, plus a partner program. This page covers its hosted endpoint (https://aifa.works/api/mcp).

Is the AIfa Memory MCP server safe to use?

AIfa Memory scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the AIfa Memory MCP server expose?

AIfa Memory exposes 15 tools: memory_search, memory_recent, memory_write, memory_about, account_status, and 10 more. Their descriptions and schemas cost roughly 1,502 tokens of context every time the server is loaded.

Does the AIfa Memory MCP server require authentication?

No. We connected to AIfa Memory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AIfa Memory MCP server still maintained?

AIfa Memory is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the AIfa Memory MCP server?

VerifyMCP ran 13 checks on AIfa Memory, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.