Skip to main content
Glama
shrey715

Mess MCP Server

by shrey715
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Mess MCP Server

No user-submitted related servers found.

    Related Servers

    • IIITH Mess MCP Server

      NJP6969
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to interact with the IIIT Hyderabad Mess Management System through natural language, allowing students to view menus, manage meal registrations, check bills, submit feedback, and configure preferences.
      29
      11
      MIT

    • IIITH Mess MCP

      Kallind
      A
      license
      A
      quality
      D
      maintenance
      Enables LLMs to interact with the IIIT Hyderabad Mess System to manage meal registrations, view menus, and track billing. It supports conversational commands for tasks like cancelling meals, estimating nutrition, and checking account balances.
      45
      5
      AGPL 3.0

    • morsel

      jirathip-dev
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables logging food meals by letting AI assistants analyze food photos and write structured meal data via MCP tools to a shared store, which can then be viewed in a dashboard.
      7 npm
      MIT

    • swiggy-lyr

      ishan-parihar
      A
      license
      Not graded
      quality
      B
      maintenance
      Aggregates Swiggy's food delivery, Instamart groceries, and Dineout table booking services into one MCP server, letting AI agents search, order, and book via a single OAuth token.
      MIT

    • mit-dining-mcp

      hongnoul
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time access to menus from all six MIT Bon Appétit dining halls. It enables users to query daily or weekly schedules and filter options by specific dietary requirements such as vegan, halal, or gluten-free.
      35 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools target distinct resource-action pairs (capacities, meal registration, extras, bills, auth, preferences), and descriptions clarify the scope. A few read operations overlap in name and intent, such as check_registrations vs get_registration and list_registered_extras vs list_extras_in_range, but the descriptions are sufficient to disambiguate.

    Naming Consistency4/5

    The server consistently uses snake_case and mostly follows a verb_noun pattern. However, verb selection is inconsistent: check_registrations vs get_registration, register_meal vs create_monthly_registration, cancel_meal vs delete_extra, and manage_skipping as a gerund all break the pattern slightly.

    Tool Count2/5

    27 tools exceeds the 25+ threshold and will feel heavy for an agent to navigate, even though the broad mess-management scope justifies some of the count. The number is high enough that an agent may struggle to choose efficiently among overlapping read operations.

    Completeness5/5

    The tool surface provides thorough lifecycle coverage: capacity checks, meal timings, meal and monthly registration CRUD, cancellation/skip workflows, extras booking, feedback, bills, config windows, auth key management, and preferences. No critical dead-end operations are missing.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources