io.github.shubhtoy/github-project-info
NPM · GITHUB-PROJECT-INFO-MCP
Read public GitHub Projects v2 boards without auth — items, fields, story points, priority.
Available components
Last scanned (19 hours ago)
Scores higher than 61% of npm servers
Category Project Management
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.29.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 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 121 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 740 tokens (~148/item across 5 items; 5 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 29 Oct 26 0
- CVE-2026-118663 affects this package: high ▼ security
- 28 Oct 26 0
- GHSA-f897-62hf-6gxq affects this package: high ▼ security
- 26 Oct 26 0
- Stability: 0.97 → pass security
- 25 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 0
- CVE-2023-54404 affects this package: high ▼ security
- 21 Oct 26 0
- CVE-2026-111771 affects this package: high ▼ security
- CVE-2026-111768 affects this package: high ▼ security
- CVE-2026-111769 affects this package: high ▼ security
- CVE-2026-111767 affects this package: high ▼ security
- 19 Oct 26 0
- Stability: 0.97 → pass security
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Analysed npm/github-project-info-mcp@0.1.3
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 →
Vulnerabilities 8 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-rmxm-3fg6-px4f | CVE-2026-118663 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | yes |
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-f897-62hf-6gxq | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes | |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
get_project_fields ~123
Get a public GitHub Projects (v2) board's field definitions — including single-select field option names/colors (e.g. Status: Todo/In Progress/Done) and saved views. Useful for resolving the option IDs found in list_project_items results to human-readable names. Currently only supported for user-owned projects (uses the same board-page data source as list_project_items for those).
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | GitHub username that owns the project |
| projectNumber | integer | yes | The project number, e.g. 4 for .../projects/4 |
No output schema declared.
No examples provided.
get_project_item ~259
Get full field data for a single item in a public GitHub Projects (v2) board — including custom fields (like Priority, Story Points) that list_project_items may not show, since that only returns the board's default-view columns while this returns every field defined on the project. Requires the project's numeric database ID (from get_project_metadata's `id` field — NOT `nodeId`, which does not work with this endpoint) and the item's numeric ID (from list_project_items). Pass owner and projectNumber too so custom field names and single-select option names (e.g. a Status ID resolved to "Done") can be resolved — omit them to get raw field IDs/option IDs instead, skipping an extra request. Uses an unofficial, undocumented GitHub endpoint — works today for public projects but is not a published API contract.
| Name | Type | Req | Description |
|---|---|---|---|
| itemId | integer | yes | The numeric item ID, from list_project_items |
| owner | string | – | GitHub username that owns the project, for resolving custom field/option names |
| projectId | integer | yes | The project's numeric database ID, from get_project_metadata's `id` field |
| projectNumber | integer | – | The project number, for resolving custom field/option names |
No output schema declared.
No examples provided.
get_project_metadata ~109
Get metadata (title, description, state, dates) for a public GitHub Projects (v2) board. Works unauthenticated for both user-owned and org-owned public projects.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | GitHub username or organization name that owns the project |
| ownerType | string | yes | Whether the project is owned by a personal GitHub user account or an organization |
| projectNumber | integer | yes | The project number, e.g. 4 for .../projects/4 |
No output schema declared.
No examples provided.
list_project_items ~166
List all items (issues/PRs/draft issues) in a public GitHub Projects (v2) board, including their status, custom field values, and other metadata. For org-owned projects this uses GitHub's official REST API. For user-owned projects, GitHub's official API requires authentication even for public projects, so this falls back to reading the public board page's embedded data — an unofficial method that could break if GitHub changes its page structure.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | GitHub username or organization name that owns the project |
| ownerType | string | yes | Whether the project is owned by a personal GitHub user account or an organization |
| projectNumber | integer | yes | The project number, e.g. 4 for .../projects/4 |
No output schema declared.
No examples provided.
list_user_projects ~83
List all public GitHub Projects (v2) boards owned by a user account. There is no official GitHub API for this (Projects aren't a Search API resource type, and the REST API requires already knowing a project number) — this reads the same project list shown on a user's profile page (the Projects tab).
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | yes | GitHub username |
No output schema declared.
No examples provided.
How do I install the io.github.shubhtoy/github-project-info MCP server?
io.github.shubhtoy/github-project-info runs locally as an npm package, launched with npx -y github-project-info-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 · github-project-info-mcp
claude mcp add shubhtoy-github-project-info -- npx -y github-project-info-mcp
What is the io.github.shubhtoy/github-project-info MCP server?
io.github.shubhtoy/github-project-info is an MCP server listed in the public MCP registry as io.github.shubhtoy/github-project-info. Read public GitHub Projects v2 boards without auth, items, fields, story points, priority. This page covers its npm package (github-project-info-mcp).
Is the io.github.shubhtoy/github-project-info MCP server safe to use?
io.github.shubhtoy/github-project-info scores 79 out of 100 on VerifyMCP. We recorded 8 known advisories against it as of 4 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.shubhtoy/github-project-info MCP server expose?
io.github.shubhtoy/github-project-info exposes 5 tools: get_project_metadata, list_project_items, get_project_item, get_project_fields, list_user_projects. Their descriptions and schemas cost roughly 740 tokens of context every time the server is loaded.
Is the io.github.shubhtoy/github-project-info MCP server still maintained?
io.github.shubhtoy/github-project-info is still listed as active in the MCP registry. We last reached this channel on 4 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.shubhtoy/github-project-info MCP server under?
io.github.shubhtoy/github-project-info declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.