io.github.AnonymousOnyx22/syllabus-calendar-mcp
NPM · SYLLABUS-CALENDAR-MCP
Syllabus to calendar MCP: pull dates from a syllabus into .ics files, merge calendars. Offline.
Available components
Last scanned (7 hours ago)
Scores higher than 36% of npm servers
Category Productivity and Notes
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1041 tokens (~260/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "merge_calendars" implies "merge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 1 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.07 ▲ functional
- Package version: 0.1.1 → 0.1.2 functional
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 51
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/syllabus-calendar-mcp@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
build_ics Build an ics calendar ~250
Build a valid .ics calendar file from dated events and recurring classes, with reminders. Inputs: events (each with title, date, optional start_time, end_time, type, course, location and notes), classes (each with course, weekdays, start_date, end_date, start_time and optional end_time, location, holidays and reading_weeks), reminders_minutes (whole minutes before each event, default 60), calendar_name and optional output_path. Each class becomes one weekly recurring event with holidays and reading weeks removed. The tool checks the file before returning it. Example prompt: "Make an .ics file for my course with a reminder one day before each assignment."
| Name | Type | Req | Description |
|---|---|---|---|
| calendar_name | string | – | Name shown in the calendar app. Defaults to "Course calendar". |
| classes | array | – | Recurring classes to add as weekly events. |
| events | array | – | Dated events such as assignments and exams. |
| output_path | string | – | Optional file path. When it is passed, the calendar is written there as a .ics file. |
| reminders_minutes | array | – | Reminder times in whole minutes before an event. Defaults to [60]. Pass an empty array for no reminders. |
| Name | Type | Req | Description |
|---|---|---|---|
| class_count | number | yes | How many recurring classes the calendar holds. |
| class_meetings | number | yes | How many class meetings the recurring events produce after skips. |
| errors | array | yes | Problems found by the checks. Empty when the calendar is valid. |
| event_count | number | yes | How many single events the calendar holds. |
| ics | string | yes | The calendar file as text, with CRLF line breaks. |
| output_path | string|null | yes | The file path the calendar was written to, or null when no path was passed. |
| valid | boolean | yes | True when the calendar passed the built in checks. |
No examples provided.
expand_recurring_classes Expand recurring classes ~383
Generate the meeting dates for a recurring class between two dates, and skip holidays and reading weeks. Inputs: course, weekdays (day names or codes such as Tuesday or TU), start_date, end_date, start_time, optional end_time, optional location, holidays (single dates or ranges) and reading_weeks (single dates or ranges). Returns every meeting date plus the dates that were skipped and why. The answer ends with a next step hint that points to build_ics when the class should become a calendar. Example prompt: "My biology class meets Tuesday and Thursday from Sep 8 to Dec 10, 2026 at 10:00. Skip the reading week of Oct 12 to Oct 16."
| Name | Type | Req | Description |
|---|---|---|---|
| course | string | yes | Course name or code, such as BIO 101. |
| end_date | string | yes | Last date of the term as YYYY-MM-DD. |
| end_time | string | – | Class end time as HH:MM or 2:30 PM. It must be after start_time. |
| holidays | array | – | Holiday dates or ranges, such as "2026-10-12" or "2026-10-12 to 2026-10-16". |
| location | string | – | Room or place. |
| reading_weeks | array | – | Reading week dates or ranges, such as "2026-10-12 to 2026-10-16". |
| start_date | string | yes | First date of the term as YYYY-MM-DD. |
| start_time | string | yes | Class start time as HH:MM or 2:30 PM. |
| title | string | – | Title for the calendar event. Defaults to the course name plus class. |
| weekdays | array | yes | Days the class meets, as names or codes, such as "Tuesday", "Tue" or "TU". |
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_count | number | yes | How many dates matched the weekdays before holidays and reading weeks were removed. |
| course | string | yes | Course name or code. |
| end_date | string | yes | Last date of the term. |
| end_time | string|null | yes | Class end time, or null when none was passed. |
| location | string|null | yes | Room or place, or null when none was passed. |
| meetings | array | yes | Every class meeting, in date order. |
| next_step | string | yes | Suggested next tool call for turning the class meetings into a calendar. |
| skipped | array | yes | Dates that were skipped, with the reason. |
| start_date | string | yes | First date of the term. |
| start_time | string | yes | Class start time. |
| title | string | yes | Title used for the calendar event. |
| weekdays | array | yes | The weekdays as two letter codes. |
No examples provided.
extract_schedule_events Extract schedule events ~257
Extract dated events from pasted syllabus text. Each line that names a date becomes one event, with a title, a type, a date and optional times. Inputs: text (the pasted syllabus or course schedule, one event per line), course (a course name or code to put on every event) and year (the year to use when a date has no year). Titles are read from the words around the date, and each event is marked as an assignment, exam, quiz, lab, reading, class or other. Any line that has no date is returned in undated_lines instead of being dropped silently. The answer ends with a next step hint that points to build_ics when the events should become a calendar. Example prompt: "Turn this syllabus into calendar events: Assignment 1 due Sep 15, Midterm exam October 20 at 10:00."
| Name | Type | Req | Description |
|---|---|---|---|
| course | string | – | Course name or code to put on every event, such as BIO 101. |
| text | string | yes | The pasted syllabus or course schedule. Put one event on each line, with a date on the line. |
| year | integer | – | The year to use when a date has no year. Defaults to the current year. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | How many events were found. |
| events | array | yes | Every dated event that was found, in date order. |
| next_step | string | yes | Suggested next tool call for turning the events into a calendar. |
| undated_lines | array | yes | Lines that had no date, kept in the order they appeared so they can be fixed. |
| year | number | yes | The year used for dates that did not name one. |
No examples provided.
merge_calendars Merge course calendars ~151
Merge several course calendars into one and list timed events that overlap. Inputs: calendars (each with an optional name and an ics string), optional calendar_name and optional output_path. Events with the same UID are kept once. Weekly and daily recurring events are expanded when conflicts are checked. Example prompt: "Merge my three course calendars and tell me which classes conflict."
| Name | Type | Req | Description |
|---|---|---|---|
| calendar_name | string | – | Name for the merged calendar. Defaults to "Merged course calendar". |
| calendars | array | yes | The calendars to merge, each with the calendar text and an optional name. |
| output_path | string | – | Optional file path. When it is passed, the calendar is written there as a .ics file. |
| Name | Type | Req | Description |
|---|---|---|---|
| calendar_count | number | yes | How many calendars were passed in. |
| conflicts | array | yes | Every pair of timed events that overlaps, in date order. |
| errors | array | yes | Problems found by the checks. Empty when the calendar is valid. |
| event_count | number | yes | How many events the merged calendar holds, after repeated UIDs are dropped. |
| ics | string | yes | The merged calendar as text, with CRLF line breaks. |
| output_path | string|null | yes | The file path the calendar was written to, or null when no path was passed. |
| valid | boolean | yes | True when the merged calendar passed the built in checks. |
No examples provided.
How do I install the io.github.AnonymousOnyx22/syllabus-calendar-mcp server?
io.github.AnonymousOnyx22/syllabus-calendar-mcp runs locally as an npm package, launched with npx -y syllabus-calendar-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · syllabus-calendar-mcp
claude mcp add anonymousonyx22-syllabus-calendar-mcp -- npx -y syllabus-calendar-mcp
What is the io.github.AnonymousOnyx22/syllabus-calendar-mcp server?
io.github.AnonymousOnyx22/syllabus-calendar-mcp is listed in the public MCP registry as io.github.AnonymousOnyx22/syllabus-calendar-mcp. Syllabus to calendar MCP: pull dates from a syllabus into .ics files, merge calendars. Offline. This page covers its npm package (syllabus-calendar-mcp).
Is the io.github.AnonymousOnyx22/syllabus-calendar-mcp server safe to use?
io.github.AnonymousOnyx22/syllabus-calendar-mcp scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.AnonymousOnyx22/syllabus-calendar-mcp server expose?
io.github.AnonymousOnyx22/syllabus-calendar-mcp exposes 4 tools: extract_schedule_events, expand_recurring_classes, build_ics, merge_calendars. Their descriptions and schemas cost roughly 1,041 tokens of context every time the server is loaded.
Is the io.github.AnonymousOnyx22/syllabus-calendar-mcp server still maintained?
io.github.AnonymousOnyx22/syllabus-calendar-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.AnonymousOnyx22/syllabus-calendar-mcp server under?
io.github.AnonymousOnyx22/syllabus-calendar-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.