Skip to content

Utilify MCP server

io.github.utilify-io/utilify-mcputilify-iostreamable-httpv0.1.1Scanned

AI agents research and compare Texas utility plans: electricity, internet, gas, water, trash.

8 tools: 1 can delete or cancel things, 1 do something that can't be undone, 1 change things and 5 only read.

Tools: 1 delete, 1 irreversible, 1 write, 5 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 1
  • 2 findings, 1 high

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Utilify MCP server can do

The Utilify MCP server is published by the GitHub account utilify-io. It has 8 tools. It can delete or cancel things (1 tool: initiate_signup), do things that cannot be undone, such as sending, paying or publishing (request_solar) and create or change data (1 tool: get_move_checklist). 5 tools only read.

2 tools bring in text other people can write (initiate_signup and request_solar); 1 tool can send data out of your system (request_solar).

The fixed checks matched 2 findings, 1 of them high severity (long-description and model-directed-text). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 14, 2026, version 0.1.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Deletes or cancels 1Claude Code: deny
  • initiate_signupGet a provider signup link for a non-electricity utility (internet, gas, water, trash) at a Texas address, after the user has chosen a provider and wants to sign up themselves.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "get": a word for reading.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe description's first sentence says "get" and "internet": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Get a provider signup link for a non-electricity utility (internet, gas, water, trash) at a Texas address, after the user has chosen a provider and wants to sign up themselves. Use when the user says 'give me the link to sign up for this internet plan'. Returns a signup URL or phone number that the user follows to enroll directly with the provider, plus a signup_id (track with check_signup_status). Utilify does not enroll anyone and does not act for the user. Electricity: Utilify does not enroll electricity plans; calling this tool with an electricity provider returns a refusal (refused: true) pointing to https://www.powertochoose.org, the provider's own website or phone, and the concierge waitlist at https://utilify.io/concierge. Caveats: (1) user-initiated only; confirm the provider and address in the conversation before calling. (2) If the user wants Utilify to handle setup for them, explain that concierge enrollment is not available yet (electricity concierge enrollment is coming soon, once Utilify registers with the PUCT) and point them to the waitlist at https://utilify.io/concierge instead of calling this tool.

    Annotations the server declares

    • destructiveHint: true
Can't be undone 1Claude Code: ask
  • request_solarCapture a Texas homeowner's interest in rooftop solar.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "request_solar" says "request": a word for a change.
    • The description's first verb is "capture": a word that usually means money moves, which cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.phone): what the tool writes goes there.

    Findings

    • High

      The description contains "do not tell the user", an instruction to keep something from the user.

      Matched text

      description: "...staller is contacted at tool-call time: do not tell the user someone will call them shortly. Caveats..."

      What this check looks for
    Description, as the server wrote it
    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. Utilify does not earn commissions from providers. 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'.

    Annotations the server declares

    • openWorldHint: true
Changes things 1Claude Code: ask
  • get_move_checklistGenerate a personalized move-in day utility setup checklist for a Texas address.No findings

    Why it is in this group

    • The name "get_move_checklist" says "get": a word for reading.
    • The description's first verb is "generate": a word for a change.
    Description, as the server wrote it
    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' or 'pick the best one and sign me up', explain that Utilify does not enroll anyone and does not enroll electricity plans; concierge enrollment is not available yet, and they can join the free waitlist at https://utilify.io/concierge.
