Generates SHA-384 cryptographic hashes from text input via GET /v1/hash/sha384. Returns 96-character hexadecimal strings for data integrity verification, checksums, and security applications. Available through MCP in Cursor and other AI editors, plus REST API. SHA-384 offers stronger collision resistance than SHA-256 while remaining computationally efficient.
curl "https://tinyfn.io/v1/hash/sha384" \
-H "X-API-Key: YOUR_API_KEY"const response = await fetch('https://tinyfn.io/v1/hash/sha384', {
headers: { 'X-API-Key': 'YOUR_API_KEY' }
});
const data = await response.json();
console.log(data);import requests
response = requests.get('https://tinyfn.io/v1/hash/sha384',
headers={'X-API-Key': 'YOUR_API_KEY'})
data = response.json()
print(data)Connect your AI agent (Claude, Cursor, Windsurf, etc.) to TinyFn's hash tools:
{
"mcpServers": {
"tinyfn-hash": {
"url": "https://tinyfn.io/mcp/hash",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}SHA-384 is a cryptographic hash function producing 384-bit (96 hex character) digests. Use it when you need stronger collision resistance than SHA-256 but don't require SHA-512's full 512-bit output.
Call the hash_sha384 MCP tool with your text input in Cursor, Claude Code, or other supported editors. The AI agent will return the deterministic 96-character hash without requiring external libraries.
Returns lowercase hexadecimal strings exactly 96 characters long. For example, 'hello' produces 'a7b3e6c1c4d7e8f9...' format suitable for checksums, file verification, and security applications.
Yes, SHA-384 handles empty strings, Unicode characters, newlines, and special symbols. Empty string produces a specific deterministic hash, while Unicode is processed as UTF-8 bytes.
Yes, SHA-384 is deterministic and standardized (FIPS 180-4). The same input always produces identical output regardless of system, making it reliable for checksums and data verification.