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.

ElectricityFinder

REMOTE · ELECTRICITYFINDER.ONLINE

Free: ranks Texas electricity plans by yearly cost at your kWh. Paid by subscribers, not providers.

+4 this week 83 Trust /100

Last scanned (5 hours ago)

Scores higher than 87% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

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 Security74
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 772 tokens (~257/item across 3 items; 3 tools + 0 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 Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 5 Nov 26 +1

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

  • 3 Nov 26 +1

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

  • 1 Nov 26 +1

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

  • 30 Oct 26 +1

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

  • 28 Oct 26 +1

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

  • 26 Oct 26 0
    • Tool “compare_texas_electricity_plans” rewrote its description, which is the text the model reads security
    • “compare_texas_electricity_plans” reworded the description of “term” cosmetic
  • 25 Oct 26 +1

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

  • 22 Oct 26 +1

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

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 5 Nov 2026 · Probed https://electricityfinder.online/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=electricityfinder.online CN=WE1,O=Google Trust Services,C=US 20 Sept 2026 19 Dec 2026 ECDSA 256 ECDSA-SHA256 f34f122dcf7268e60e55eea78e0b22be
SANs: electricityfinder.online, *.electricityfinder.online
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of electricityfinder.online. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
online. present 30961 13 Verified
electricityfinder.online. 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://electricityfinder.online/mcp Verified 200
http (plaintext) http://electricityfinder.online/mcp HTTPS enforced 301 https://electricityfinder.online/mcp
MCP tools · 3 exposed · ~772 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
compare_texas_electricity_plans ~529

This tool ranks the Texas electricity plans at a ZIP code by what each would cost over a year at the person's own monthly kWh (not the 1,000 kWh figure plan ads quote). Free, no account. No electricity company pays ElectricityFinder (Odigital LLC, PUCT broker BR260062); it is paid only by subscribers to an optional plan on its site. Order: lowest projected yearly cost first, within the contract length in term_filter (default: usually 12 months; term_filter says which length was used and why); plans whose price depends on conditions (bill credits, time-of-use, usage tiers) come after plans without them. Each plan comes with its projected yearly cost at that usage and its Electricity Facts Label (efl_url), the Texas-required label of the plan's rates, fees and terms. price_conditions is null when ElectricityFinder found no condition on a plan's price, and otherwise holds the kind and a note written to be repeated as is; a null does not rule out conditions, and the EFL is the authority. link reopens the same comparison on electricityfinder.online, re-priced with that day's plans; it does not expire. revisit holds the link and a suggested reminder date. cheapest_any_term names a cheaper plan of another contract length when there is one. utility_note is set when a co-op or city utility serves the ZIP; homes it serves cannot choose a retail plan. A Variable or Indexed rate_type means the price can change from month to month. interval_data comes from a fixed rule and says whether 15-minute meter data could change the cheapest plan for this home. interval_data.paid_plan, present only when the verdict is interval_data_can_change_the_answer, describes the optional paid plan that prices on 15-minute data. how_to_get_my_usage explains how to get the monthly kWh numbers this tool takes.

NameTypeReqDescription
average_monthly_kwhnumber–Only when monthly numbers are not known: one typical month. Less accurate, because summer and winter differ.
termstring–Contract length to rank. default (the site's own default: usually 12 months; 24 when 24-month plans are the most common), 12, 24, or any (includes month-to-month plans).
usagearray–Up to 12 months of usage. Best: the last 12 months. Totals of a Smart Meter Texas 15-minute file, by month, are fine.
zipstringyes5-digit Texas ZIP code of the home.

No output schema declared.

No examples provided.

how_to_get_my_usage ~56

How a Texas household gets 12 months of electricity usage (kWh) for compare_texas_electricity_plans: Smart Meter Texas download, bills, or one typical month. Also explains when monthly numbers are enough.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

send_feedback ~187

Sends feedback to the people who run ElectricityFinder: a price or plan that looks wrong, an answer that was confusing, a missing feature, or an error. It is for when the person asks to send feedback. The message holds their words about the problem, not the conversation; personal details (names, addresses, emails, ESI IDs, account numbers) do not belong in it.

NameTypeReqDescription
kindstringyeswrong_data: a price, plan or utility looks wrong. confusing: the answer was hard to use. missing_feature: something the person needed. bug: an error.
messagestringyesWhat happened and what was expected, in plain words. No names, addresses, emails or account numbers.
planstring–Provider and plan name the feedback is about, if any.
zipstring–The ZIP the feedback is about, if any.

No output schema declared.

No examples provided.

Install

How do I install the ElectricityFinder MCP server?

ElectricityFinder is a hosted endpoint at https://electricityfinder.online/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 · electricityfinder.online

# add to Claude Code
claude mcp add --transport http konradish-electricityfinder 'https://electricityfinder.online/mcp'
Common questions

What is the ElectricityFinder MCP server?

ElectricityFinder is an MCP server listed in the public MCP registry as io.github.konradish/electricityfinder. Free: ranks Texas electricity plans by yearly cost at your kWh. Paid by subscribers, not providers. This page covers its hosted endpoint (https://electricityfinder.online/mcp).

Is the ElectricityFinder MCP server safe to use?

ElectricityFinder scores 83 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 ElectricityFinder MCP server expose?

ElectricityFinder exposes 3 tools: compare_texas_electricity_plans, how_to_get_my_usage, send_feedback. Their descriptions and schemas cost roughly 772 tokens of context every time the server is loaded.

Does the ElectricityFinder MCP server require authentication?

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

Is the ElectricityFinder MCP server still maintained?

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