Home / MCP registry index / com.texashomebills/texas-electricity
TexasHomeBills — Texas electricity plans
com.texashomebills/texas-electricity in the official MCP registry.
Endpoint https://texashomebills.com/mcp.
The registry describes it as: Texas electricity plans by real annual cost, plus EIA/ERCOT grid and mobile-phone data (26 tools).
We read its 26 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
about electricity_utilities electricity_find_utility electricity_rank_plans electricity_cheapest electricity_plan electricity_compare_my_plan electricity_price_trends electricity_data_product electricity_news market_catalog market_wholesale_prices market_grid market_gas_prices market_texas_retail market_us_states market_large_load market_generation market_grid_demand market_outlook wireless_service market_weather market_delivery_charges market_provider_complaints market_regulatory electricity_ev_charging_cost
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-texashomebills-texas-electricity)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.