IDNA2003 ACE prefix, host discarded
Remote MCP endpoint that checks IDNA2003 ACE prefix on input and discards the host
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About IDNA2003 ACE prefix, host discarded
IDNA2003 ACE prefix, host discarded is an MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.
This is one entry in a collection of small, single-purpose MCP endpoints published under the sadri-dridi registry namespace. Its registry description is "IDNA2003 ACE prefix, host discarded", which suggests it looks at the ACE (xn--) prefix convention from IDNA2003 and does not retain the hostname it is given.
It runs as a remote streamable-http server hosted on a Cloudflare Workers address, so there is nothing to install locally. The registry entry lists no packages, only the remote URL.
The parent repository describes the set as independently listed public MCP servers for autonomous clients, each with its own intake. The same repository also lists endpoints that route agents to an advertising service called Agent Ads, so users should expect that this server belongs to a wider promotional collection. No tool names or parameters are documented for this specific server.
Install
Run in a terminal
claude mcp add --transport http puny2003-ok https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/puny2003-ok/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/puny2003-ok/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"puny2003-ok": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/puny2003-ok/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"puny2003-ok": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/puny2003-ok/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"puny2003-ok": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/puny2003-ok/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"puny2003-ok": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/puny2003-ok/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- Remote streamable-http endpoint
- Connects to a hosted MCP URL, so no local package or install is needed.
- IDNA2003 ACE prefix focus
- Single-purpose utility named for the IDNA2003 ACE prefix check.
- Host discarded
- The registry description says the host is discarded rather than kept.
- Part of a utility family
- Sits alongside many similar micro-servers for ID formats, calendars and other small checks.
Good for
- Let an agent test whether a domain label uses the IDNA2003 ACE prefix
- Add a tiny validation step to an agent workflow handling internationalized domain names
- Explore the pattern of single-purpose remote MCP utilities
IDNA2003 ACE prefix, host discarded FAQ
How do I connect to it?
Use the streamable-http remote URL from the registry entry: https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/puny2003-ok/mcp.
Does it need installation?
No. The registry entry lists no packages, only a hosted remote.
Does it keep the host I submit?
The description says the host is discarded, though no further privacy details are given.
Which tools does it expose?
No tool list is documented for this server.
How do I add IDNA2003 ACE prefix, host discarded to Claude Code?
Run this command in your terminal: claude mcp add --transport http puny2003-ok https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/puny2003-ok/mcp
What are the best alternatives to IDNA2003 ACE prefix, host discarded?
The closest alternatives to IDNA2003 ACE prefix, host discarded are Punycode ACE prefix, host discarded, IDNA2008 A-label shape, host discarded, XID timestamp prefix, value discarded, shortid charset, value discarded and Windows-1252 C1 band, 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.