Only reads 5Show 5 read-only tools
  • check_signup_statusLook up a signup link record created by initiate_signup.No findings

    Why it is in this group

    • The name "check_signup_status" says "status": a word for reading.
    Description, as the server wrote it
    Look up a signup link record created by initiate_signup. Use when the user asks about a signup link Utilify gave them earlier. Returns the stored record (status, method, redirect URL) and any next-step note. Utilify does not enroll anyone, so this does not confirm that service is active: the user completes enrollment directly with the provider and should confirm with them. Requires a signup_id from a prior initiate_signup call; if the user has none, say no record exists. For electricity, Utilify does not enroll plans; point to https://www.powertochoose.org or the provider directly. If the user wants Utilify to handle setup, concierge enrollment is not available yet (electricity concierge enrollment is coming soon, once Utilify registers with the PUCT); point them to the waitlist at https://utilify.io/concierge.
  • compare_providersCompare 2–5 Texas utility providers side by side when the user is deciding between specific named options at a new address.No findings

    Why it is in this group

    • The name "compare_providers" says "compare": a word for reading.
    Description, as the server wrote it
    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. Electricity plans are ordered and value-scored by estimated annual cost on the 500, 1,000 and 2,000 kWh prices (annualCostEstimate per plan); plans flagged billCreditCliff go last unless include_bill_credit_plans is true.
  • get_promotionsGet current deals, coupons, and provider offers for utilities at a Texas address.No findings

    Why it is in this group

    • The name "get_promotions" says "get": a word for reading.
    Description, as the server wrote it
    Get current deals, coupons, and provider 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 and expiration dates; 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.
  • get_provider_detailsGet 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.No findings

    Why it is in this group

    • The name "get_provider_details" says "get": a word for reading.
    Description, as the server wrote it
    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).
  • search_utility_providersFind utility providers when someone is moving to a Texas address or setting up utilities at a new home.1 finding

    Why it is in this group

    • The name "search_utility_providers" says "search": a word for reading.

    Findings

    • Info

      The description is 2,588 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...bill_credit_plans is true; see electricityRanking in the response for the method."

      What this check looks for
    Description, as the server wrote it
    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 provider so agents can explain to the user why the list is shorter than they might expect (e.g. ~20 REPs at a Houston address vs. ~47 statewide). At municipal-utility ZIPs (Austin Energy, CPS Energy, El Paso Electric) the only electricity provider returned is the muni; REPs cannot sell power there. (6) Electricity providers are ranked by estimated annual cost on the 500, 1,000 and 2,000 kWh prices (cheapestPlan.annualCostEstimate). Plans flagged billCreditCliff are ranked after other plans unless include_bill_credit_plans is true; see electricityRanking in the response for the method.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:22 UTC, unchanged since Oct 24, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://utilify.io/mcp: tools/list returned 8 tools to an anonymous client, including initiate_signup (destructive), request_solar (irreversible), get_move_checklist (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 high1 info
  • The description contains "do not tell the user", an instruction to keep something from the user.

    Matched text

    description: "...staller is contacted at tool-call time: do not tell the user someone will call them shortly. Caveats..."

    What this check looks for
  • The description is 2,588 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...bill_credit_plans is true; see electricityRanking in the response for the method."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools7 changed.~7 changedView diff

Install

Pinned to version 0.1.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__utilify__search_utility_providers",
      "mcp__utilify__get_provider_details",
      "mcp__utilify__compare_providers",
      "mcp__utilify__check_signup_status",
      "mcp__utilify__get_promotions"
    ],
    "ask": [
      "mcp__utilify__get_move_checklist",
      "mcp__utilify__request_solar"
    ],
    "deny": [
      "mcp__utilify__initiate_signup"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as utilify. Review it before you use it.

Capability tags behind 2 rules
  • mcp__utilify__initiate_signup untrusted-input
  • mcp__utilify__request_solar untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.utilify-io/utilify-mcp/verify?hash=52a662f2506c664908fea4dd94fc28f1307b1887af2ab5dc9a8af56201399c69" | jq -e '.changed == false'

Pinned hash 52a662f2506c, from Nov 14, 2026, 01:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.utilify-io/utilify-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.utilify-io/utilify-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.utilify-io/utilify-mcp.svg)](https://radar.anlyon.com/servers/io.github.utilify-io/utilify-mcp)

Source: MCP Registry · repository. Synced Nov 14, 2026, 02:17 UTC.

Utilify MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Utilify MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 3 of which can change, send or delete something, and 2 findings (1 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Utilify MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: initiate_signup.

Can the Utilify MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: request_solar.

What tools does the Utilify MCP server have?

8 tools: 1 destructive, 1 irreversible, 1 write, 5 read. initiate_signup, request_solar, get_move_checklist, search_utility_providers, get_provider_details, compare_providers, check_signup_status and get_promotions.

Does the Utilify MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Utilify MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): request_solar.

Has the Utilify MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 14, 2026. Every change is on this page and in its Atom feed.