Skip to main content
Glama
mitkozh

osiris-mcp-server

by mitkozh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to osiris-mcp-server

No user-submitted related servers found.

    Related Servers

    • University Course Catalog MCP

      Rushikesh-5706
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server exposing a university course catalog with tools for searching courses, looking up prerequisites and instructors, and generating prerequisite graphs, plus resources and a prompt template for AI academic advisors.
      -

    • ufind-mcp

      ParadoxTR
      A
      license
      A
      quality
      C
      maintenance
      An MCP server for the University of Vienna's course catalogue (u:find), enabling natural language queries for courses, programmes, staff, and schedules. Read-only, no account or API key required.
      13
      MIT

    • tudelft-mcp

      danieltyukov
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables TU Delft students to access their Brightspace courses, OSIRIS records, MyTimetable schedule, and the Study Guide through any MCP client. It handles sign-in and requires confirmation before performing write actions.
      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.1/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools are clearly distinct: list/get operations separate by resource (years, categories, faculties, course_types, courses). The main ambiguity is between get_course (header), get_course_details (full details), and get_course_details_by_id (full details by internal id) — get_course_details and get_course_details_by_id return the same data but keyed differently, and get_course's 'header' vs details boundary could cause misselection.

    Naming Consistency4/5

    The set follows a consistent get_/list_ verb prefix pattern (get_available_years, get_categories, list_courses, get_course, search_courses). Minor deviations exist: search_courses uses a different verb while other exploration tools use get_/list_, and get_course_details_by_id introduces the '_by_id' suffix that isn't used elsewhere.

    Tool Count4/5

    Ten tools is within the ideal range for a catalog/query server. Each tool earns a place: three discovery tools (years, categories, faculties/course_types), course listing/search, and course retrieval at different granularities.

    Completeness4/5

    The tool surface is strong for a read-only catalog: discovery (faculties, years, course types, categories), search, listing, and multi-level retrieval (header vs full details). The main gap is that get_course_details_by_id is redundant with get_course_by_code — agents could hit dead ends if they don't know which lookup path to use; a by-code variant of full details is also missing from the direct route.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources