ebill-mcp
Related Servers
Alternatives to ebill-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server providing access to the easybill REST API for managing invoices, customers, articles, payments, projects, and time tracking, with read-only mode by default.162819 npmMIT
- AlicenseNot gradedqualityCmaintenanceThis MCP server provides a single read-only tool to query official CPFL (electric utility) bill download data via a hosted, prepaid service without requiring platform credentials.MIT
- AlicenseNot gradedqualityCmaintenanceRead-only MCP server for downloading and OCR-processing CPFL electricity bills from official sources, supporting any MCP client with prepaid per-query credits.MIT
- AlicenseNot gradedqualityCmaintenanceRead-only MCP server for FinTS/HBCI banking; enables account information retrieval such as balances and transactions via PIN-TAN.MIT
- AlicenseAqualityAmaintenanceMCP server for the Canton of Bern tax portal TaxMe/BE-Login that reads account statements and tax returns via Playwright browser automation.135 npmMIT
- AlicenseNot gradedqualityBmaintenanceRead-only MCP server that exposes SAP Business One Service Layer and Cisco CCWR contract search APIs for querying sales orders, delivery notes, business partners, and service contracts, without modifying data.MIT
TDQS
Scored across 8 tools
Each tool has a distinct purpose: session status, login window, settings, bill listing, single bill retrieval, biller listing, single download, and bulk download. There is no overlap or ambiguity between them.
All tools share the 'ebill_' prefix, but naming conventions are mixed. Some verbs (open), some nouns (status, settings, billers), and some verb+noun (list_bills, get_bill, download_bill). This is readable but not strictly consistent.
8 tools is a well-scoped set for an e-bill retrieval and download service, comfortably within the ideal 3-15 range. Each tool serves a clear, necessary function.
The surface covers session management, configuration, bill listing, retrieval, and downloads (single and all). Minor gaps like a logout or payment operation could be argued, but they are not core to the stated purpose, so the workflow is largely complete.