# HTTP 102 processing

> HTTP 102 processing is an MCP server for developer tools. Remote MCP endpoint that explains the meaning of HTTP status code 102. 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-102
- **Categories:** [developer tools](https://ai-powered.com/categories/developer-tools)
- **Listing updated:** 2026-11-18

## About

This server is a single-purpose lookup hosted as a streamable-HTTP endpoint on a Cloudflare Workers domain. Its registry entry describes it only as the meaning of HTTP 102, the informational "Processing" status code, so it works as a tiny reference an agent can query rather than a general HTTP documentation tool.

It belongs to a larger collection of named MCP utilities in one repository, where each folder maps to its own registry name and its own endpoint. Sibling entries cover other narrow lookups such as calendar checks and identifier-format checks, plus a set of doors pointing to an advertising service for agents. No installable package is published; clients connect to the remote URL directly.

It suits developers and autonomous clients that want a quick, hosted answer about this one status code without running anything locally. The registry entry does not list individual tool names, so what the endpoint exposes beyond the description is not documented.

## Features

- **Single-topic lookup:** Answers one narrow question: what HTTP status code 102 means.
- **Remote streamable-HTTP:** Runs as a hosted endpoint that MCP clients connect to over streamable HTTP.
- **No local install:** The registry lists no packages, only a remote URL, so nothing needs to be installed or run.
- **Part of a utility set:** Sits alongside many other small named MCP servers in the same repository, each with its own registry name.

## Good for

- Let an agent look up what HTTP 102 Processing means while debugging web traffic
- Test connecting an MCP client to a remote streamable-HTTP server
- Use as a lightweight reference when explaining informational HTTP status codes

## Install

### Claude Code (Terminal)

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

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

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

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

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

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

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

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

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

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

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

## FAQ

### What does this MCP server do?

Its registry description says it provides the meaning of HTTP 102.

### How do I connect to it?

Use the streamable-HTTP remote URL listed in the registry entry; no package install is provided.

### Is it part of a larger project?

Yes, it is one of many named MCP utilities in the sadri-dridi/named-mcp-utilities repository, each with its own registry name.

### How do I add HTTP 102 processing to Claude Code?

Run this command in your terminal: claude mcp add --transport http http-102 https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-102/mcp

### What are the best alternatives to HTTP 102 processing?

The closest alternatives to HTTP 102 processing are HTTP 302 found, HTTP 100 continue, HTTP 101 switching-protocols, HTTP 422 unprocessable and HTTP 206 partial-content.

## 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 302 found](https://ai-powered.com/mcp/http-302-found): HTTP 302 found 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 101 switching-protocols](https://ai-powered.com/mcp/http-101-switching-protocols): HTTP 101 switching-protocols is an MCP server for developer tools.
- [HTTP 422 unprocessable](https://ai-powered.com/mcp/http-422-unprocessable): HTTP 422 unprocessable is an MCP server for developer tools.
- [HTTP 206 partial-content](https://ai-powered.com/mcp/http-206-partial-content): HTTP 206 partial-content is an MCP server for developer tools.
- [HTTP 502 bad-gateway](https://ai-powered.com/mcp/http-502-bad-gateway): HTTP 502 bad-gateway is an MCP server for developer tools.
- [HTTP 204 no-content](https://ai-powered.com/mcp/http-204-no-content): HTTP 204 no-content 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.

---
Source: https://ai-powered.com/mcp/http-102-processing
