mcp-registry/io.github.utilify-io/utilify-mcp · v0.1.0
Also listed as glama/utilify-io/utilify-mcp-server
As of 2026-10-23 06:47 UTC, the Utilify Io Utilify MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 6 minutes.
AI agents compare and sign up for Texas utility plans: electricity, internet, gas, water, trash.
Claude Code
claude mcp add --transport http utilify-io-utilify-mcp-server https://utilify.io/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"utilify-io-utilify-mcp-server": {
"type": "http",
"url": "https://utilify.io/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
Handshake + tools/list takes ~1,547 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
7 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.utilify-io%2Futilify-mcp/fixes
{
"name": "check_signup_status",
"description": "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), ",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"signup_id"
],
"properties": {
"signup_id": {
"type": "string",
"description": "The signup ID returned by initiate_signup"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "compare_providers",
"description": "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 candida",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"provider_slugs",
"address"
],
"properties": {
"address": {
"type": "string",
"description": "Full street address for plan availability"
},
"provider_slugs": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 5,
"minItems": 2,
"description": "Provider slugs to compare (2-5)"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_move_checklist",
"description": "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, tra",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"address"
],
"properties": {
"address": {
"type": "string",
"description": "Full move-in address including city, state, and ZIP code"
},
"tenancy": {
"enum": [
"rent",
"own"
],
"type": "string",
"description": "Whether the user is renting or buying their new place. Shapes the checklist and unlocks homeowner cross-sells."
},
"move_date": {
"type": "string",
"description": "ISO 8601 date for the planned move-in"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.utilify-io/utilify-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.utilify-io/utilify-mcp"}) over MCP.
request_solar ~498 tokensinitiate_signup ~482 tokenssearch_utility_providers ~338 tokensget_promotions ~303 tokensget_move_checklist ~295 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.utilify-io%2Futilify-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.utilify-io%2Futilify-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.utilify-io%2Futilify-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.utilify-io%2Futilify-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.utilify-io%2Futilify-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:f1b93b7f920d199f…, first seen 2026-10-17, included at leaf 11919 of 50,596. Version history · verify what your client received.
Compare: most reliable other servers · most reliable knowledge servers · most reliable productivity servers · most reliable search servers · most reliable communication servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-23 06:47 UTC, the Utilify Io Utilify MCP server is up with a Glimind reliability score of 91/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 6 minutes.
Utilify Io Utilify MCP server advertises 8 tools, including check_signup_status, compare_providers, get_move_checklist, get_promotions, get_provider_details.
Point your MCP client at this streamable-http endpoint: https://utilify.io/mcp
Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.