cvc-mcp
Related Servers
Alternatives to cvc-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceExposes USC's public course catalog API to AI agents, enabling natural-language queries about courses, GE requirements, schedules, and fees with optional filters for days, times, and open sections.16MIT
- FlicenseNot gradedqualityBmaintenanceEnables querying a local course catalog to list available courses and retrieve detailed records by course ID.-
- FlicenseNot gradedqualityDmaintenanceProvides intelligent access to a university course catalog with full-text search, prerequisite tracking, instructor lookups, and course comparison prompts.-
- FlicenseAqualityNot gradedmaintenanceEnables interaction with Canvas LMS courses and assignments directly from your LLM, allowing you to retrieve, search, and summarize course information, check due dates, and access assignment details without leaving your AI assistant.4189 npm-
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to explore, compare, and engage with postsecondary education and training offerings—programs, courses, certifications, credit transfer, prior learning, and career transitions—with sourced, snapshot-dated answers and explicit statements of missing data.-
- AlicenseAqualityAmaintenanceGives AI assistants direct, on-demand access to McGill's public Visual Schedule Builder timetable data, letting them search course offerings, fetch sections and meeting times, check conflicts, and generate ranked schedule combinations without a login, API key, or browser session. Queries and schedule calculations run locally on structured results, with a short-lived cache for repeated requests.42MIT
TDQS
Scored across 4 tools
get_course and scrape_courses are clearly distinct, but search_course_ids and scrape_course_ids both search for CVC course IDs and differ mainly by implementation. The descriptions help by marking one as preferred and the other as experimental fallback, but the boundary is still somewhat blurred.
All tools follow a consistent snake_case verb_noun pattern: get_course, search_course_ids, scrape_course_ids, scrape_courses. The verbs vary by operation type, but the structure is uniform and predictable.
Four tools is slightly small but well-scoped for a course search server. Each tool serves a clear retrieval or search purpose, and the count does not feel excessive or artificially padded.
The server covers ID search, course detail retrieval, and a detailed search fallback. A minor gap is the lack of a direct non-scrape detailed course search, but the existing combination of search_course_ids plus get_course and scrape_courses covers the core workflow.