# 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.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `syllabus-calendar-mcp`: 69/100 (this document), [markdown](https://verifymcp.io/servers/anonymousonyx22-syllabus-calendar-mcp/syllabus-calendar-mcp.md), [page](https://verifymcp.io/servers/anonymousonyx22-syllabus-calendar-mcp/syllabus-calendar-mcp)

## Channel facts

- Registry: `npm`
- Package: `syllabus-calendar-mcp`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add anonymousonyx22-syllabus-calendar-mcp -- npx -y syllabus-calendar-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "anonymousonyx22-syllabus-calendar-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "syllabus-calendar-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "anonymousonyx22-syllabus-calendar-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "syllabus-calendar-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add anonymousonyx22-syllabus-calendar-mcp -- npx -y syllabus-calendar-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "anonymousonyx22-syllabus-calendar-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "syllabus-calendar-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add anonymousonyx22-syllabus-calendar-mcp --command npx --arg -y --arg syllabus-calendar-mcp
```

### Hermes

```yaml
mcp_servers:
  anonymousonyx22-syllabus-calendar-mcp:
    command: "npx"
    args: ["-y", "syllabus-calendar-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "anonymousonyx22-syllabus-calendar-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "syllabus-calendar-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add anonymousonyx22-syllabus-calendar-mcp -t stdio -c npx -a -y syllabus-calendar-mcp
```

### Other

```json
{
  "mcpServers": {
    "anonymousonyx22-syllabus-calendar-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "syllabus-calendar-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 69, +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.

### 2026-11-02 (score 68, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-01 (score 52, −14)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.07
- [functional] Package version: 0.1.1 → 0.1.2

### 2026-10-31 (score 66, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-30 (score 51)

First indexed and scored.

## MCP tools (4)

### `extract_schedule_events` (~257 tokens)

Extract schedule events

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."

Input parameters:

- `course` (string): Course name or code to put on every event, such as BIO 101.
- `text` (string, required): 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.

Output parameters:

- `count` (number): How many events were found.
- `events` (array): Every dated event that was found, in date order.
- `next_step` (string): Suggested next tool call for turning the events into a calendar.
- `undated_lines` (array): Lines that had no date, kept in the order they appeared so they can be fixed.
- `year` (number): The year used for dates that did not name one.

### `expand_recurring_classes` (~383 tokens)

Expand recurring classes

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."

Input parameters:

- `course` (string, required): Course name or code, such as BIO 101.
- `end_date` (string, required): 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, required): First date of the term as YYYY-MM-DD.
- `start_time` (string, required): 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, required): Days the class meets, as names or codes, such as "Tuesday", "Tue" or "TU".

Output parameters:

- `candidate_count` (number): How many dates matched the weekdays before holidays and reading weeks were removed.
- `course` (string): Course name or code.
- `end_date` (string): Last date of the term.
- `end_time` (string|null): Class end time, or null when none was passed.
- `location` (string|null): Room or place, or null when none was passed.
- `meetings` (array): Every class meeting, in date order.
- `next_step` (string): Suggested next tool call for turning the class meetings into a calendar.
- `skipped` (array): Dates that were skipped, with the reason.
- `start_date` (string): First date of the term.
- `start_time` (string): Class start time.
- `title` (string): Title used for the calendar event.
- `weekdays` (array): The weekdays as two letter codes.

### `build_ics` (~250 tokens)

Build an ics calendar

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."

Input parameters:

- `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.

Output parameters:

- `class_count` (number): How many recurring classes the calendar holds.
- `class_meetings` (number): How many class meetings the recurring events produce after skips.
- `errors` (array): Problems found by the checks. Empty when the calendar is valid.
- `event_count` (number): How many single events the calendar holds.
- `ics` (string): The calendar file as text, with CRLF line breaks.
- `output_path` (string|null): The file path the calendar was written to, or null when no path was passed.
- `valid` (boolean): True when the calendar passed the built in checks.

### `merge_calendars` (~151 tokens)

Merge course calendars

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."

Input parameters:

- `calendar_name` (string): Name for the merged calendar. Defaults to "Merged course calendar".
- `calendars` (array, required): 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.

Output parameters:

- `calendar_count` (number): How many calendars were passed in.
- `conflicts` (array): Every pair of timed events that overlaps, in date order.
- `errors` (array): Problems found by the checks. Empty when the calendar is valid.
- `event_count` (number): How many events the merged calendar holds, after repeated UIDs are dropped.
- `ics` (string): The merged calendar as text, with CRLF line breaks.
- `output_path` (string|null): The file path the calendar was written to, or null when no path was passed.
- `valid` (boolean): True when the merged calendar passed the built in checks.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/anonymousonyx22-syllabus-calendar-mcp/syllabus-calendar-mcp#diagnostics

## Score history

- 2026-11-05: 69
- 2026-11-04: 69
- 2026-11-03: 68
- 2026-11-02: 68
- 2026-11-01: 52
- 2026-10-31: 66
- 2026-10-30: 51

## Common questions

### 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.

### What did VerifyMCP test on the io.github.AnonymousOnyx22/syllabus-calendar-mcp server?

VerifyMCP ran 16 checks on io.github.AnonymousOnyx22/syllabus-calendar-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/syllabus-calendar-mcp
- Socket report: https://socket.dev/npm/package/syllabus-calendar-mcp
- Repository: https://github.com/AnonymousOnyx22/syllabus-calendar-mcp
- Website: https://brightspacemcp.com/more-mcps/
- Changelog RSS feed: https://verifymcp.io/servers/anonymousonyx22-syllabus-calendar-mcp/syllabus-calendar-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/anonymousonyx22-syllabus-calendar-mcp/syllabus-calendar-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/anonymousonyx22-syllabus-calendar-mcp/syllabus-calendar-mcp.json
- HTML version of this page: https://verifymcp.io/servers/anonymousonyx22-syllabus-calendar-mcp/syllabus-calendar-mcp