Skip to main content
Glama
Chiiz0

ezmcd-mcp

by Chiiz0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ezmcd-mcp

No user-submitted related servers found.

    Related Servers

    • fallpharm-mcp

      sjgant80-hub
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a sovereign, MIT-licensed MCP server for professional-service workflows, running entirely on your infrastructure with Ed25519 cryptographic signing for every action.
      MIT

    • Support Workflow Lab

      ducnmm
      A
      license
      A
      quality
      C
      maintenance
      A local stdio MCP server that brings scattered tickets, transactions, and current policies together so a model can retrieve evidence, assess cases, and prepare reply and escalation drafts. All writes stay local and pending human review, with no ability to send messages, move money, change accounts, or publish content.
      7
      Apache 2.0

    • troth

      xgre1
      A
      license
      Not graded
      quality
      B
      maintenance
      A persistent AI partner MCP server that keeps identity, memory, goals and refusals in a local SQLite substrate, renting language work from Claude, ChatGPT, Kimi, local models or any BYOK OpenAI-compatible provider, with governed shell/fs/http tools, MCP "hands" gated by state-transition-validated cognition, loopback-only security, and tamper-evident audit.
      10
      AGPL 3.0

    • fallimmig-us-mcp

      sjgant80-hub
      A
      license
      Not graded
      quality
      C
      maintenance
      A sovereign, MIT-licensed MCP server for professional-service workflows, providing offline-capable, Ed25519-signed tools for autonomous agents and human developers.
      MIT

    • multi-mail-mcp

      claygeo
      F
      license
      A
      quality
      C
      maintenance
      Local-first MCP server for agents that need to work across multiple Gmail and Microsoft 365 accounts without cloud token storage.
      6
      -
    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

    B3.1/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools target clearly distinct resources or actions, and the descriptions explicitly clarify boundaries around account, cart, and checkout. The closest overlap is between order_pay and checkout_submit because both involve real payment, but the existing-order versus fresh-quote distinction is stated.

    Naming Consistency3/5

    All names use snake_case and are mostly resource_action, but the pattern is mixed: accounts_list and stores_favorites use plural resources while account_check and store_get use singular, and several names are noun_noun (order_status, product_detail). The conventions are readable but not fully consistent.

    Tool Count4/5

    17 tools is slightly above the typical 3–15 range, but the domain has several separate stages—account, store/menu, cart, checkout, payment/status—so each tool is largely justified. It is on the heavy side but not excessive for a safety-critical ordering workflow.

    Completeness3/5

    The core purchase flow is covered from account check through menu, cart, quote, payment, and status. However, cart editing is limited to add-only operations with no remove/update/clear, and there are no tools for order cancellation, order history, or store search/favorites management.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources