Local-first MCP server for Canvas LMS. Stdio transport, no third-party broker.
Local-first MCP server for Canvas LMS. Stdio transport, no network round-trips beyond the official Canvas API. Status: alpha. Single-user, no warranty, API surface may still shift. File issues if it breaks. Canvas is built for instructors. As a student you get a fragmented UI, no cross-course search, and notifications that arrive late or never. This server exposes the Canvas REST API as MCP tools…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
Local-first MCP server for Canvas LMS. Stdio transport, no network round-trips beyond the official Canvas API. Status: alpha. Single-user, no warranty, API surface may still shift. File issues if it breaks. Canvas is built for instructors. As a student you get a fragmented UI, no cross-course search, and notifications that arrive late or never. This server exposes the Canvas REST API as MCP tools so you can drive the LMS from any MCP-compatible client (Claude Code, Claude Desktop, etc.). Server…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.