mcp-server-il-benefits
Related Servers
Alternatives to mcp-server-il-benefits
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables an LLM agent to search products, manage a shopping cart, and reorder from purchase history at the Rami Levy supermarket chain via its real API.7MIT
- FlicenseNot gradedqualityDmaintenanceEnables searching and comparing live credit card merchant offers (cash back, points, statement credits) across Amex, Chase, Citi, PayPal, Rakuten, and Capital One from any AI agent.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search and retrieve Israel's social services data, including service details, taxonomy, and location-based queries.MIT
- AlicenseNot gradedqualityBmaintenanceLets AI agents search merchant product catalogs, obtain signed offers with agent pricing, and run checkout sessions that always settle on the merchant's own payment page. It also scores any website's agent-readiness and exposes the published rubric checks.MIT
- AlicenseAqualityBmaintenanceLets an AI agent work with your own Amazon account in a separate local browser profile — reading order history and return deadlines, looking up products, and filling or editing the cart. Purchases happen only after you click "Place order" on an approval page, and no tool can place an order on its own.8MIT
- AlicenseNot gradedqualityDmaintenanceEnables searching and browsing products on KSP.co.il, one of Israel's largest electronics and retail stores, using natural language.35 npm6MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: best_way_to_pay queries benefits, list_sources explains data origins, wallet_get reads the saved wallet, and wallet_set writes it. The read/write pair is unambiguous, and there is no meaningful overlap between tools.
The set mixes three conventions: a natural-language phrase (best_way_to_pay), verb_noun (list_sources), and noun_verb (wallet_get, wallet_set). Names are readable but not predictable as a pattern.
Four tools map neatly onto the narrow domain (query benefits, inspect sources, read/write a wallet). It is slightly thin but each tool earns its place with no redundancy.
The surface covers query, source explanation, and wallet read/write for the benefits domain. Minor gaps exist, such as no way to add or remove individual providers (wallet_set replaces the whole list), but core workflows are served.