vit-bhopal-vtop-mcp-server
Related Servers
Alternatives to vit-bhopal-vtop-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to log in to a student's VIT Bhopal academic portal and fetch attendance, marks, timetable, exam schedules, grades, calendar, and profile data. It also calculates bunk allowances, OD usage, and GPA/CGPA projections.174Apache 2.0
- AlicenseNot gradedqualityCmaintenanceMCP server that provides intelligent student assistance tools for academic calculations, attendance tracking, marks analysis, and syllabus reading via Groq LLM.16 npm1MIT
- AlicenseNot gradedqualityBmaintenanceA read-only MCP server that exposes courses, assignments, calendar events, announcements, participants, and course materials from IIIT Hyderabad's Moodle instance through browser automation with persistent CAS-authenticated sessions.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables an AI assistant to securely access a student's own VIT VTOP account through a read-only, structured MCP interface, providing academic summaries, CGPA, courses, attendance, assignments, events, feedback, and session status.MIT
- AlicenseBqualityDmaintenanceMCP server for Universidade de São Paulo's student systems (Moodle, JupiterWeb) enabling assistants to query grades, schedule, tasks, and more via secure backend.205GPL 3.0
- AlicenseAqualityBmaintenanceA read-only MCP server that lets students query Union College's Nexus (Moodle) account through natural language, covering courses, assignments, due and overdue work, grades, course materials, announcements, and calendar events, plus daily/weekly briefings and workload analysis. It uses Moodle's official web-service API with a personal student token, so it only reads the user's own data and never writes or scrapes.191MIT
TDQS
Scored across 33 tools
Most tools target clearly distinct resources and actions, and the descriptions proactively resolve near-overlaps (e.g. get_profile vs get_student_profile, get_marks vs get_internal_totals, get_leave_status vs get_leave_history, get_semesters vs get_semester_info). A few clusters remain somewhat confusable (the four curriculum tools and four marks/grades tools), but the descriptions generally steer correctly.
The set is uniformly snake_case with predictable verb_noun naming (get_*, apply_leave, cancel_leave, calculate_attendance, check_pass_eligibility). The only deviations are the verb-less auth tools (login, logout, session_status), which are reasonable given their role.
33 tools is heavy and sits in the over-large range, with some genuine redundancy (get_profile/get_student_profile, get_marks/get_internal_totals, three overlapping curriculum tools). However, the portal's breadth (auth, attendance, marks, curriculum, profile, fees, hostel leave, exams) justifies a large surface more than most.
Coverage is broad and lifecycle-aware: read access across attendance, marks, grades, curriculum, profile, fees and exams, plus a full two-step apply/cancel leave flow and a full auth flow. Only minor gaps exist (write operations for functions outside hostel leave, no exam re-evaluation/registration), which agents can work around.