Developer · Remote MCP server

Connectivity Index

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

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.futuremultihousing-dev/connectivity-index
Version
1.0.1
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-03-13
Updated
2026-03-13
Publisher
futuremultihousing-dev (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/futuremultihousing-dev) · how
Repository
github.com/futuremultihousing-dev/connectivity-index
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://connectivity-index-mcp-cloudflare.futuremultihousing.workers.devx-api-key (required, secret)

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 404)
Handshake
HTTP 404
Checked on
2026-10-05

How the live check works

How to connect Connectivity Index

Connectivity Index is a remote MCP server: there is nothing to install. Its endpoint is https://connectivity-index-mcp-cloudflare.futuremultihousing.workers.dev, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

The registry entry declares an HTTP header for the connection: x-api-key (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
Config Dsl Lint Snippet PackYour config files are never compiled - nothing fails until deploy. 36 snippets and 28 lint rules for.Local · stdionpm: @readystack/config-dsl-lint-snippet-pack
Confluent MCPMCP server for Confluent Cloud: environments, Kafka clusters. Needs an API key.Local · stdionpm: confluent-mcp
Confucius DebugAI debugging with 980+ verified fixes. Search the YanHui KB - never repeat a mistake.Local · stdionpm: confucius-debug-mcp
ConnectionsAWS, GitHub and connected services from your agent, no keys to paste, plus local shell and browser.Local · stdionpm: connections-mcp
ConnectWise Control MCPManage ConnectWise Control (ScreenConnect) remote support and access sessions from one CLI or agent.Local · stdioMCP Bundle (.mcpb): Servosity/msp-skills/releases/download/connectwi
ConsensusCoordination for AI coding agents: declare plans, catch design conflicts early, share team memory.Remote · HTTPLive check: ✗ no handshakeconsensus-production-aed6.up.railway.app
Consent Proof Record LintReads the consent record your code stored and names every proof field GDPR Article 7(1) needs and yo.Local · stdionpm: @readystack/consent-proof-record-lint
ConsentLayerCookie consent for GDPR/CCPA: scan sites for trackers, configure consent banners, get install code.Remote · HTTPLive check: sign-in requiredapi.consentlayer.com