Skip to main content
Glama
shiftyasan

Shiftyasan MCP Server

by shiftyasan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Shiftyasan MCP Server

No user-submitted related servers found.

    Related Servers

    • ticksy-mcp

      artkrsk
      A
      license
      A
      quality
      C
      maintenance
      MCP server for the Ticksy support ticket API, enabling AI agents to read and write support tickets.
      16
      4 npm
      MIT

    • SpaceTraders MCP Server

      TheValverde
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI agents to interact with the SpaceTraders API, managing agents, fleets, contracts, and trading operations in the SpaceTraders universe.
      MIT

    • w2w-mcp

      TheRealAlexV
      F
      license
      A
      quality
      D
      maintenance
      MCP server integrating with When2Work scheduling API, enabling AI assistants to query employee schedules, shifts, time off, and reports via a set of tools.
      7
      -

    • chouseisan-mcp

      soyalumno
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server to read and write events on chouseisan.com (Chouseisan), a Japanese scheduling tool, using unofficial HTTP protocol. Enables creating events, fetching schedules, and managing responses via AI agents or CLI.
      -

    • kaiten-mcp

      Happiest-d
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for managing Kaiten tasks through AI agents like Claude, enabling task retrieval, creation, updating, and time logging.
      14 npm
      2
      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

    A4.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct and non-overlapping purpose: validating input, running the solver, and checking async job status. There is no ambiguity in selecting between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase and underscores: validate_shift_input, solve_shift, get_solve_job. The naming is uniform and predictable.

    Tool Count5/5

    Three tools is a well-scoped set for a specialized solver API, covering validation, synchronous invocation, and asynchronous status retrieval without bloat or unnecessary redundancy.

    Completeness5/5

    The tool surface covers the full workflow: validate payload, run solver, and retrieve async result. There are no obvious missing operations for the stated domain of shift scheduling solving.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources