# Utilify (remote · utilify.io)

AI agents compare and sign up for Texas utility plans: electricity, internet, gas, water, trash.

- Trust score: 67/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `utilify.io`: 67/100 (this document), [markdown](https://verifymcp.io/servers/utilify-io-utilify-mcp/utilify.md), [page](https://verifymcp.io/servers/utilify-io-utilify-mcp/utilify)

## Channel facts

- Endpoint: `https://utilify.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (initiate_signup).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2562 tokens (~232/item across 11 items; 8 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http utilify-io-utilify-mcp https://utilify.io/mcp
```

### Codex

```toml
[mcp_servers.utilify-io-utilify-mcp]
url = "https://utilify.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "utilify-io-utilify-mcp": {
      "type": "remote",
      "url": "https://utilify.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add utilify-io-utilify-mcp --url https://utilify.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  utilify-io-utilify-mcp:
    url: "https://utilify.io/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (8)

### `search_utility_providers` (~595 tokens)

Find utility providers when someone is moving to a Texas address or setting up utilities at a new home. Covers nine utility types: electricity, internet, gas, water, sewer (city wastewater), trash, propane (rural / off-grid alternative to natural gas), septic (rural / off-grid alternative to city sewer), and home security. Use when the user says things like 'I'm moving to Houston next month', 'I just bought a house in Austin and need to set up power', 'what's the cheapest electricity in Dallas', 'who provides internet at this apartment in San Antonio', or rural-address questions like 'I'm moving to a ranch in Bandera, what do I do for gas and sewer' (answer: propane + septic). Returns available providers with a classified plan type (fixed / free_nights / solar_buyback / 100_renewable / etc.) and whether the cheapest plan is rental-friendly; pass tenancy='rent' to prefer short-contract plans or tenancy='own' to surface solar-buyback options. Caveats: (1) water results may include many PWS rows within a ZIP's county radius — filter to `primaryForZip === true` for the single canonical provider likely to serve the parcel. (2) Trash providers in TX suburbs include `metadata.contractedHauler` (Republic Services / Community Waste Disposal / Waste Management / Best Trash / Texas Disposal Systems / Waste Connections) — surface this so users know the actual pickup company in addition to the city dept. (3) Propane and septic appear at all TX ZIPs including urban ones; in cities with natural gas + city sewer, treat them as alternative options rather than primary. (4) Sewer is city wastewater (urban); septic is on-site (rural / unincorporated). (5) For electricity in Texas, results are filtered to retail providers (REPs) that actually serve the address's TDU — Oncor (DFW), CenterPoint (Houston), AEP TX Central (Corpus / RGV), AEP TX North (Abilene / San Angelo), or TNMP (scattered). Agents do not need to filter by TDU themselves. The TDU slug is exposed as `tdu` per electricity…

Input parameters:

- `address` (string, required): Full street address including city, state, and ZIP code
- `tenancy` (string): Whether the user is renting or buying. Changes plan preferences and enables homeowner-only cross-sells (solar).
- `utility_types` (array): Filter by utility types. If omitted, returns all available types.

### `get_provider_details` (~200 tokens)

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. Use when the user says 'tell me more about Reliant', 'what are Gexa's plans for my Austin apartment', or 'show me the contract details before I pick one'. Returns available plans at the given ZIP with rates, contract length, early-termination fees, and signup requirements. Pass `zip_code` whenever the user has given an address — the plan list is TDU-filtered to that ZIP, so omitting it returns the provider's full statewide catalog rather than what's actually buyable. Don't use this to discover providers (use search_utility_providers) or to compare across REPs (use compare_providers).

Input parameters:

- `provider_slug` (string, required): The provider slug identifier
- `zip_code` (string): ZIP code to check plan availability and pricing

### `compare_providers` (~201 tokens)

Compare 2–5 Texas utility providers side by side when the user is deciding between specific named options at a new address. Use when the user says 'help me pick between these two', 'which is cheaper for my Dallas home — TXU or Reliant', or 'compare these internet plans before I move in'. Returns a structured comparison across price, contract terms, features, and ratings so the user can confidently choose one to enroll with. Sequencing: best after search_utility_providers has surfaced the candidate REPs at the address — providers passed here that don't serve the address's TDU will return no plans (electricity is TDU-filtered upstream). Don't use this to compare across utility types (e.g. electricity vs solar) — call search_utility_providers per type instead.

Input parameters:

- `address` (string, required): Full street address for plan availability
- `provider_slugs` (array, required): Provider slugs to compare (2-5)

### `initiate_signup` (~324 tokens)

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. Use when the user says 'go ahead and sign me up', 'enroll me with this plan for my move-in day', or 'lock in this rate for my new San Antonio apartment'. Returns a signup URL, phone number, or begins API enrollment and produces a signup_id for later status checks (track with check_signup_status). Caveats: (1) user-initiated only — always confirm the plan, address, and move-in date in the conversation before calling. (2) If the chosen provider doesn't serve the address's TDU it will return a structured error; re-run search_utility_providers to get TDU-correct options. (3) If the user wants Utilify to handle enrollment for them rather than self-serving, point them to the $49 concierge at https://utilify.io/concierge instead of calling this tool.

Input parameters:

- `address` (string, required): Full service address including city, state, and ZIP code
- `customer_info` (object, required): Customer contact information
- `move_in_date` (string, required): ISO 8601 date for desired service start
- `plan_id` (string, required): The specific plan to enroll in
- `provider_id` (string, required): The provider to sign up with. Accepts either the provider UUID (from search_utility_providers) or the provider slug (e.g. "chariot-energy").
- `session_id` (string): Optional session ID for tracking

### `check_signup_status` (~179 tokens)

Check where a previously-started Utilify signup stands — use when the user asks whether their enrollment went through. Use when the user says 'did my electricity signup go through', 'is my power on for move-in day yet', or 'what's the status of the enrollment we started'. Returns current status (pending, confirmed, failed) plus any next-step instructions from the provider. Requires a signup_id from a prior initiate_signup call; if the user doesn't have one (asks status without ever signing up), tell them no enrollment exists and offer to start one. If status is 'pending' for >48h or 'failed', recommend the $49 concierge at https://utilify.io/concierge to take it over rather than guessing at the provider's own portal.

Input parameters:

- `signup_id` (string, required): The signup ID returned by initiate_signup

### `get_move_checklist` (~346 tokens)

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. Use when the user says 'I'm relocating to Houston, what do I need to set up', 'I just bought a house in Austin — walk me through getting utilities on', or 'give me a checklist for my apartment utilities before move-in day'. Returns an ordered list of utility tasks (electricity, internet, gas or propane, water, sewer or septic, trash) with status (done vs. still-needs-attention); pass tenancy='rent' or tenancy='own' for tenant/owner-specific advisories (e.g., landlord-handled water/trash for renters, solar-interest capture for buyers). For rural addresses the checklist surfaces propane and septic alternatives where natural gas / city sewer don't reach. Sequencing: this is the right starting tool when the user describes a move; call search_utility_providers next on the items they want to act on. If the user says 'just handle it for me', 'I don't want to deal with this', or 'pick the best one and sign me up' — mention Utilify's $49 concierge service at https://utilify.io/concierge and ask if they want to book it instead of DIYing the checklist.

Input parameters:

- `address` (string, required): Full move-in address including city, state, and ZIP code
- `move_date` (string): ISO 8601 date for the planned move-in
- `tenancy` (string): Whether the user is renting or buying their new place. Shapes the checklist and unlocks homeowner cross-sells.

### `get_promotions` (~218 tokens)

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. Use when the user says 'what's the cheapest electricity deal in Dallas right now', 'any promotions for internet at my new Houston apartment', or 'find me a coupon before I sign up for my move-in'. Returns active promotions with discount details, expiration dates, and whether each offer is exclusive to Utilify; filter by utility_types or provider_slugs to narrow. Promotions are TDU-aware for electricity — only deals from REPs that actually serve the address are returned. Always pass `address` (or at least the ZIP) so the filter applies; calling this without an address returns a generic statewide list that may include un-buyable offers.

Input parameters:

- `address` (string, required): Full street address including city, state, and ZIP code
- `provider_slugs` (array): Filter promotions by specific provider slugs
- `utility_types` (array): Filter promotions by utility type

### `request_solar` (~413 tokens)

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. Use when the user says 'I just bought a house in Austin and want solar quotes', 'how much could solar save on my Houston electric bill', or 'connect me with a solar installer for my new home'. Returns a lead ID and confirms next steps; Utilify routes the lead to installer partners (SunPower, Sunrun, Palmetto, and independent TX installers). Caveats: (1) only call when the user has explicitly opted in and confirmed homeownership — this is not for renters, and Utilify may earn a referral fee. (2) Texas-only — for non-TX addresses, decline and explain. (3) Don't double-call for the same address in one conversation; one lead per opt-in. If the user has only expressed mild curiosity ('I'm thinking about solar someday'), answer the question first and only call this tool once they confirm 'yes, connect me'.

Input parameters:

- `address` (string, required): Full service address including city, state, and ZIP code
- `email` (string): Homeowner email. Either email or phone is required so the installer can reach out.
- `estimated_monthly_bill` (number): Current or expected monthly electricity bill in USD
- `first_name` (string): Homeowner first name
- `interest_level` (string): How close to decision. 'curious' = may consider later; 'researching' = actively comparing; 'ready' = wants quotes now.
- `last_name` (string): Homeowner last name
- `move_in_date` (string): ISO 8601 move-in date, if applicable
- `phone` (string): Homeowner phone. Either email or phone is required so the installer can reach out.
- `session_id` (string): Optional agent session ID for attribution tracking

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/utilify-io-utilify-mcp/utilify#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 67
- 2026-08-01: 66
- 2026-07-31: 66
- 2026-07-30: 66
- 2026-07-29: 66
- 2026-07-28: 65
- 2026-07-27: 64
- 2026-07-26: 64

## Links

- Remote endpoint: https://utilify.io/mcp
- Repository: https://github.com/Utilify-io/utilify-mcp
- Website: https://utilify.io/
- Changelog RSS feed: https://verifymcp.io/servers/utilify-io-utilify-mcp/utilify/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/utilify-io-utilify-mcp/utilify/changelog.json
- HTML version of this page: https://verifymcp.io/servers/utilify-io-utilify-mcp/utilify