Productivity

utilify.io

Helps users find, compare, and sign up for utility providers in Texas.

1 endpoint8 known toolsFirst detected May 18, 2026Last detected September 6, 2026

ENDPOINT 1

https://utilify.io/mcp

No auth detected

MCP server metadata

Name: utilify
Version: 0.1.0

Capabilities

tools.listChangedprompts.listChangedresources.listChangedlogging

Known tools 8

search_utility_providers

Find utility providers when someone is moving to a Texas address or setting up utilities at a new home.

Inferred read-only

get_provider_details

Get plans, pricing, and terms for a specific Texas utility provider — use after search_utility_providers has narrowed the list and the user wants to drill into one option.

Inferred read-only

compare_providers

Compare 2–5 Texas utility providers side by side when the user is deciding between specific named options at a new address.

Inferred read-only

initiate_signup

Start enrollment with a specific utility provider at a Texas address — use after the user has chosen a plan and confirmed they want to sign up.

Inferred read-only

check_signup_status

Check where a previously-started Utilify signup stands — use when the user asks whether their enrollment went through.

Inferred read-only

get_move_checklist

Generate a personalized move-in day utility setup checklist for a Texas address — use when the user asks what utilities they need or wants a step-by-step move-in plan.

Inferred read-only

get_promotions

Get current deals, coupons, and exclusive affiliate offers for utilities at a Texas address — use when the user wants the best available price, not just any provider.

Inferred read-only

request_solar

Capture a Texas homeowner's interest in rooftop solar and route to a licensed installer — use when the user owns (or is buying) a Texas home and mentions solar panels, solar quotes, solar savings, or reducing their bill through solar.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.utilify]
url = "https://utilify.io/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "utilify": {
      "type": "http",
      "url": "https://utilify.io/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: utilify
Remote MCP URL: https://utilify.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "utilify": {
      "url": "https://utilify.io/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "utilify": {
      "type": "http",
      "url": "https://utilify.io/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "utilify",
  "transport": "streamable-http",
  "url": "https://utilify.io/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.