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.

ALTWEB Context Loader

NPM · ALTWEB-CONTEXT

Loads signed ALTWEB context capsules — refuses unsigned, tampered, or untrusted by default.

Available components

+9 this week 95 Trust /100

Last scanned (18 hours ago)

Scores higher than 98% of npm servers

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security99
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 7 of 46 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to danielsoimu/altweb). View diagnostics → Pass
  • Clear OSI-approved license (AGPL-3.0-or-later).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 212 tokens (~70/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 15 Oct 26 +1

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

  • 14 Oct 26 +44
    • Injection markers: unverified → pass ▲ security
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.83 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 13 Oct 26 −36
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Provenance: fail → pass ▲ security
    • The attested source repository moved: danielsoimu/altweb security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Stability: pass → 0.80 functional
    • Package version: 1.1.0 → 1.1.2 functional
  • 12 Oct 26 0
    • Stability: 0.97 → pass security
  • 4 Oct 26 +1

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

  • 2 Oct 26 +1

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

  • 30 Sept 26 +1

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

  • 29 Sept 26 −3
    • Stability: pass → 0.80 functional
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 16 Oct 2026 · Analysed npm/altweb-context@1.1.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo danielsoimu/altweb
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/danielsoimu/altweb/.github/workflows/release.yml@refs/heads/main
Rekor log index 3245351844
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:6ccaa1bcf5bedcc4cdeaaf9f590796e218e20c1bf01880d2058412be6c90cfebfe947669d4501002e2fca50de2ae13f892405c6ee9a8375518467d216

Background: How many MCP packages publish verified provenance →

Dependencies 46 packages
Packages resolved 46
Stale 7
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~212 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
list_trusted_keys ~22

Show the signers currently allowed by the local trust file.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

load_capsule ~99

Verify an ALTWEB capsule and, only if its signature is valid AND the signer fingerprint is trusted, return its markdown content. Refuses unsigned, tampered, and untrusted capsules.

NameTypeReqDescription
passwordstring–Password for encrypted capsules
sourcestringyesCapsule source: path to a .altweb.html or .altweb file, a URL with #hash, a URL to a hosted standalone capsule, or the raw hash string

No output schema declared.

No examples provided.

verify_capsule ~91

Provenance report for an ALTWEB capsule (signed? verified? trusted? encrypted?) without returning its content.

NameTypeReqDescription
passwordstring–Password: for encrypted capsules the signature covers the decrypted payload
sourcestringyesCapsule source: path to a .altweb.html or .altweb file, a URL with #hash, a URL to a hosted standalone capsule, or the raw hash string

No output schema declared.

No examples provided.

Install

How do I install the ALTWEB Context Loader MCP server?

ALTWEB Context Loader runs locally as an npm package, launched with npx -y altweb-context. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · altweb-context

# add to Claude Code
claude mcp add software-altweb-altweb-context -- npx -y altweb-context
Common questions

What is the ALTWEB Context Loader MCP server?

ALTWEB Context Loader is an MCP server listed in the public MCP registry as software.altweb/altweb-context. Loads signed ALTWEB context capsules, refuses unsigned, tampered, or untrusted by default. This page covers its npm package (altweb-context).

Is the ALTWEB Context Loader MCP server safe to use?

ALTWEB Context Loader scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 ALTWEB Context Loader MCP server expose?

ALTWEB Context Loader exposes 3 tools: load_capsule, verify_capsule, list_trusted_keys. Their descriptions and schemas cost roughly 212 tokens of context every time the server is loaded.

Is the ALTWEB Context Loader MCP server still maintained?

ALTWEB Context Loader is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the ALTWEB Context Loader MCP server under?

ALTWEB Context Loader declares the AGPL-3.0-or-later licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.