Generates cryptographically secure HMAC-SHA512 hashes for message authentication and integrity verification. Use via MCP in Cursor or Windsurf, or call GET /v1/hash/hmac-sha512 with your message and secret key. Returns a 128-character hexadecimal digest. HMAC-SHA512 combines SHA-512's collision resistance with keyed authentication, making it ideal for API signatures and JWT tokens.
curl "https://tinyfn.io/v1/hash/hmac-sha512" \
-H "X-API-Key: YOUR_API_KEY"const response = await fetch('https://tinyfn.io/v1/hash/hmac-sha512', {
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/hmac-sha512',
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"
}
}
}
}HMAC-SHA512 requires a secret key and provides message authentication, while SHA-512 is just a hash function. HMAC proves the message came from someone who knows the key and hasn't been tampered with.
Call the hmac-sha512 tool with your message and secret key parameters. The AI agent will return a 128-character hex string that you can use for API authentication or data verification.
Returns a 128-character lowercase hexadecimal string (512 bits). For example: 'abc123' with key 'secret' produces a hash starting with 'd2d2d2...'
No, each unique message + key combination produces a different hash. The same message with the same key will always produce identical output, but changing either input completely changes the result.
Yes, HMAC-SHA512 is cryptographically secure and widely used for API signatures, webhook verification, and JWT tokens. Use a strong, randomly generated secret key of at least 64 bytes.