Httpstatus MCP Server

by httpstatus Your server? Claim it

answering

Httpstatus is answering right now. Last checked 7 min ago.

AI-callable tools for API mocking, testing, monitoring, security, and automation.

Uptime history 47 days of history · worst day 92%

47 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

192 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Httpstatus every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp-server --transport http https://mcp.httpstatus.com/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.httpstatus.com/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.mcp-server]
url = "https://mcp.httpstatus.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.httpstatus.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.httpstatus.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.httpstatus.com/mcp	streamable-http	sign-in	251 ms	7 min ago

Alternatives to Httpstatus

same job, measured the same way

MCP Console Automation

by ooples

MCP server for AI-driven console application automation and monitoring

32 installs/wk local only

Zabbix MCP

by mhajder

MCP server for Zabbix monitoring and automation

695 installs/wk local only

Ninjaone

by lungshot

MCP server for NinjaONE RMM with device management, monitoring, and automation

local only

Anakin

by anakin

Web data for AI agents: scrape, crawl, search, deep research, site monitoring, browser automation

328 installs/wk local only

MCP Process

by digital-defiance

Process management and monitoring for AI agents with strict security boundaries

62 installs/wk local only

MCPower Security Proxy

by mcpower-security

Security proxy that automatically wraps MCP servers with real-time monitoring and policy enforcement

local only

Validoria MCP

by validoria

Continuous website testing by Validoria — monitor security, SEO, performance, and accessibility.

34 installs/wk 74 tools answering

Web

by rog0x

Web scraping, search, monitoring, and HTML-to-markdown for AI agents

32 installs/wk local only

Httpstatus — questions

Answers built from our own checks of this server.

Why is there no tool list for Httpstatus?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Httpstatus working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 192 ms. The bar chart above shows every period we have measured.

How do I connect Httpstatus?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to Httpstatus?

No API key is involved. Httpstatus answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is Httpstatus?

It answers our handshake in 192 ms on average, which is faster than 68% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.