io.github.shubhtoy/github-project-info

NPM · GITHUB-PROJECT-INFO-MCP · SCANNED AUG 3

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

Available components

+22 this week 67 67 Trust /100

Trust breakdown (6 categories)

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 →

Supply Chain Security83

No malware found by supply-chain analysis.Pass
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. View diagnostics → Fail
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. 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 28 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability72

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 Management23

Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

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

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · github-project-info-mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# add to Codex CLI

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
    }
  }
}

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.json

{
  "mcpServers": {
    "shubhtoy-github-project-info": {
      "command": "npx",
      "args": [
        "-y",
        "github-project-info-mcp"
      ]
    }
  }
}

Changelog

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.

3 Aug 26 +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.
2 Aug 26 +61
- GHSA-frvp-7c67-39w9 affects this package: medium ▼ security
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Licence: MIT functional
31 Jul 26 −19
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −21
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
27 Jul 26 45

First indexed and scored.

Show 3 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Vulnerabilities 1 finding

ID	CVE	Severity	Vector	Fix available
GHSA-frvp-7c67-39w9		medium	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N	yes

Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 5 exposed · ~740 tokens

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.

Tool Tokens

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

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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.

Input Output Examples

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

Input Output Examples

Name	Type	Req	Description
username	string	yes	GitHub username

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug