HMAC-SHA256 hex length, input discarded
Remote MCP endpoint reporting the hex length of an HMAC-SHA256 digest
- Pricing
- Open source
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About HMAC-SHA256 hex length, input discarded
HMAC-SHA256 hex length, input discarded is an open-source MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.
This server is one of many single-purpose endpoints published in the named-mcp-utilities repository. Its registry description says it returns the hex length of an HMAC-SHA256 digest while discarding whatever input is sent, so nothing is retained.
It runs as a remote streamable-http service hosted on a Cloudflare Workers address, with no local package to install. An MCP client connects to the registry-listed URL directly.
The repository README describes the endpoints as independently listed public MCP servers aimed at autonomous clients, each with its own registry name and intake. The same repo also lists date, ID-format and agent-advertising endpoints, so this one is best seen as a tiny utility probe, not a full cryptography toolkit.
Install
Run in a terminal
claude mcp add --transport http hmac-sha256 https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/hmac-sha256/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/hmac-sha256/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"hmac-sha256": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/hmac-sha256/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"hmac-sha256": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/hmac-sha256/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"hmac-sha256": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/hmac-sha256/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"hmac-sha256": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/hmac-sha256/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- HMAC-SHA256 length output
- Reports the hex length associated with an HMAC-SHA256 digest.
- Input discarded
- The registry description states that submitted input is discarded rather than kept.
- Remote streamable-http
- Connects over a hosted streamable-http URL with no local installation.
- Separate registry name
- Published under its own official registry name, io.github.sadri-dridi/hmac-sha256.
Good for
- Checking the expected hex length of an HMAC-SHA256 digest from an agent
- Testing an MCP client against a minimal remote streamable-http server
- Validating digest-length assumptions in an automated workflow
Pricing
Open source
HMAC-SHA256 hex length, input discarded FAQ
What does this server do?
Per its registry entry, it returns the hex length of an HMAC-SHA256 digest and discards the input.
How do I connect to it?
Use the streamable-http remote URL in the registry entry; no package is provided to install.
Where does the source live?
In the sadri-dridi/named-mcp-utilities GitHub repository, which lists many similar small endpoints.
Is HMAC-SHA256 hex length, input discarded free?
Yes. HMAC-SHA256 hex length, input discarded is open source, so you can use and self-host it for free.
How do I add HMAC-SHA256 hex length, input discarded to Claude Code?
Run this command in your terminal: claude mcp add --transport http hmac-sha256 https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/hmac-sha256/mcp
What are the best alternatives to HMAC-SHA256 hex length, input discarded?
The closest alternatives to HMAC-SHA256 hex length, input discarded are HMAC-SHA1 hex length, input discarded, SHA3-256 hex length, input discarded, SHA-3 hex length, input discarded, SHA-384 hex length, input discarded and SHA-512 hex length, input discarded.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.