URL Alive Check MCP Server

by cedrickouma Your server? Claim it

answering

URL Alive Check is answering right now. Last checked 9 min ago. 25 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 · +77% w/w

a month agotoday

Uptime history 48 days of history · worst day 95%

48 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

717 ms

Response time

average over 24h

Installs / week

npm and PyPI

URL Alive Check does not always answer

Over the last week it answered 99.4% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

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 one needs environment variables set before it will start: AGENTFORGE_BASE_URL (AgentForge APIM gateway base URL), AGENTFORGE_API_KEY (APIM subscription key (Ocp-Apim-Subscription-Key / x-api-key)). The author declared them in the registry entry; get the values from the project itself.

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URL	Transport	State	Latency	Checked
https://apim-agentforge-6lfm33.azure-api.net/url-alive-check/mcp	streamable-http	needs key	714 ms	9 min ago

Alternatives to URL Alive Check

same job, measured the same way

Openapi Lint

by cedrickouma

MCP server (stdio): lint OpenAPI specs with Spectral via the AgentForge API

25 installs/wk answering

JSON Repair

by cedrickouma

MCP server (stdio): repair broken/malformed JSON via the AgentForge API

26 installs/wk answering

Fetch Extract

by cedrickouma

MCP server (stdio): fetch web pages as clean readable markdown via the AgentForge API

26 installs/wk answering

Schema Validate

by cedrickouma

MCP server (stdio): validate JSON against JSON Schema (draft-07 / 2020-12) via the AgentForge API

30 installs/wk answering

Robokassa MCP

by theyahia

MCP server for Robokassa payment API — generate payment URLs, check invoice status. First MCP for R

57 installs/wk local only

Sms Ru MCP

by theyahia

MCP server for SMS.RU API — send SMS, check status, balance. 3 tools.

44 installs/wk local only

Healthchecks Io MCP

by ronniechong

Unofficial MCP server for managing Healthchecks.io checks via the Management API

62 installs/wk local only

Trello MCP Server

by stucchi

MCP server for the Trello REST API – manage boards, lists, cards, labels, checklists and more

83 installs/wk local only

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: 100.0% 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 91 of 91 checks got a reply (100.0%), average response time 717 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: 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 717 ms on average, which is faster than 16% 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 25 times in the last week. Week over week that is +77%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.