Crc
Checksum MCP — CRC-32 & Adler-32.
Open the source (opens github.com) https://github.com/pipeworx-io/mcp-crc
Before you use it
- Runs on someone else's server: what you send it leaves your machine.
- Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
- Needs credentials: PIPEWORX_API_KEY. Use a key with the least access you can.
What it is
MCP servers from io.github.pipeworx-io.
The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.
How to get it
npm package (stdio)
@pipeworx/mcp-crc@0.2.1
From the server's entry in the official MCP Registry
Remote endpoint (streamable-http)
https://gateway.pipeworx.io/crc/mcp
From the server's entry in the official MCP Registry
Settings it asks for
PIPEWORX_API_KEYsecret · Optional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.
Related
-
crc-mcp
MCP serversCRC-32, CRC-32C, CRC-16 variants and Adler-32 offline, with checksum check values verified, keyless.
@mrfentmen/crc-mcp@1.0.1 -
CRC16 hex, input discarded
MCP serversCRC16 hex, input discarded
-
CRC32 hex, input discarded
MCP serversCRC32 hex, input discarded
-
CRC8 hex, input discarded
MCP serversCRC8 hex, input discarded
-
CRC-16 hex length, input discarded
MCP serversCRC-16 hex length, input discarded
-
CRC-24 hex length, input discarded
MCP serversCRC-24 hex length, input discarded