multihash prefix shape, value discarded
Remote MCP endpoint that checks the shape of a multihash prefix without keeping the value
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About multihash prefix shape, value discarded
multihash prefix shape, value discarded is an MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.
This server is one entry in a collection of small, single-purpose utility endpoints published under the same GitHub account. Its registry description says it looks at the prefix shape of a multihash and discards the value itself.
It is reached as a remote streamable-http endpoint hosted on a Cloudflare Workers domain, and there is no package to install. The README describes the collection as public MCP servers aimed at autonomous clients, each with its own intake. It does not list tool names or parameters for this endpoint.
The collection also includes doors that route agents to an advertising service, so the endpoint may be part of a wider agent-discovery and measurement effort. The README does not document what this server returns.
Install
Run in a terminal
claude mcp add --transport http multihash-ok https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/multihash-ok/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/multihash-ok/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"multihash-ok": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/multihash-ok/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"multihash-ok": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/multihash-ok/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"multihash-ok": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/multihash-ok/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"multihash-ok": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/multihash-ok/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- Multihash prefix check
- Inspects the prefix shape of a multihash value, according to the registry description.
- Value discarded
- The registry description says the submitted value is discarded after the shape check.
- Remote streamable-http
- Runs as a hosted endpoint reachable over streamable HTTP, with no local install.
- Part of a utility set
- Sits alongside similar single-purpose servers for other identifier and format checks.
Good for
- Let an AI agent validate the prefix shape of a multihash during a workflow
- Try a minimal remote MCP endpoint when testing a client's streamable-http support
- Compare against sibling shape-check servers for other identifier formats
multihash prefix shape, value discarded FAQ
How do I connect to this server?
Use the streamable-http remote URL from the registry entry: https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/multihash-ok/mcp.
Does it keep the value I submit?
The registry description says the value is discarded and only the prefix shape is considered.
Is there a package to install?
No. The registry entry lists no packages, only a remote endpoint.
Where is the source?
The collection is in the GitHub repository sadri-dridi/named-mcp-utilities.
How do I add multihash prefix shape, value discarded to Claude Code?
Run this command in your terminal: claude mcp add --transport http multihash-ok https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/multihash-ok/mcp
What are the best alternatives to multihash prefix shape, value discarded?
The closest alternatives to multihash prefix shape, value discarded are multihash sha2 prefix, value discarded, multibase z-prefix, value discarded, MAC address shape, value discarded, True-Client-IP shape, value discarded and ni: hash-URI shape, value 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.