Loads signed and verifiable context capsules into AI agents while refusing unsigned or untrusted content to prevent context poisoning.
Also known as danielsoimu/altweb, altweb, altweb-context
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.1.2
- Last commit
- Oct 13, 2026
- License
- AGPL-3.0
What is ALTWEB Context Loader MCP?
ALTWEB Context Loader loads signed and verifiable context capsules into AI agents while refusing unsigned or untrusted content to prevent context poisoning.
Summary generated from the project's README
About ALTWEB Context Loader MCP server
Securing AI agent instructions and memory from unauthorized changes is the primary function of ALTWEB Context Loader. It prevents context poisoning by ensuring that only signed and verifiable markdown capsules are injected into an agent's workflow. Developers use the altweb-context MCP server to load these self-contained .altweb.html files, which can be compressed, encrypted with AES-256-GCM, or signed using ECDSA P-256.
To use this server, you must first generate a signing identity using the altweb CLI and add the corresponding public keys to a local trust file. The loader operates on a principle of refusal, meaning it will reject any unsigned or untrusted content by default. When an agent requests context, the server uses the load_capsule, verify_capsule, and list_trusted_keys tools to validate the provenance of the data before allowing the markdown to be injected into the session.
What you can do with it
- 1Preventing context poisoningAn AI agent can refuse to load any instructions or persona files that lack a valid cryptographic signature.
- 2Managing trusted identitiesYou can restrict an agent to only accept context from specific, pre-approved authors by maintaining a local trust file.
Written from the project's README. Every use case is checked against a quote from it.
How to install ALTWEB Context Loader MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall ALTWEB Context Loader MCP in Claude Code
$ claude mcp add altweb -- npx -y altweb-contextInstall ALTWEB Context Loader MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"altweb": {
"command": "npx",
"args": [
"-y",
"altweb-context"
]
}
}
}Install ALTWEB Context Loader MCP in VS Code
.vscode/mcp.json
{
"servers": {
"altweb": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"altweb-context"
]
}
}
}Install ALTWEB Context Loader MCP in VS Code CLI
$ code --add-mcp '{"name":"altweb","type":"stdio","command":"npx","args":["-y","altweb-context"]}'Install ALTWEB Context Loader MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"altweb": {
"command": "npx",
"args": [
"-y",
"altweb-context"
]
}
}
}Install ALTWEB Context Loader MCP in Codex
$ codex mcp add altweb -- npx -y altweb-contextInstall ALTWEB Context Loader MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.altweb] command = "npx" args = ["-y", "altweb-context"]
Install ALTWEB Context Loader MCP in Gemini CLI
$ gemini mcp add -s user altweb npx -- -y altweb-contextInstall ALTWEB Context Loader MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"altweb": {
"command": "npx",
"args": [
"-y",
"altweb-context"
]
}
}
}Configuration
ALTWEB_TRUST_FILEOverride the local trust file of allowed signer public keys (default: ~/.altweb/trusted-keys.json). A missing or empty trust file refuses every capsule.
| Name | Description | |
|---|---|---|
| ALTWEB_TRUST_FILE | Override the local trust file of allowed signer public keys (default: ~/.altweb/trusted-keys.json). A missing or empty trust file refuses every capsule. |
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachabledanielsoimu/altweb is public and reachablegithub.com/danielsoimu/altweb ↗Pass
- Package names this repository as its sourcealtweb-context names danielsoimu/altweb as sourcenpmjs.com/package/altweb-context ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for altweb-contextnpmjs.com/package/altweb-context/v/1.1.2#provenance ↗Pass
- Open source license (OSI)AGPL-3.0spdx.org/licenses/AGPL-3.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-13github.com/danielsoimu/altweb ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from altweb-contextPass
- No critical advisory in the package or its dependencies47 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubALTWEB — signed context capsules
Signed context capsules for AI agents — Markdown compiled into self-contained, verifiable, optionally encrypted artifacts + an MCP loader that refuses unsigned or untrusted context. Verify before you inject.
AI agents run on plain-text context: instructions, personas, skills, memory files. None of it has provenance — anything that can write those files can poison them. ALTWEB gives context a chain of custody, and makes the loader refuse anything that lacks one:
- Capsule — markdown compiled into a single
.altweb.htmlfile (or URL): content compressed (deflate), optionally encrypted (AES-256-GCM), optionally signed (ECDSA P-256). Self-contained — opens in any browser, verifies offline, needs no server: you hand someone a file, not a database. - Verified context loading — the
altweb-contextMCP server loads a capsule into your agent only when the signature is valid and the signer's public key is in your trust file. Unsigned, tampered, or untrusted capsules are refused at load time, with an explicit reason. Refusal is the default: an empty trust file rejects everything, signed or not.
you write MD ──► altweb compile --sign ──► capsule (.altweb.html / URL)
│
agent asks for context ──► altweb-context ──► verify signature + trust
│
trusted ──► markdown injected
everything else ──► REFUSED (reason)
Packages
| Package | What it is |
|---|---|
altweb |
CLI: altweb compile / decode / verify / keygen (packages/cli) |
altweb-context |
MCP server: load_capsule, verify_capsule, list_trusted_keys (packages/mcp) |
@altweb/core |
Headless engine: content model, codec, crypto, markdown, sanitize (bundled into both; npm release planned) |
@altweb/editor |
Notion-style editor (built on Novel) with one-click capsule export |
site/ |
Documentation site (Astro + Starlight) |
Quickstart
Both tools are on npm — nothing to clone. Run these commands outside a source checkout (inside this repository, npm resolves the local workspace package):
# create your signing identity (deterministic from a passphrase; only the
# public key + fingerprint are stored, in ~/.altweb/identity.json)
npx altweb keygen --save
# write, compile, sign
echo "# My agent's operating notes" > notes.md
npx altweb compile notes.md -o notes.altweb.html --sign
# verify anywhere, offline
npx altweb verify notes.altweb.html
Wire the loader into an MCP client (Claude Code example):
claude mcp add altweb-context -- npx -y altweb-context
(From source: npm install && npm run build, then use the bundles under
packages/*/dist/.)
Running from source
Node.js 20 or newer is required. From the repository root:
npm install
npm run build
# Create and save an identity with the locally built CLI
npm run keygen
# Start the editor in development mode
npm run dev
The editor prints its local URL (normally http://localhost:5173). The CLI can
be invoked as node packages/cli/dist/altweb.mjs <command>. Do not use npx altweb inside the checkout: npm may select the local workspace package, whose
executable does not exist until it has been built.
The documentation site is intentionally a separate npm project rather than a workspace. To run it locally:
npm install --prefix site
npm run dev --prefix site
Trust a signer by adding its full public key to ~/.altweb/trusted-keys.json
(the UNTRUSTED_KEY refusal message hands you the ready-made entry; the short
fingerprint is a human label, not the trust anchor):
{ "keys": [ { "name": "Me", "publicKey": "<base64url SPKI>", "fingerprint": "ab:12:..." } ] }
What a signature proves — and what it does not
A valid signature proves who authored the capsule and that the bytes are intact. It does not make the content safe or true. The trust file is your policy; keep it short.
Pick a long passphrase. Identities derive deterministically from your passphrase via Argon2id with a fixed protocol salt (that is what makes them portable with nothing stored). Memory-hardness makes mass dictionary attacks economically hostile, but the passphrase's entropy is still the identity's foundation. Use a 16+ character diceware-style phrase; the tooling enforces a minimum strength.
Security
Content is sanitized with DOMPurify on decode; artifacts carry a CSP; the
codec validates structure with zod. See site/ docs → Security model for the
full write-up, including the encrypted-capsule caveat (the signature covers
the decrypted payload, so verification completes after decryption).
Roadmap
Near-term, in rough order:
@altweb/coreon npm — the engine as an installable library, for programmatic use (the CLI and loader already ship it bundled).- Hardware-backed identity (FIDO2 / passkeys) — an optional identity type alongside the passphrase one: the private key lives in a security key or secure enclave, never extractable, signing requires physical presence. The passphrase identity stays the default — "a passphrase is a keypair" — hardware keys add something you have for those who want it.
Credits
Built on excellent open source: Novel (Apache-2.0) and Tiptap (MIT) for the editor; DOMPurify, marked, pako, zod, @noble/curves in the engine. See NOTICE.
License
ALTWEB is dual-licensed:
- Open source: AGPL-3.0-or-later. Free to use, study, modify,
and share — with one core obligation: if you modify ALTWEB and distribute it
or run it as a network service (e.g. hosting
altweb-contextfor others), you must release your modified source under the AGPL. - Commercial: by agreement. To use ALTWEB in a closed-source product, or as a hosted service without publishing your changes, you need a separate commercial license. See COMMERCIAL.md.
Copyright © 2026 Daniel C. ȘOIMU. Bundled third-party components keep their own (permissive) licenses — see NOTICE.
ALTWEB Context Loader MCP questions
How do I add ALTWEB Context Loader MCP to Claude Code?
Run claude mcp add altweb -- npx -y altweb-context in your terminal. Add --scope user to make it available in every project.
How do I add ALTWEB Context Loader MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What is an ALTWEB capsule?
A capsule is a markdown file compiled into a single, self-contained .altweb.html file or URL that can be compressed, encrypted, and signed.
How does the server handle untrusted context?
The server refuses to load any capsule that is unsigned, tampered with, or lacks a signer whose public key is in your local trust file.
How do I trust a new signer?
You must add the signer's full public key to your local trusted-keys.json file.