mcp-registry/io.github.apollowinner/billtruth · v1
As of 2026-10-22 20:30 UTC, the Apollowinner Billtruth MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 98.9% of Glimind's liveness checks. It had 17 outages in 90 days, with a median recovery of 9 minutes.
Real annual cost for every Texas electricity plan, from each retailer's Electricity Facts Label.
Point your MCP client at this streamable-http endpoint: https://billtruth.co/api/v1/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →
4 of 4 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 →
3 parameter(s) across 2 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Reachable 98.9% of the time over the last 30 days; median recovery 9 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
Handshake + tools/list takes ~1,999 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 →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.apollowinner%2Fbilltruth/fixes
{
"name": "check_territory",
"description": "Whether a zip is in the deregulated Texas market, and which TDU serves it.",
"inputSchema": {
"type": "object",
"required": [
"zip"
],
"properties": {
"zip": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "compare_plans",
"description": "Rank certified Texas electricity plans for a zip by real twelve-month cost at a monthly kWh average. Returns verified_as_of with every number.",
"inputSchema": {
"type": "object",
"required": [
"zip"
],
"properties": {
"zip": {
"type": "string",
"description": "Five-digit US zip code"
},
"detail": {
"enum": [
"summary",
"full"
],
"type": "string",
"description": "summary (default) is the ranking. full attaches the month-by-month receipt to each plan."
},
"monthly_kwh": {
"type": "number",
"description": "Monthly usage in kWh. Default 1000. Expanded into a Texas seasonal year."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "compare_this_house",
"description": "Rank certified Texas electricity plans for a street address using a twelve-month usage profile for that meter. Prefer this over compare_plans when the user has an address. The profile is an estimate for the premise, not Smart Meter Texas interval reads. If the meter is found but has no usage history, ranks against a modeled Texas seasonal estimate at 1,000 kWh/month and says so. Never store or repeat the street. Returns verified_as_of with every number.",
"inputSchema": {
"type": "object",
"properties": {
"zip": {
"type": "string",
"description": "Five-digit US zip code. Strongly recommended."
},
"esiid": {
"type": "string",
"description": "Meter id from a previous ambiguous result. Use this instead of address when the user picked a unit."
},
"detail": {
"enum": [
"summary",
"full"
],
"type": "string",
"description": "summary (default) is the ranking. full attaches the month-by-month receipt to each plan."
},
"address": {
"type": "string",
"description": "Street address including the house number. Do not send a URL."
}
}
},
"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.apollowinner/billtruth"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.apollowinner/billtruth"}) over MCP.
compare_this_house ~290 tokenscompare_plans ~165 tokensexplain_plan ~110 tokenscheck_territory ~58 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.apollowinner%2Fbilltruth?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.apollowinner%2Fbilltruth?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.apollowinner%2Fbilltruth.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.apollowinner%2Fbilltruth.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.apollowinner%2Fbilltruth?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:87cc41104b144e73…, first seen 2026-10-17, included at leaf 6249 of 64,653. Version history · verify what your client received.
Compare: most reliable data servers · most reliable search servers · most reliable knowledge 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-22 20:30 UTC, the Apollowinner Billtruth MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 98.9% of Glimind's liveness checks. It had 17 outages in 90 days, with a median recovery of 9 minutes.
Apollowinner Billtruth MCP server advertises 4 tools, including check_territory, compare_plans, compare_this_house, explain_plan.
Point your MCP client at this streamable-http endpoint: https://billtruth.co/api/v1/mcp
Glimind scanned all 4 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.