{ "SchemaVersion": "1", "Kind": "DirectoryEntry", "SubjectType": "mcp-server", "Slug": "infinitecampus-mcp", "Name": "infinitecampus-mcp", "Title": "infinitecampus-mcp MCP Server | Pod", "Description": "Infinite Campus (Campus Parent) for Claude β€” grades, attendance, assignments, messages", "CanonicalUrl": "https://askpod.ai/mcp/infinitecampus-mcp", "MarkdownUrl": "https://askpod.ai/mcp/infinitecampus-mcp.md", "JsonUrl": "https://askpod.ai/mcp/infinitecampus-mcp.json", "DatePublished": "2026-08-31T23:50:54.202Z", "DateModified": "2026-08-31T23:50:54.202Z", "RegistryName": "io.github.chrischall/infinitecampus-mcp", "RepositoryUrl": "https://github.com/chrischall/infinitecampus-mcp", "VerificationStatus": "unverified", "Identities": [], "Sources": [ { "Source": "github_issues", "LastSeenAt": "2026-08-31T23:50:54.202Z" }, { "Source": "official_mcp_registry", "ExternalId": "io.github.chrischall/infinitecampus-mcp", "LastSeenAt": "2026-08-31T23:50:54.202Z" } ], "Categories": [], "FirstParty": false, "Deployments": [ { "Kind": "package", "PackageRegistry": "npm", "PackageIdentifier": "infinitecampus-mcp", "ConfigSnippet": "{\n \"mcpServers\": {\n \"infinitecampus-mcp\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"infinitecampus-mcp\"\n ]\n }\n }\n}" } ], "Tools": { "Claimed": [], "ClaimedCount": 0, "Observed": null, "ObservedCount": null, "Verified": false, "Mismatch": null }, "Measured": null, "Usage": { "Registry": "npm", "DownloadsLast30d": 1608 }, "Issues": [ { "Title": "Auto-review follow-ups for PR #152: feat: add ic_healthcheck, and surface district linkage", "Excerpt": "\n\nTracking auto-review follow-ups for #152 (verdict: **warn**).\n\n### 🟑 Nits\n- [x] CLAUDE.md, README.md, and skills/ic/SKILL.md still say \"19 tools\" after this PR adds the 20th tool (ic_healthcheck); SKILL.md's tool tables also lack a row for ic_healthcheck\n\n---\nChecklist regenerated from the auto-review of `aee82ae` ([run](https://github.com/chrischall/infinitecampus-mcp/actions/runs/33336991502)). Ticks survive later rounds, but a round that reviewed an older", "SourceUrl": "https://github.com/chrischall/infinitecampus-mcp/issues/153", "PublishedAt": "2026-08-30T21:44:18.000Z", "State": "closed", "Comments": 1, "Reporter": "Contributor", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Auto-review follow-ups for PR #144: feat: cache the primary district's session so a restart skips the login", "Excerpt": "\n\nTracking auto-review follow-ups for #144 (verdict: **warn**).\n\n### 🟑 Nits\n- [ ] src/client.ts:447 comments a non-latching `return true` as \"a real, permanent answer\" while line 460 calls the same non-latching outcome \"transient\" β€” make the permanent/transient wording match the actual `discoveryDone` behaviour\n- [ ] tests/client.test.ts:1899-1919 (\"retries discovery when the CUPS probe failed rather than latching\") has a dead first `mockImplementation` and de", "SourceUrl": "https://github.com/chrischall/infinitecampus-mcp/issues/145", "PublishedAt": "2026-08-27T23:31:03.000Z", "State": "closed", "Comments": 0, "Reporter": "Contributor", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Auto-review follow-ups for PR #134: chore: declare a mint.yaml hosting manifest", "Excerpt": "\n\nTracking auto-review follow-ups for #134 (verdict: **warn**).\n\n### 🟑 Nits\n- [ ] `.mcpbignore`'s new `mint.yaml` line is redundant β€” already excluded by the pre-existing `*.yaml`/`*.yml` glob\n- [ ] `mint.yaml` isn't added to CLAUDE.md's 'Plugin / Marketplace / Registry' inventory of distribution-only manifest files, unlike its siblings\n\n---\nChecklist regenerated from the auto-review of `23615e3` ([run](https://github.com/chrischall/infinitecampus-mcp/actions/", "SourceUrl": "https://github.com/chrischall/infinitecampus-mcp/issues/135", "PublishedAt": "2026-08-25T22:36:06.000Z", "State": "closed", "Comments": 0, "Reporter": "Contributor", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Auto-review follow-ups for PR #118: test(auth): hold the per-host lifter cache in place, and drop a stale docstring", "Excerpt": "\n\nTracking auto-review follow-ups for #118 (verdict: **warn**).\n\n### 🟑 Nits\n- [ ] Test isolation: lifterFactoryMock not reset in beforeEach, causing test-order dependency (tests/auth.test.ts:51)\n\n---\nWhen addressing the review on #118, resolve each item and add `Closes #` to the PR once everything is genuinely fixed; deferred items stay open here. See the auto-review follow-up convention in CLAUDE.md.", "SourceUrl": "https://github.com/chrischall/infinitecampus-mcp/issues/119", "PublishedAt": "2026-08-03T02:00:18.000Z", "State": "closed", "Comments": 0, "Reporter": "Contributor", "Rank": "top", "Extractor": "github_issue" }, { "Title": "Auto-review follow-ups for PR #116: refactor(auth): collapse the hand-rolled lifter onto createSessionLifter", "Excerpt": "\n\nTracking auto-review follow-ups for #116 (verdict: **warn**).\n\n### 🟑 Nits\n- [ ] Stale duplicate JSDoc comment left above lifterFor's cache in src/auth.ts:141-148, describing the wrong declaration\n- [ ] tests/auth.test.ts doesn't verify the single-flight lifter caching the PR calls load-bearing β€” the mock can't distinguish a cached lifter from a freshly-constructed one per call\n\n---\nWhen addressing the review on #116, resolve each item and add `Closes #\n\nTracking auto-review follow-ups for #113 (verdict: **warn**).\n\n### 🟑 Nits\n- [ ] src/client.ts:54 β€” the `fetchproxyMode` private field is assigned but never read after both discovery guards were removed; delete it, and fix its doc comment which still claims the client cannot re-login on cookie expiry and that discovery runs lazily on the first `ensureDiscovery()` call\n- [ ] src/client.ts:137 β€” `ensureDiscovery()` binds `const session = await …ensure()` only t", "SourceUrl": "https://github.com/chrischall/infinitecampus-mcp/issues/114", "PublishedAt": "2026-08-03T01:03:06.000Z", "State": "closed", "Comments": 0, "Reporter": "Contributor", "Rank": "top", "Extractor": "github_issue" } ], "Observations": [], "ObservationCount": 0, "Related": [], "Indexable": true, "ContentMarkdown": "# infinitecampus-mcp MCP Server\n\nInfinite Campus (Campus Parent) for Claude β€” grades, attendance, assignments, messages\n\n**Publisher claimed.** No tool list reported, and Pod has not connected to this server.\n\n## Status\n\nPod has not dialled infinitecampus-mcp yet, so everything on this page is what its publisher reported rather than what we observed. Registries describe servers; they do not connect to them. Until a check runs, treat the tool list below as a claim.\n\n## Connect\n\nPublished as `infinitecampus-mcp` on npm. Runs locally.\n\n## Known issues\n\n**6 problems reported by people outside the maintainer team.** Issues filed by the project's own owners, members and collaborators are excluded β€” those are release checklists and internal refactors, not things that will go wrong for you. Showing 5.\n\n### Most discussed\n\n### Auto-review follow-ups for PR #152: feat: add ic_healthcheck, and surface district linkage\n\n\n\nTracking auto-review follow-ups for #152 (verdict: **warn**).\n\n### 🟑 Nits\n- [x] CLAUDE.md, README.md, and skills/ic/SKILL.md still say \"19 tools\" after this PR adds the 20th tool (ic_healthcheck); SKILL.md's tool tables also lack a row for ic_healthcheck\n\n---\nChecklist regenerated from the auto-review of `aee82ae` ([run](https://github.com/chrischall/infinitecampus-mcp/actions/runs/33336991502)). Ticks survive later rounds, but a round that reviewed an older\n\n[Read the thread](https://github.com/chrischall/infinitecampus-mcp/issues/153) Β· 2026-08-30 Β· closed Β· outside contributor Β· 1 comment\n\n### Auto-review follow-ups for PR #144: feat: cache the primary district's session so a restart skips the login\n\n\n\nTracking auto-review follow-ups for #144 (verdict: **warn**).\n\n### 🟑 Nits\n- [ ] src/client.ts:447 comments a non-latching `return true` as \"a real, permanent answer\" while line 460 calls the same non-latching outcome \"transient\" β€” make the permanent/transient wording match the actual `discoveryDone` behaviour\n- [ ] tests/client.test.ts:1899-1919 (\"retries discovery when the CUPS probe failed rather than latching\") has a dead first `mockImplementation` and de\n\n[Read the thread](https://github.com/chrischall/infinitecampus-mcp/issues/145) Β· 2026-08-27 Β· closed Β· outside contributor Β· 0 comments\n\n### Auto-review follow-ups for PR #134: chore: declare a mint.yaml hosting manifest\n\n\n\nTracking auto-review follow-ups for #134 (verdict: **warn**).\n\n### 🟑 Nits\n- [ ] `.mcpbignore`'s new `mint.yaml` line is redundant β€” already excluded by the pre-existing `*.yaml`/`*.yml` glob\n- [ ] `mint.yaml` isn't added to CLAUDE.md's 'Plugin / Marketplace / Registry' inventory of distribution-only manifest files, unlike its siblings\n\n---\nChecklist regenerated from the auto-review of `23615e3` ([run](https://github.com/chrischall/infinitecampus-mcp/actions/\n\n[Read the thread](https://github.com/chrischall/infinitecampus-mcp/issues/135) Β· 2026-08-25 Β· closed Β· outside contributor Β· 0 comments\n\n### Auto-review follow-ups for PR #118: test(auth): hold the per-host lifter cache in place, and drop a stale docstring\n\n\n\nTracking auto-review follow-ups for #118 (verdict: **warn**).\n\n### 🟑 Nits\n- [ ] Test isolation: lifterFactoryMock not reset in beforeEach, causing test-order dependency (tests/auth.test.ts:51)\n\n---\nWhen addressing the review on #118, resolve each item and add `Closes #` to the PR once everything is genuinely fixed; deferred items stay open here. See the auto-review follow-up convention in CLAUDE.md.\n\n[Read the thread](https://github.com/chrischall/infinitecampus-mcp/issues/119) Β· 2026-08-03 Β· closed Β· outside contributor Β· 0 comments\n\n### Auto-review follow-ups for PR #116: refactor(auth): collapse the hand-rolled lifter onto createSessionLifter\n\n\n\nTracking auto-review follow-ups for #116 (verdict: **warn**).\n\n### 🟑 Nits\n- [ ] Stale duplicate JSDoc comment left above lifterFor's cache in src/auth.ts:141-148, describing the wrong declaration\n- [ ] tests/auth.test.ts doesn't verify the single-flight lifter caching the PR calls load-bearing β€” the mock can't distinguish a cached lifter from a freshly-constructed one per call\n\n---\nWhen addressing the review on #116, resolve each item and add `Closes #