Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

crypto_keccak_generator

Read-onlyIdempotent

Compute Keccak-224/256/384/512 hashes for Ethereum and blockchain applications from text, hex, or base64 input. Returns hex digest with variant details and notes on Keccak vs SHA-3 differences.

Instructions

Keccak Hash Generator. Compute an original Keccak digest (Keccak-224/256/384/512) of a text, hex, or base64 input and return it as lowercase hex. This is the pre-NIST Keccak that uses 0x01 padding, so its output differs from final SHA-3 (0x06 padding) at every bit length; Keccak-256 is the function Ethereum uses for addresses and transaction hashing. Use crypto_sha3_generator instead when you need the NIST-standardized SHA-3, and reach for this tool when you specifically need Ethereum/blockchain-compatible Keccak. Runs locally on the input you provide: read-only, non-destructive, deterministic (no random salt), contacts no external service, and is rate-limited (30 requests/min anonymous). Returns the digest as hex plus the variant, output size, security level, and explanatory notes on the Keccak-vs-SHA3 difference.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputNoMessage to hash, interpreted per inputFormat. The empty string is valid and hashes the zero-length input.
variantNoKeccak bit length to compute. Defaults to keccak-256 (the Ethereum variant).keccak-256
inputFormatNoHow to decode input into bytes before hashing: UTF-8 text, hexadecimal, or base64.text

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputNoThe submitted message, echoed back.
inputFormatNoResolved input encoding (text, hex, or base64).
variantNoResolved Keccak variant in upper case, for example KECCAK-256.
digestNoThe Keccak digest as lowercase hex.
hashNoAlias of digest (same lowercase hex string).
hashLengthNoLength of the hex digest string in characters.
outputSizeNoHuman-readable output size, for example 256 bits (32 bytes).
securityLevelNoApproximate security level, for example 128-bit security.
descriptionNoShort description of the chosen variant.
differencesNoOne-line note on the padding difference from the matching SHA-3 variant.
applicationsNoTypical use cases for the chosen variant.
noticeNoNotice that this computes original Keccak using pre-standard SHA-3 padding.
technicalDifferencesNoMap of Keccak-vs-SHA3 technical differences (padding, standardization, domain separation, capacity).
implementationsNoMap of real-world Keccak usage notes (Ethereum, Bitcoin, Monero, academic).
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond annotations (readOnly, idempotent, non-destructive), description adds local execution, deterministic behavior, no external service contact, rate limiting, and return of variant and notes. No contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is information-dense but well-structured with clear sentences. Slightly verbose for some readers, but each sentence adds meaningful context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given rich annotations and expected output schema, description covers all key aspects: input formats, variants, use-case distinction, and behavioral properties. No missing information.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with detailed parameter descriptions. Description adds minimal extra value beyond mentioning default variant, but serves as reinforcement.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly defines the tool as computing Keccak digests for text/hex/base64 inputs, with specific mention of Ethereum/blockchain use. Distinguishes from crypto_sha3_generator by highlighting the 0x01 vs 0x06 padding difference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs when to use this tool (Ethereum/blockchain-compatible Keccak) versus crypto_sha3_generator (NIST-standard SHA-3), providing clear usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Jambozx/onlinecybertools-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server