# io.github.shubhtoy/github-project-info (npm · github-project-info-mcp)

Read public GitHub Projects v2 boards without auth — items, fields, story points, priority.

- Trust score: 67/100 (medium)
- Change this week: +22
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `github-project-info-mcp`: 67/100 (this document), [markdown](https://verifymcp.io/servers/shubhtoy-github-project-info/github-project-info-mcp.md), [page](https://verifymcp.io/servers/shubhtoy-github-project-info/github-project-info-mcp)

## Channel facts

- Registry: `npm`
- Package: `github-project-info-mcp`
- Version: `0.1.3`
- 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-08-03.

- **Supply Chain Security**: 83/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known medium-severity CVE affects @hono/node-server 1.19.17, reached via @modelcontextprotocol/sdk > @hono/node-server. A fixed version is available.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **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 28 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add shubhtoy-github-project-info -- npx -y github-project-info-mcp
```

### Codex

```bash
codex mcp add shubhtoy-github-project-info -- npx -y github-project-info-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shubhtoy-github-project-info": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "github-project-info-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add shubhtoy-github-project-info --command npx --arg -y --arg github-project-info-mcp
```

### Hermes

```yaml
mcp_servers:
  shubhtoy-github-project-info:
    command: "npx"
    args: ["-y", "github-project-info-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "shubhtoy-github-project-info": {
      "command": "npx",
      "args": [
        "-y",
        "github-project-info-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-08-03 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 66, +61)

- [security regression] GHSA-frvp-7c67-39w9 affects this package: medium
- [security regression] Provenance: unverified → fail
- [security regression] Known CVEs: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Stability: unverified → 0.20
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] Tool coverage: unverified → 100
- [functional] Licence: MIT

### 2026-07-31 (score 5, −19)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 24, −21)

- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 45)

First indexed and scored.

## MCP tools (5)

### `get_project_metadata` (~109 tokens)

Get metadata (title, description, state, dates) for a public GitHub Projects (v2) board. Works unauthenticated for both user-owned and org-owned public projects.

Input parameters:

- `owner` (string, required): GitHub username or organization name that owns the project
- `ownerType` (string, required): Whether the project is owned by a personal GitHub user account or an organization
- `projectNumber` (integer, required): The project number, e.g. 4 for .../projects/4

### `list_project_items` (~166 tokens)

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.

Input parameters:

- `owner` (string, required): GitHub username or organization name that owns the project
- `ownerType` (string, required): Whether the project is owned by a personal GitHub user account or an organization
- `projectNumber` (integer, required): The project number, e.g. 4 for .../projects/4

### `get_project_item` (~259 tokens)

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.

Input parameters:

- `itemId` (integer, required): The numeric item ID, from list_project_items
- `owner` (string): GitHub username that owns the project, for resolving custom field/option names
- `projectId` (integer, required): The project's numeric database ID, from get_project_metadata's `id` field
- `projectNumber` (integer): The project number, for resolving custom field/option names

### `get_project_fields` (~123 tokens)

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

Input parameters:

- `owner` (string, required): GitHub username that owns the project
- `projectNumber` (integer, required): The project number, e.g. 4 for .../projects/4

### `list_user_projects` (~83 tokens)

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

Input parameters:

- `username` (string, required): GitHub username

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/shubhtoy-github-project-info/github-project-info-mcp#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 66
- 2026-08-01: 5
- 2026-07-31: 5
- 2026-07-30: 24
- 2026-07-28: 45
- 2026-07-27: 45

## Links

- npm package: https://www.npmjs.com/package/github-project-info-mcp
- Socket report: https://socket.dev/npm/package/github-project-info-mcp
- Repository: https://github.com/shubhtoy/github-project-info-mcp
- Changelog RSS feed: https://verifymcp.io/servers/shubhtoy-github-project-info/github-project-info-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/shubhtoy-github-project-info/github-project-info-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/shubhtoy-github-project-info/github-project-info-mcp