@theyahia/atol-online-mcp
Related Servers
Alternatives to @theyahia/atol-online-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceMCP server for T-Kassa (T-Bank/Tinkoff) payment API. Provides 16 tools for payments, refunds, recurring charges, customer management, saved cards, SBP, receipts, and T-Invest portfolio.35MIT
- AlicenseAqualityAmaintenanceMCP server for YooKassa API enabling payments, refunds, receipts, payouts, webhooks, and more via 20 tools.20524MIT
- AlicenseAqualityDmaintenanceMCP server for Factura.uz electronic invoicing system (Uzbekistan). Supports creating, signing, accepting, and rejecting e-invoices, plus company and product lookups.87MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for iiko restaurant management system REST API, providing 39 tools to manage products, employees, entities, documents, payments, reports, and raw API access.1-
- AlicenseNot gradedqualityCmaintenanceMCP server for Belarus ERIP/E-POS/KROK payments via aggregator APIs, offering platform-specific tools for Express-Pay, bePaid, WEBPAY, Hutki Grosh, and Assist to manage invoices and payments.19MIT
- AlicenseNot gradedqualityNot gradedmaintenanceMCP server for Altegio API — appointments, clients, services, staff schedules1-
TDQS
Scored across 8 tools
Each tool has a clear, distinct purpose: token management (get_token, get_token_info), receipt creation for each fiscal operation type (sell, sell_refund, buy, buy_refund, correction), and report retrieval. No overlapping functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_token, create_sell_receipt). The use of 'get' for retrieval and 'create' for creation is consistent and predictable.
With 8 tools, the server is well-scoped for the ATOL Online fiscal receipt domain. Each tool covers an essential operation without unnecessary redundancy or bloat.
The tool set covers the full lifecycle of fiscal receipt management: authentication (token retrieval and info), all receipt types (sell, buy, refunds, correction), and status checking via report. No obvious gaps for typical 54-FZ operations.