Checksum Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.7Updated Oct 29, 2026

Compute file and text checksums locally with sha and md5. No network and no key.

VerifiedSTDIODesktop onlyDeveloper Tools

Server details

Identifier: io.github.mrfentmen/checksum-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 22, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account mrfentmen for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.mrfentmen%2Fchecksum-mcp.svg)](https://sourceweft.com/mcp/io.github.mrfentmen%2Fchecksum-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

A local MCP server that lets an assistant compute SHA and MD5 checksums of files and text on your own machine, with no network or API key.

What you can do: Compute SHA checksums of files and text
Compute MD5 checksums of files and text
Run entirely locally, with no network calls or credentials
When to use it: Useful when you want an assistant to verify file integrity, compare hashes, or fingerprint text and downloads without sending data to an external service.
Requirements: Runs as a local process installed from the npm package checksum-mcp over stdio, so Node.js and a desktop MCP client are needed. No accounts, API keys, headers or network access are declared.

Before you install

Checksums are computed locally and no credentials are requested. MD5 is not collision-resistant, so it is unsuitable for security-critical verification; prefer the SHA option for that.

Installation

In SourceWeft

Open Checksum Mcp in the dashboard and add it to a workspace.
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

This repository has no README.

Tools

SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not start.

Version history

v1.0.7LatestOct 29, 2026
v1.0.1Sep 22, 2026

Score

25% 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
License10 pts
Declare a license in the repository or the registry entry.