Safe header name check
Remote MCP endpoint that checks whether an HTTP header name is safe
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About Safe header name check
Safe header name check is an MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.
This is one of many small single-purpose MCP endpoints published in the named-mcp-utilities repository. Each folder in that repo maps to one official registry name, and this one is registered as io.github.sadri-dridi/header-safe.
It runs as a hosted streamable-http remote rather than a package you install, so an MCP client connects to the remote URL directly. The registry entry describes it only as a safe header name check, and neither the registry entry nor the README says how it validates names, what it returns, or which tools it exposes.
The repo says these servers are aimed at autonomous clients and that each has its own intake. Because the repo also promotes an advertising service for agents, treat the endpoint as an experimental utility and review what it does before depending on it.
Install
Run in a terminal
claude mcp add --transport http header-safe https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/header-safe/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/header-safe/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"header-safe": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/header-safe/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"header-safe": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/header-safe/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"header-safe": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/header-safe/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"header-safe": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/header-safe/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- Header name check
- Offers a check described as a safe header name check.
- Remote streamable-http
- Served from a hosted streamable-http endpoint, so there is nothing to install locally.
- Registry-listed
- Published under the official MCP registry name io.github.sadri-dridi/header-safe.
- Single-purpose design
- Part of a collection where each folder is one registry name with a narrow function.
Good for
- Letting an agent test whether an HTTP header name is acceptable
- Trying a minimal remote MCP endpoint over streamable-http
- Exploring small utility MCP servers aimed at autonomous clients
Safe header name check FAQ
How do I connect to it?
Use the streamable-http remote URL from the registry entry in an MCP client that supports remote servers.
Do I need to install a package?
No. The registry entry lists no packages, only a hosted remote endpoint.
What is its registry name?
io.github.sadri-dridi/header-safe.
Which tools does it expose?
The available information does not list its tools.
How do I add Safe header name check to Claude Code?
Run this command in your terminal: claude mcp add --transport http header-safe https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/header-safe/mcp
What are the best alternatives to Safe header name check?
The closest alternatives to Safe header name check are Safe filename charset, name discarded, Git tag name safety, name discarded, Git branch name safety, name discarded, Git tag name safety, name discarded and Heading level 1-6 shape.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.