mcpbeat

URL Alive Check MCP Server

io.github.CedricKouma/url-alive-check
answering

URL Alive Check is answering right now. Last checked 5 min ago. 33 installs a week from npm.

MCP server (stdio): check if URLs are alive (status, redirects, latency) via the AgentForge API

Installs per day peak 26 · avg 6 · +27% w/w
a month agotoday
Uptime history 41 hours of history · worst hour 67%
41 hours agonow
97.8%
Uptime 24h
89 of 91 checks
—
Tools
hidden behind auth
650 ms
Response time
average over 24h
33
Installs / week
npm and PyPI

Connect this server

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

run in your terminal
claude mcp add url-alive-check --transport http https://apim-agentforge-6lfm33.azure-api.net/url-alive-check/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "url-alive-check": {
      "url": "https://apim-agentforge-6lfm33.azure-api.net/url-alive-check/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.url-alive-check]
url = "https://apim-agentforge-6lfm33.azure-api.net/url-alive-check/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "url-alive-check": {
      "url": "https://apim-agentforge-6lfm33.azure-api.net/url-alive-check/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "url-alive-check": {
      "url": "https://apim-agentforge-6lfm33.azure-api.net/url-alive-check/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://apim-agentforge-6lfm33.azure-api.net/url-alive-check/mcp streamable-http needs key 690 ms 5 min ago

URL Alive Check — questions

Answers built from our own checks of this server.

Why is there no tool list for URL Alive Check?
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: 97.8% of checks in the last 24 hours got a reply.
Is URL Alive Check working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 91 checks got a reply (97.8%), average response time 650 ms. The bar chart above shows every period we have measured.
How do I connect URL Alive Check?
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 will need your own key or an OAuth login: it refuses anonymous clients.
Does URL Alive Check need an API key?
Yes. Every time we knock, URL Alive Check answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is URL Alive Check?
It answers our handshake in 650 ms on average, which is faster than 14% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use URL Alive Check?
The npm package agentforge-url-check-mcp was installed 33 times in the last week. Week over week that is +27%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.