MIREA Lecture Assistant MCP
Related Servers
Alternatives to MIREA Lecture Assistant MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI clients to perform safe, read-only IT diagnostics and retrieve local runbooks, asset records, and knowledge articles through MCP, with allowlisted network checks and audit logging.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to query an Action1 RMM tenant for organizations, endpoints, groups, missing updates, vulnerabilities, automations, reports, users, and roles, and to build custom PowerShell-based reports whose results can be requeryed and read back. It also runs one-off PowerShell diagnostics as SYSTEM on selected Windows endpoints and allows limited report-related changes, while leaving endpoints, users, and organizations untouched.MIT
- FlicenseAqualityCmaintenanceEnables AI clients to query AxonHub admin data through natural language, including instance status, projects, channels, models, requests, and usage statistics, with read-only safeguards and sensitive-field redaction.8-
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to read local business data and request database mutations, while requiring human approval before updates or deletions are executed. It provides read-only tools, approval workflows, and audit logging to prevent autonomous destructive changes.-
- AlicenseAqualityCmaintenanceEnables AI agents to query Oracle WebLogic Server runtime state, health, and JVM metrics through the REST management API, and to start, shut down, or force-shut-down servers via Node Manager, all under a least-privilege account with allowlisting, read-only mode, and JSON audit logging for every call.4MIT
- AlicenseAqualityAmaintenanceEnables AI clients to perform Sisense environment operations such as governance, asset and user/group management, lifecycle tasks, and health checks using the calling user's own credentials.36MIT
TDQS
Scored across 6 tools
Each tool has a primarily distinct purpose: reads cover status, settings, schedule, and subject rules, while writes cover settings and subject rules. There is minor overlap between update_settings and set_subject_rule because both modify application configuration, but the descriptions clarify the boundaries.
The set uses consistent snake_case and a predictable get_ prefix for read operations. Minor deviations exist in write verbs (update_settings vs set_subject_rule) and number agreement (get_subject_rules vs set_subject_rule), but the overall pattern remains readable.
Six tools is well-scoped for the server's purpose of reading app status/configuration and managing settings and subject rules. No tool appears redundant, and the surface is neither thin nor bloated.
The read and configuration-write surface is mostly covered, but there is no way to refresh the schedule cache or trigger lecture-opening actions mentioned in the domain. Subject rules can only be set for existing subjects, with no broader subject lifecycle management.