TypeID prefix charset, value discarded
Remote MCP endpoint for checking a TypeID prefix's character set without keeping the value
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About TypeID prefix charset, value discarded
TypeID prefix charset, 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 MCP endpoints published under the sadri-dridi registry namespace. It is described as a TypeID prefix charset check where the submitted value is discarded rather than stored.
It runs as a hosted remote over streamable HTTP, so there is no package to install; an MCP client connects directly to the endpoint URL listed in the registry. The repository README describes the collection as public MCP servers aimed at autonomous clients, each with its own intake.
The README does not document the exact tool names, inputs or outputs of this endpoint, so developers should inspect the server's tool list after connecting. The same repository also hosts many sibling utilities (ID formats, calendar checks) and several endpoints that route agents to an advertising service.
Install
Run in a terminal
claude mcp add --transport http typeid-prefix https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/typeid-prefix/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/typeid-prefix/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"typeid-prefix": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/typeid-prefix/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"typeid-prefix": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/typeid-prefix/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"typeid-prefix": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/typeid-prefix/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"typeid-prefix": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/typeid-prefix/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- TypeID prefix check
- Targets the character set of a TypeID prefix, as stated in the registry description.
- Value discarded
- The listing states the submitted value is discarded after the check.
- Remote streamable HTTP
- Reached through a hosted streamable-http endpoint, with no local package to install.
- Part of a utility collection
- Published alongside many other narrow single-purpose MCP endpoints in the same repository.
Good for
- Validating the prefix portion of a TypeID in an agent workflow
- Adding a lightweight ID-format check to an MCP-capable client
- Testing remote streamable-HTTP MCP connections with a minimal endpoint
TypeID prefix charset, value discarded FAQ
How does this server connect?
It is a remote server using streamable HTTP, with the endpoint URL given in the MCP registry entry.
Does it keep the values I submit?
The description says the value is discarded.
Is there a package to install?
No packages are listed; it is accessed only as a remote endpoint.
Does it come with other tools?
The repository lists many sibling endpoints, each registered as a separate server.
How do I add TypeID prefix charset, value discarded to Claude Code?
Run this command in your terminal: claude mcp add --transport http typeid-prefix https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/typeid-prefix/mcp
What are the best alternatives to TypeID prefix charset, value discarded?
The closest alternatives to TypeID prefix charset, value discarded are TypeID prefix_suffix, value discarded, TypeID base32 suffix, value discarded, shortid charset, value discarded, short-uuid sid charset, value discarded and URL-ish token charset, 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.