mcpbeat

Connectivity Index MCP Server

io.github.futuremultihousing-dev/connectivity-index
not responding

Connectivity Index is listed as active in the registry but did not answer our last check.

Machine-readable FCC pre-diligence corpus for multifamily broadband infrastructure scenarios.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 39 hours of history · worst hour 0%
39 hours agonow
0.0%
Uptime 24h
0 of 91 checks
—
Tools
hidden behind auth
266 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add connectivity-index --transport http https://connectivity-index-mcp-cloudflare.futuremultihousing.workers.dev
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "connectivity-index": {
      "url": "https://connectivity-index-mcp-cloudflare.futuremultihousing.workers.dev"
    }
  }
}
~/.codex/config.toml
[mcp_servers.connectivity-index]
url = "https://connectivity-index-mcp-cloudflare.futuremultihousing.workers.dev"
.cursor/mcp.json
{
  "mcpServers": {
    "connectivity-index": {
      "url": "https://connectivity-index-mcp-cloudflare.futuremultihousing.workers.dev"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "connectivity-index": {
      "url": "https://connectivity-index-mcp-cloudflare.futuremultihousing.workers.dev"
    }
  }
}

Endpoints

URLTransportStateLatencyChecked
https://connectivity-index-mcp-cloudflare.futuremultihousing.workers.dev streamable-http answering 266 ms 13 min ago

Connectivity Index — questions

Answers built from our own checks of this server.

Is Connectivity Index working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 266 ms. The bar chart above shows every period we have measured.
Is Connectivity Index still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
The registry lists Connectivity Index as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Connectivity Index?
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.
Does Connectivity Index need an API key?
No. Connectivity Index completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. This is what we observed, not what the docs claim.