HTTP 101 switching-protocols
Remote MCP endpoint that returns the meaning of HTTP status code 101
- Platforms
- API
- Runs
- Remotely
- Version
- 1.0.0
- Listing updated
- today
Similar MCP servers
About HTTP 101 switching-protocols
HTTP 101 switching-protocols is an MCP server for developer tools. It runs as a hosted remote server, so there is nothing to install locally.
This is a single-purpose remote MCP endpoint, registered as io.github.sadri-dridi/http-101, that answers one question: what HTTP 101 (Switching Protocols) means. It is served over streamable HTTP from a hosted worker, so there is nothing to install locally.
It belongs to a larger repository of small named MCP utilities, each published as its own registry entry with a separate endpoint. The README describes the collection as public MCP servers for autonomous clients. The repository also lists a set of doors that route agents to an advertising service, so the maintainer's wider interest in agent traffic is visible there.
The registry entry gives only a one-line description and no tool list, so exact inputs and outputs are not documented. It suits agent developers who want to try a minimal remote MCP connection.
Install
Run in a terminal
claude mcp add --transport http http-101 https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-101/mcpAdd to Settings → Connectors → Add custom connector
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-101/mcpAdd to ~/.cursor/mcp.json
{
"mcpServers": {
"http-101": {
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-101/mcp"
}
}
}Add to .vscode/mcp.json
{
"servers": {
"http-101": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-101/mcp"
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"http-101": {
"serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-101/mcp"
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"http-101": {
"type": "http",
"url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-101/mcp"
}
}
}Using several servers? Build one config file with the MCP config generator.
What it does
- Single-topic lookup
- Focused on explaining the meaning of HTTP status code 101.
- Streamable HTTP transport
- Exposed as a remote endpoint using the streamable-http MCP transport.
- No local install
- The registry lists no packages, only a hosted remote URL to connect to.
- Registry-named entry
- Published under its own official registry name as part of a collection of small utilities.
Good for
- Test a remote streamable-HTTP MCP connection from an agent client
- Let an agent look up what HTTP 101 Switching Protocols means
- Use as a minimal example of a hosted single-purpose MCP server
HTTP 101 switching-protocols FAQ
What does this server do?
Its registry description says it provides the meaning of HTTP 101.
How do I connect to it?
Point an MCP client that supports streamable HTTP at the remote URL in the registry entry, on the nolimit-observatory.workers.dev host.
Do I need to install a package?
No. The registry entry lists no packages, only a remote endpoint.
Is it part of a larger project?
Yes, it is one of many small named MCP utilities in the sadri-dridi/named-mcp-utilities repository.
How do I add HTTP 101 switching-protocols to Claude Code?
Run this command in your terminal: claude mcp add --transport http http-101 https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-101/mcp
What are the best alternatives to HTTP 101 switching-protocols?
The closest alternatives to HTTP 101 switching-protocols are HTTP 102 processing, HTTP 301 moved-permanently, HTTP 501 not-implemented, HTTP 404 not-found and HTTP 103 early-hints.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.