# MCP Server Status

Live checks of 45 official remote MCP servers. Open one for its endpoint URL and step-by-step fixes.

URL: https://shortformkit.com/mcp-server-status/
Updated: 2026-10-14

We send each server the same first request an MCP client sends, initialize, at most once every five minutes. **Up** means the server answers. Most of these servers use OAuth, so the normal answer is HTTP 401, «sign in first»; that counts as up. **Down** means no answer, a timeout or a server error.

If a server is up here but your connector still fails, the cause is almost always on your side: an expired sign-in, an old URL or a blocked network. Each server page lists the fixes in the order that solves most cases. To check any other server, use the [MCP Server Tester](https://shortformkit.com/mcp-server-tester/); for servers that need no account at all, see the [free remote MCP servers](https://shortformkit.com/free-remote-mcp-servers/).

## How it works

1. **Find the server** Look it up in the live table.
2. **Read the status** Up with HTTP 401 is normal for OAuth servers.
3. **Open its page** Current URL and fixes, in the order that solves most cases.

## FAQ

**How do I know if an MCP server is down?**
Check the live table on this page. If a server answers our initialize request, even with 401 «sign in first», it is up. No answer or a 5xx error means it is down.

**Why does an MCP server return 401?**
Because it uses OAuth and the request had no token. That is the normal first answer; your client then opens the sign-in. A 401 after you signed in means the token expired or was revoked: remove and add the connector again.

**How often are the servers checked?**
At most once every five minutes per server, with a single initialize request.


Source: Shortform Kit (https://shortformkit.com/mcp-server-status/). Free, no login.