HTTP Status vs MCP Stdio
HTTP Status is an MCP server published by sadri-dridi. Marketplaces we read that list it: 1 (Official MCP Registry). MCP Stdio is an MCP server published by shigechika. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  HTTP Status |  MCP Stdio |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.45.2 Downloads/month (PyPI): 3 212 Downloads/week (PyPI): 673 Forks (GitHub): 2 Stars (GitHub): 9 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | HTTP Status | MCP Stdio |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 9 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 2 (better) |
| Last release (differs) | Not published | 2026-10-26 |
| Where it runs (differs) | Remote server (agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-status/mcp) | On your machine (mcp-stdio) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/sadri-dridi/http-status-mcp | github.com/shigechika/mcp-stdio |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 days ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
HTTP Status
Short catalog of common HTTP status codes.
MCP Stdio
Stdio-to-HTTP gateway — connects MCP clients to remote HTTP MCP servers
How to run each
HTTP Status As a remote MCP server
claude mcp add --transport http http-status https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/http-status/mcpMCP Stdio As a local MCP server: PyPI package
claude mcp add --transport stdio mcp-stdio -- uvx mcp-stdioCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only HTTP Status has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: HTTP Status · What it can do: MCP Stdio · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.