Track and report student attendance via a SIS or LMS attendance API
domain: education-general · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Retrieve the list of scheduled class sessions for the term from the SIS or LMS, capturing session_id, course_id, section_id, and scheduled_date for each
For each session, retrieve the roster of enrolled students to establish the expected attendee list
Submit attendance records by POSTing to the platform's attendance endpoint with student_id, session_id, date, and attendance_code (e.g., 'present', 'absent', 'tardy', 'excused') for each student
Pull aggregate attendance reports with a GET to the attendance summary endpoint, filtering by student_id or section_id and a date range, to compute attendance rate per student
Flag students whose attendance rate falls below a configurable threshold and surface that data to instructors or advisors through a reporting dashboard query
Known gotchas
Attendance codes are institution-specific and not standardized across platforms; always retrieve the valid code set from the platform's descriptor or picklist API before submitting records to avoid rejection
Retroactive attendance corrections (changing 'absent' to 'excused') may require elevated permissions or a separate amendment workflow depending on the platform; a plain PUT to the attendance record may be blocked after a grace period
Attendance data is part of the education record under FERPA; aggregate absence counts disclosed to parents of students 18 or older require student consent unless the institution has a specific FERPA exception policy in place
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?