# HTTP 101 switching-protocols

> HTTP 101 switching-protocols is an MCP server for developer tools. Remote MCP endpoint that returns the meaning of HTTP status code 101. It runs as a hosted remote server, so there is nothing to install locally.

- **Kind:** MCP server
- **Platforms:** API
- **Repository:** https://github.com/sadri-dridi/named-mcp-utilities
- **MCP Registry name:** io.github.sadri-dridi/http-101
- **Categories:** [developer tools](https://ai-powered.com/categories/developer-tools)
- **Listing updated:** 2026-11-18

## About

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.

## Features

- **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

## Install

### Claude Code (Terminal)

```sh
claude mcp add --transport http http-101 https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-101/mcp
```

### Claude Desktop (Settings → Connectors → Add custom connector)

```sh
https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-101/mcp
```

### Cursor (~/.cursor/mcp.json)

```json
{
  "mcpServers": {
    "http-101": {
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-101/mcp"
    }
  }
}
```

### VS Code (.vscode/mcp.json)

```json
{
  "servers": {
    "http-101": {
      "type": "http",
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-101/mcp"
    }
  }
}
```

### Windsurf (~/.codeium/windsurf/mcp_config.json)

```json
{
  "mcpServers": {
    "http-101": {
      "serverUrl": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-101/mcp"
    }
  }
}
```

### Other clients (your client's MCP settings (most use this shape))

```json
{
  "mcpServers": {
    "http-101": {
      "type": "http",
      "url": "https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-101/mcp"
    }
  }
}
```

## 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.

## Alternatives

- [HTTP 102 processing](https://ai-powered.com/mcp/http-102-processing): HTTP 102 processing is an MCP server for developer tools.
- [HTTP 301 moved-permanently](https://ai-powered.com/mcp/http-301-moved-permanently): HTTP 301 moved-permanently is an open-source MCP server for developer tools.
- [HTTP 501 not-implemented](https://ai-powered.com/mcp/http-501-not-implemented): HTTP 501 not-implemented is an MCP server for developer tools.
- [HTTP 404 not-found](https://ai-powered.com/mcp/http-404-not-found): HTTP 404 not-found is an open-source MCP server for developer tools.
- [HTTP 103 early-hints](https://ai-powered.com/mcp/http-103-early-hints): HTTP 103 early-hints is an MCP server for developer tools.
- [HTTP 100 continue](https://ai-powered.com/mcp/http-100-continue): HTTP 100 continue is an MCP server for developer tools.
- [HTTP 302 found](https://ai-powered.com/mcp/http-302-found): HTTP 302 found is an MCP server for developer tools.
- [HTTP status class 1xx-5xx](https://ai-powered.com/mcp/http-status-class-1xx-5xx): HTTP status class 1xx-5xx is an MCP server for developer tools.

---
Source: https://ai-powered.com/mcp/http-101-switching-protocols
