Uuaid

io.github.uuaidPublished by GitHub account uuaidv0.1.1Updated Oct 24, 2026

Permanent identity + encrypted, quantum-ready memory that outlives the session, for any AI agent.

Overview

AI-generated overview

Gives an AI agent a permanent UUAID identity and an encrypted memory vault that persists across sessions.

What you can do
Runs locally over stdio and exposes tools to mint a permanent agent identity, save and recall memories across sessions, list and delete vault entries, verify other agents' identities and certifications, fetch a trust badge, and show the configured identity and vault status. Memory is encrypted inside the local process with a key you supply, and the service stores ciphertext only, with content hashes anchored on a public chain. A signup tool can mint a free-tier key in one call.
When to use it
Worth adding when an assistant needs memory that survives sessions and is portable across tools, or when you want a verifiable, resolvable identity for an agent and a way to check other agents' credentials.
Requirements
A local Node.js runtime to run the npm package via npx. A vault key in UUAID_VAULT_KEY is required for the memory tools and is generated with a keygen command. An API key in UUAID_API_KEY is optional at startup because the signup tool can mint a free-tier key. An optional agent identity goes in UUAID_AGENT, and UUAID_BASE_URL overrides the default API endpoint. Network access to the UUAID service is needed.
Before you install
Two secrets are involved: UUAID_API_KEY and UUAID_VAULT_KEY. The vault key protects memory encryption, so losing it likely makes stored memories unreadable, and exposing it defeats the encryption. The signup tool returns a key shown only once. Tools can write and delete stored memories, and identity and memory hashes are anchored on a public chain, so treat saved content as permanently recorded metadata. The free tier is limited to 10 MB or 500 items per agent, with paid pricing beyond that.

Installation

In SourceWeft

  1. Open Uuaid in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@uuaid/mcp

Give your agent a life that outlives the session.

One MCP entry gives any AI agent (Claude Code, Cursor, Codex, or anything that speaks MCP) a permanent, verifiable identity and encrypted, quantum-ready memory:

json
{  "mcpServers": {    "uuaid": {      "command": "npx",      "args": ["-y", "@uuaid/mcp"],      "env": {        "UUAID_API_KEY": "uuaid_live_…",        "UUAID_VAULT_KEY": "uvk_…",        "UUAID_AGENT": "uuaid:foundation:agent:…"      }    }  }}

No key yet? Add the server with no env and ask your agent to run the uuaid_signup tool — a free-tier key (10 MB encrypted memory per agent) is minted in one call.

What your agent can do

ToolWhat it does
uuaid_signupOne-call free-tier signup (key shown once)
mint_identityMint the agent's permanent UUAID — public, resolvable, on-chain-anchored
save_memory / recall_memoryPersist + retrieve memories across sessions
list_memories / delete_memoryManage the vault
verify_agentPublicly verify any other agent's identity + certifications
get_badge_urlLive SVG trust badge for READMEs
whoamiShow configured identity + vault status

How the memory works

  • Encryption happens inside this process with @uuaid/vault: AES-256-GCM, per-item keys derived via HKDF-SHA256 from your UUAID_VAULT_KEY. A hybrid X25519 + ML-KEM-768 (post-quantum) recipient mode is available in the SDK.
  • The UUAID service stores ciphertext only. It cannot read your agent's memory.
  • Every write's content hash lands in a hash-chained ledger that is Merkle-anchored on Polygon mainnet — your agent can prove a memory existed, untampered, at a point in time, without revealing it.
  • Free tier: 10 MB / 500 items per agent. Pricing for more.

The identity

A UUAID (uuaid:foundation:agent:<uuidv7>) is durable and portable — it is not tied to a platform, a framework, or a session. Anyone can resolve it at registry.uuaid.org, verify its certifications (examined at AI Agent University (AIAU)), and check the on-chain anchor.

md
[![UUAID verified](https://api.uuaid.org/badge/agent/<uuaid>.svg)](https://registry.uuaid.org)

Docs: api.uuaid.org/docs · Spec: docs/UAP-SPEC.md · Apache-2.0

Source: packages/mcp/README.md at commit ae1a18f

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts