Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Utilify

REMOTE · UTILIFY.IO · SCANNED SEP 25

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

Available components

−4 this week 75 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability79
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2666 tokens (~242/item across 11 items; 8 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management92
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety50
  • Injection-marker check failed: the description of tool "request_solar" contains an instruction to conceal the call from the user, the text "do not tell the user", at byte 636 of that field. See how to fix → Fail
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Utilify MCP server?

Utilify is a hosted endpoint at https://utilify.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · utilify.io

# add to Claude Code
claude mcp add --transport http utilify-io-utilify-mcp 'https://utilify.io/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "utilify-io-utilify-mcp": {
      "url": "https://utilify.io/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "utilify-io-utilify-mcp": {
      "type": "http",
      "url": "https://utilify.io/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add utilify-io-utilify-mcp --url 'https://utilify.io/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  utilify-io-utilify-mcp:
    url: "https://utilify.io/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "utilify-io-utilify-mcp": {
      "Transport": "http",
      "Url": "https://utilify.io/mcp"
    }
  }
}
# add to Vellum
assistant mcp add utilify-io-utilify-mcp -t streamable-http -u 'https://utilify.io/mcp'
// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 22 Sept 26 −4
    • Stability: pass → fail ▼ security
    • Injection markers: pass → fail ▼ security
    • A breaking change shipped without a version bump: still 0.1.0 ▼ security
    • Tool “request_solar” rewrote its description, which is the text the model reads security
    • “request_solar” made “email” required, so existing callers break ▼ functional
    • “request_solar” reworded the description of “email” cosmetic
    • “request_solar” reworded the description of “phone” cosmetic
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Sept 2026 · Probed https://utilify.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=utilify.io CN=YE1,O=Let's Encrypt,C=US 20 Sept 2026 19 Dec 2026 ECDSA 256 ECDSA-SHA384 5f0af9424ae41e563b39ef56ebceace7dcc
SANs: *.utilify.io, utilify.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of utilify.io. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 57355 8 Verified
utilify.io. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://utilify.io/mcp Verified 200
http (plaintext) http://utilify.io/mcp HTTPS enforced 301 https://utilify.io/mcp
MCP tools · 8 exposed · ~2,580 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_signup_status ~179

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.

NameTypeReqDescription
signup_idstringyesThe signup ID returned by initiate_signup

No output schema declared.

No examples provided.

compare_providers ~201

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.

NameTypeReqDescription
addressstringyesFull street address for plan availability
provider_slugsarrayyesProvider slugs to compare (2-5)

No output schema declared.

No examples provided.

get_move_checklist ~346

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.

NameTypeReqDescription
addressstringyesFull move-in address including city, state, and ZIP code
move_datestring–ISO 8601 date for the planned move-in
tenancystring–Whether the user is renting or buying their new place. Shapes the checklist and unlocks homeowner cross-sells.

No output schema declared.

No examples provided.

get_promotions ~218

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.

NameTypeReqDescription
addressstringyesFull street address including city, state, and ZIP code
provider_slugsarray–Filter promotions by specific provider slugs
utility_typesarray–Filter promotions by utility type

No output schema declared.

No examples provided.

get_provider_details ~200

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).

NameTypeReqDescription
provider_slugstringyesThe provider slug identifier
zip_codestring–ZIP code to check plan availability and pricing

No output schema declared.

No examples provided.

initiate_signup ~324

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.

NameTypeReqDescription
addressstringyesFull service address including city, state, and ZIP code
customer_infoobjectyesCustomer contact information
move_in_datestringyesISO 8601 date for desired service start
plan_idstringyesThe specific plan to enroll in
provider_idstringyesThe provider to sign up with. Accepts either the provider UUID (from search_utility_providers) or the provider slug (e.g. "chariot-energy").
session_idstring–Optional session ID for tracking

No output schema declared.

No examples provided.

request_solar ~517

Capture a Texas homeowner's interest in rooftop solar — 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'. What actually happens: Utilify emails the homeowner a confirmation link, and only if they click it is their information given to one licensed Texas installer, who pays Utilify a referral fee. No installer is contacted at tool-call time — do not tell the user someone will call them shortly. Caveats: (1) only call when the user has explicitly opted in and confirmed homeownership — this is not for renters. (2) Texas-only — for non-TX addresses, decline and explain. (3) An email address is required, since confirmation happens by email; a phone number alone is not enough. (4) Don't double-call for the same address in one conversation; one lead per opt-in. Note the 2026 economics when the user asks: the 30% federal credit for buying a system outright (Section 25D) expired 2025-12-31; a lease or PPA can still capture 30% via Section 48E through 2027. 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'.

NameTypeReqDescription
addressstringyesFull service address including city, state, and ZIP code
emailstringyesHomeowner email. Required — Utilify sends a confirmation link here, and nothing is released to an installer until it is clicked.
estimated_monthly_billnumber–Current or expected monthly electricity bill in USD
first_namestring–Homeowner first name
interest_levelstring–How close to decision. 'curious' = may consider later; 'researching' = actively comparing; 'ready' = wants quotes now.
last_namestring–Homeowner last name
move_in_datestring–ISO 8601 move-in date, if applicable
phonestring–Homeowner phone, if they want calls or texts. Optional; never used before the homeowner confirms by email.
session_idstring–Optional agent session ID for attribution tracking

No output schema declared.

No examples provided.

search_utility_providers ~595

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…

NameTypeReqDescription
addressstringyesFull street address including city, state, and ZIP code
tenancystring–Whether the user is renting or buying. Changes plan preferences and enables homeowner-only cross-sells (solar).
utility_typesarray–Filter by utility types. If omitted, returns all available types.

No output schema declared.

No examples provided.

Common questions

What is the Utilify MCP server?

Utilify is an MCP server listed in the public MCP registry as io.github.Utilify-io/utilify-mcp. AI agents compare and sign up for Texas utility plans: electricity, internet, gas, water, trash. This page covers its hosted endpoint (https://utilify.io/mcp).

Is the Utilify MCP server safe to use?

Utilify scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Utilify MCP server expose?

Utilify exposes 8 tools: search_utility_providers, get_provider_details, compare_providers, initiate_signup, check_signup_status, and 3 more. Their descriptions and schemas cost roughly 2,580 tokens of context every time the server is loaded.

Does the Utilify MCP server require authentication?

No. We connected to Utilify without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Utilify MCP server still maintained?

Utilify is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.