Connectivity Index

io.github.futuremultihousing-devPublished by GitHub account futuremultihousing-devv1.0.1Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

A remote MCP server exposing a machine-readable FCC pre-diligence corpus for multifamily broadband infrastructure scenarios.

What you can do
Provides access to a machine-readable FCC pre-diligence corpus covering multifamily broadband infrastructure scenarios. No individual tools are listed in the manifest, so the exact operations available to an assistant are not documented here. It is a hosted remote endpoint rather than a local package.
When to use it
Consider it when an assistant needs FCC-related pre-diligence reference material for multifamily broadband infrastructure work, such as early-stage research before a formal filing or assessment.
Requirements
A remote MCP connection to the provider's hosted endpoint over streamable HTTP. An API key is required and must be sent in the x-api-key header. No local runtime, packages, or environment variables are declared.
Before you install
The server requires an API key sent as the x-api-key header; treat it as a secret and avoid exposing it in logs or shared configurations. The manifest lists no tools, so review what the server actually exposes before relying on it. Queries and any data sent go to a third-party hosted endpoint.

Installation

In SourceWeft

  1. Open Connectivity Index in the dashboard and add it to a workspace.
  2. Connect x-api-key credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.futuremultihousing-dev%2Fconnectivity-index/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "connectivity-index": {
      "type": "http",
      "url": "https://connectivity-index-mcp-cloudflare.futuremultihousing.workers.dev/",
      "headers": {
        "x-api-key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.