Vexa
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Description from the maker (original English)
Manage anon.li email aliases, recipients and encrypted file drop metadata over OAuth.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://anon.li/api/mcpRun this in your terminal
claude mcp add --transport http anon-li https://anon.li/api/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"anon-li": {
"url": "https://anon.li/api/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"anon-li": {
"type": "http",
"url": "https://anon.li/api/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://anon.li/api/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account anondotli, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 440 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 16 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Vexa, emailmd, MCP WhatsApp Cloud
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
MCP server for WhatsApp Cloud API (Meta) — messages, media, and templates via Graph API
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Open-source email aliasing, end-to-end encrypted file sharing, and encrypted forms. Privacy by default.
👋 Welcome! If you prefer a visual tour, check out our 2-minute intro video on YouTube .
We built anon.li because we were tired of handing our sensitive files and real email addresses to black-box companies.
Create unique aliases for every service. Reply from your aliases without ever exposing your real identity. Emails pass through our servers for forwarding instead of being stored in a hosted mailbox.
Share files securely. Everything is encrypted in your browser using AES-256-GCM.
Build forms whose responses are encrypted in the respondent's browser. The application stores ciphertext and encrypted owner keys; authorized owners decrypt responses locally after unlocking their vault.
[!IMPORTANT]
This repository contains the Next.js web application and control plane. The production SMTP/Haraka delivery pipeline that receives and forwards alias email is a separate service and is not included here. You can run and develop Alias management locally, but end-to-end email forwarding requires your own compatible mail transport.
anon.li is an integration-backed application and deliberately fails fast when required infrastructure is missing. Local development requires Bun \>= 1.4.3, Node.js 24, and credentials for the services below.
| Service | Purpose | Required |
|---|---|---|
| PostgreSQL | Application data and encrypted metadata | Yes |
| Private Cloudflare R2-compatible bucket | Drop/Form ciphertext | Yes |
| Upstash Redis REST | Rate limits, locks, and webhook idempotency | Yes |
| Resend | Authentication and transactional email | Yes |
| Cloudflare Turnstile | Bot protection | Yes |
| Stripe | Billing client and webhooks | Yes |
| NOWPayments | Cryptocurrency checkout | No |
| GitHub/Google OAuth | Optional login providers | No |
| PostHog | Product analytics and error reporting | No |
PostgreSQL, an S3-compatible stand-in for R2, and an Upstash-compatible Redis REST endpoint can run locally with docker compose up -d (or podman compose); see the local development guide for the matching .env values, Turnstile test keys, Stripe CLI webhooks, and current limitations.
git clone https://github.com/anondotli/anon.li.git
cd anon.li bun install # also generates the Prisma client cp .env.example .env
bun run db:migrate:deploy
bun dev
Open http://localhost:3000. Blank optional provider variables are normalized as disabled; required variables are validated at startup. Use independent generated values for AUTH_SECRET, CRON_SECRET, IP_HASH_PEPPER, REPORT_ENCRYPTION_KEY, and DKIM_ENCRYPTION_KEY as documented in .env.example.
When you change prisma/schema.prisma, create a migration with bun run db:migrate --name concise_migration_name and commit it. Avoid bun run db:push except on a throwaway database: it skips objects that exist only in migration SQL (such as the partial unique index domains_domain_verified_key) and leaves no migration history, so db:migrate:deploy can no longer be applied to that database.
Before opening a pull request, run the same checks enforced by CI:
bun run audit
bun run check # lint, type-check, dead-code check, tests, and production build
Production databases must be updated with the committed Prisma migrations. Do not use prisma db push in production; it bypasses the reviewed migration history.
bun install --frozen-lockfile
bun run build bun run db:migrate:deploy bun run start
Set every required variable documented in .env.example in the deployment platform, back up the database before applying migrations, and run bun run db:migrate:deploy once per release before starting the new application version. The build command regenerates the Prisma client automatically. Use HTTPS for every public service origin; plain HTTP is accepted only for loopback development endpoints.
Vercel deployments also require CRON_SECRET and Upstash Redis. The production schedules are intentionally limited to Hobby-compatible daily/weekly expressions; see the cron operations runbook for the schedule, rollout checks, and failure handling.
Client-IP rate limits trust one edge only. Vercel is detected automatically. On a self-hosted origin behind Cloudflare, set TRUSTED_PROXY_PROVIDER=cloudflare and restrict direct origin traffic to Cloudflare's network; otherwise forwarding headers are spoofable.
anon.li Drop uploads and downloads blob data directly between the browser and R2 via S3 presigned URLs, avoiding server-side relay bottlenecks. Download URLs are short-lived; multipart upload URLs are bound to an upload ID, part number, and exact encrypted byte length and last up to seven days so very large transfers can complete.
r2.dev URL and do not attach a public custom domain. Public object access would bypass Drop expiry, revocation, recipient, and download-limit checks.R2_ACCESS_KEY_ID, R2_SECRET_ACCESS_KEY, R2_BUCKET_NAME, and the account S3 API endpoint (R2_ENDPOINT=https:// .r2.cloudflarestorage.com) in .env.GET, HEAD, and PUT from your application origin and expose the ETag response header. Browser transfers still go directly to R2; R2 does not charge internet egress fees.Cloudflare presigned URLs are supported on the S3 API domain, not on custom domains. Treat private-bucket access as a security requirement, not only a deployment preference.
Browser (plaintext + keys)
├─ HTTPS → Next.js app (auth, policy, metadata, presigned capabilities) └─ presigned HTTPS → private R2 bucket (ciphertext only)
Next.js app ├─ PostgreSQL (accounts, policy metadata, ciphertext metadata, wrapped keys) └─ Redis REST (rate limits, locks, webhook idempotency)
External providers: Resend, Stripe, Turnstile, optional NOWPayments/PostHog/OAuth Separate deployment: inbound/outbound alias mail transport
Next.js 16 (App Router) · React 19 · PostgreSQL + Prisma · Better Auth (magic links, email/password, TOTP 2FA) · Cloudflare R2 · Stripe · Upstash Redis · Resend · Tailwind CSS + shadcn/ui
Jurisdiction: Liechtenstein · Privacy Policy · Terms · AUP · DMCA
[GNU Affero General Public License v3.0](https://github.com/anondotli/anon.li/blob/main/LICENSE) - Copyright © 2026 anon.li.