Install the HTMLToolz products you can verify.

Use this center to copy install commands, get packages, confirm SHA-256 checksums, and move from a public diagnostic to the right paid or local product without hunting through separate product pages.

  • Checksums are served beside downloadable builds
  • AI Deck executable still requires account entitlement
  • Package routes use stable URLs for repeatable setup
Download readiness
AgentLockpackage online
Discord MCPpackage online
AI Deckentitlement required
Get-FileHash .\HTMLToolzAiDeck.exe -Algorithm SHA256
Install planner

Pick the path that matches your next job.

Each path keeps the user on the fastest route from a public HTMLToolz diagnostic to the product, command, verification step, and checkout path that fits the problem they are actually trying to solve.

Start with MCP FlightCheck No install required. Test handshake, discovery, schema size, and client compatibility before you publish or connect a server.
  1. Run a public MCP endpoint through FlightCheck.
  2. Open AI Tools Lab if the schema or client config needs cleanup.
  3. Install AgentLock only after the server shape is ready to lock.
Free package

AgentLock

Create deterministic lockfiles for AI agent dependencies, MCP identities, packages, models, and instruction files without storing secret values.

npm install -g https://htmltoolz.com/downloads/agentlock
  • Zero runtime dependencies
  • Designed for source-controlled lockfiles
  • Fails CI when agent dependencies drift
Windows app

AI Deck

Inventory AI CLIs, MCP client configs, local commands, and setup drift from one read-only Windows control center with sanitized exports.

  • Executable download requires AI Deck lifetime access
  • Checksum is public for release verification
  • Exports redact known credential values
Paid connector

Discord MCP

Run a local Discord MCP connector for Claude, Cursor, and MCP-capable assistants with a customer-owned bot token and HTMLToolz license gate.

npx -y https://htmltoolz.com/downloads/discord-mcp
  • Bot token stays on the customer machine
  • Destructive moderation tools require explicit confirmation
  • Lifetime connector access is purchased separately

Not sure what to install first?

Start with a public MCP scan, audit your pasted client config locally, then add the local package that closes the gap you found.