Skip to main content
Glama
J-X0

westmere-recsys

by J-X0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to westmere-recsys

No user-submitted related servers found.

    Related Servers

    • overton

      hookdump
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Overton, an admission control daemon that gates coding agent dispatch based on per-account and per-project budget allocation. It lets agents ask for permission to run, returning verdicts such as go, wait, ask, or deny with retry timing to prevent overspending.
      0
      MIT

    • bank.mcp

      owieschon
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that turns bank transactions into a financial digest including cash-flow forecast, spending breakdown, fee detection, and receipt reconciliation, exposing deterministic engines as JSON-RPC tools.
      Apache 2.0

    • Deploy to Agents Server

      saezbaldo
      A
      license
      Not graded
      quality
      B
      maintenance
      Remote MCP server for auditing app surfaces in AI agent ecosystems, checking recommendation status, and creating distribution plans.
      19 npm
      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

    B3.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: recommend generates candidate rankings under budget, record_feedback logs observed rewards, and budget_status reports spend/remaining cap. There is no meaningful overlap between them.

    Naming Consistency3/5

    The names are readable but not fully consistent: 'record_feedback' follows a verb_noun pattern, 'recommend' is a bare verb, and 'budget_status' is noun_noun without an action verb. A consistent set like 'recommend_items', 'record_feedback', and 'get_budget_status' would improve predictability.

    Tool Count5/5

    Three tools is a well-scoped size for a focused recommendation/bandit service. Each tool covers a necessary part of the core workflow: recommending, recording feedback, and checking budget.

    Completeness4/5

    The core loop of recommend -> record_feedback -> check budget is covered, and there are no dead ends in that workflow. However, there is no tool for managing tenants, candidate items, or budget configuration, which are minor gaps if the server is expected to handle those resources.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources