Hex Image Audit

io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.2Updated Oct 24, 2026

Recomputes every record checksum in a .hex or .s19 firmware image and names the bad records, the ove

The publisher's own server: audit.domains - Domain Valuation

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Recomputes record checksums in .hex or .s19 firmware images and reports which records fail.

What you can do
The server works on Intel HEX and Motorola S-record firmware image files. It recomputes the checksum of every record and names the records that do not match, so an assistant can point at the exact bad lines in an image. The registry description also mentions reporting the overall result, but the tool list is not published.
When to use it
Useful when you are validating or debugging a firmware image before flashing it, or when a build produces a .hex or .s19 file and you want a quick integrity check of its records.
Requirements
Runs locally over stdio, started with npx from the npm package @readystack/hex-image-audit. Requires Node.js and the firmware image file on the local machine. Desktop only; no web execution. No accounts, API keys, or environment variables are declared.
Before you install
The published README does not describe this server's usage, so the actual behavior of the package cannot be confirmed from the supplied material. It reads local firmware files; verify the package and its publisher before running it on sensitive images.

Installation

In SourceWeft

  1. Open Hex Image Audit in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

readystack-themes

Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack

Source: README.md at commit ee1c884

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 18, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Audit integrations