Skip to content

AlloFlow Remediation MCP mcpb-v0.3.5

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 17 Aug 07:12
· 45 commits to main since this release
mcpb-v0.3.5
facd0de

AlloFlow Remediation MCP for Claude Desktop

This is the local-first AlloFlow document-remediation connector. It runs on your computer; it does
not require an AlloFlow account, institution account, Cloudflare Worker, or paid AlloFlow service.

Install

  1. Download alloflow-remediation.mcpb from this release.
  2. In Claude Desktop, open Settings > Extensions and install or drag in the downloaded file.
  3. Ask Claude to run remediation_capabilities.
  4. If Chromium is not installed, ask Claude to run remediation_setup once.
  5. The Gemini key is optional. Deterministic tools such as PDF/UA validation, text extraction,
    redaction, structure checks, contrast repair, form conversion, alternative-format export, and
    resource-pack generation work without it.

Privacy boundary

Local/keyless tools keep document processing on the machine. Tools described as requiring Gemini
send the selected document or content to Google's Gemini API under the user's own key. Installing
this extension does not make third-party processing FERPA compliant. Review PRIVACY.md before using
AI-dependent tools with education records.

Verify the download

Compare the file with SHA256SUMS.txt. GitHub CLI users can additionally verify that GitHub Actions
built the exact bytes from this repository:

gh attestation verify alloflow-remediation.mcpb -R Apomera/AlloFlow

The CycloneDX file covers packaged npm dependencies. vendor-manifest.json records the SHA-256 and
byte count of every separately bundled browser-runtime asset; THIRD_PARTY_NOTICES.md documents those
third-party components.

Registry discovery

This release is also the install source for the official MCP Registry entry
io.github.Apomera/alloflow-remediation. Registry discovery installs these same checksum-bound MCPB
bytes; it does not route documents through an AlloFlow or Cloudflare server. Registry publication is
a separate explicit maintainer action after the GitHub release has passed provenance verification.

First useful requests

  • Audit this document for accessibility and explain what can be checked locally.
  • Extract the text from this document without uploading it anywhere.
  • Validate this PDF for PDF/UA-1 locally.
  • Redact these exact student identifiers from this accessible HTML and verify they are gone.
  • Convert this accessible HTML to EPUB, DAISY, or uncontracted Braille.
  • Remediate this document thoroughly. Before sending anything to Gemini, tell me what will leave my
    computer and ask for confirmation.
Assets 10
Loading