Creates HMAC-MD5 hashes using a secret key for message authentication. Access via MCP in Cursor or Windsurf for secure hash generation, or call GET /v1/hash/hmac-md5 with message and key parameters. Returns a 32-character hexadecimal digest. HMAC-MD5 combines MD5 hashing with key-based authentication to prevent tampering.
curl "https://tinyfn.io/v1/hash/hmac-md5" \
-H "X-API-Key: YOUR_API_KEY"
const response = await fetch('https://tinyfn.io/v1/hash/hmac-md5', {
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-md5',
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"
}
}
}
}
Pass your message and secret key to the endpoint. The tool combines them cryptographically to produce a 32-character hex hash that verifies both authenticity and integrity.
HMAC-MD5 uses a secret key for authentication, making it suitable for verifying message integrity. Regular MD5 is just a hash function vulnerable to collision attacks.
Yes, it's commonly used for API signatures. Generate the HMAC-MD5 of your request payload with a shared secret, then include the hash in headers for verification.
While HMAC-MD5 is more secure than plain MD5, prefer HMAC-SHA256 for new applications. HMAC-MD5 may be required for legacy system compatibility.
Returns a 32-character lowercase hexadecimal string, like 'a1b2c3d4e5f6789...'. This is the standard format for MD5-based hashes.