Github Pro MCP Server

github-pro-mcp npm v0.0.2

Published by anantanandgupta — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 34

Each tool and what it can reach — statically extracted from the published source.

  • auth_get_current_loginno sensitive capability
  • code_searchno sensitive capability
  • file_create_updateno sensitive capability
  • file_deleteno sensitive capability
  • file_get_contentno sensitive capability
  • issue_add_commentno sensitive capability
  • issue_add_labelno sensitive capability
  • issue_closeno sensitive capability
  • issue_createno sensitive capability
  • issue_get_field_valueno sensitive capability
Show 24 more tools ↓
  • issue_listno sensitive capability
  • issue_readno sensitive capability
  • issue_remove_labelno sensitive capability
  • issue_reopenno sensitive capability
  • issue_searchno sensitive capability
  • issue_set_field_valueno sensitive capability
  • issue_updateno sensitive capability
  • label_listno sensitive capability
  • label_writeno sensitive capability
  • organization_searchno sensitive capability
  • owner_list_issue_fieldno sensitive capability
  • owner_list_issue_typeno sensitive capability
  • owner_list_organizationno sensitive capability
  • owner_list_projectno sensitive capability
  • owner_list_repositoryno sensitive capability
  • profile_getno sensitive capability
  • projects_getno sensitive capability
  • projects_writeno sensitive capability
  • pull_request_createno sensitive capability
  • pull_request_mergeno sensitive capability
  • pull_request_readno sensitive capability
  • repository_searchno sensitive capability
  • server_infono sensitive capability
  • sub_issue_writeno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.0.2 latest A 99/100 0 1.9.0 2026-07-24

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/github-pro-mcp/badge.svg)](https://mcptrustchecker.com/registry/github-pro-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/github-pro-mcp"><img src="https://mcptrustchecker.com/registry/github-pro-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/github-pro-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan github-pro-mcp --online

Use the free API → How scoring works

More in Developer Tools