Unified Github MCP Server

unified-github-mcp-server npm v4.0.1

Published by yourusername — 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.

Unified GitHub MCP Server - Comprehensive GitHub API integration with multi-account support, natural language workflows, and 35+ GitHub tools

Trust grade
C
74/100
Last scanned get badge →
Trust
C · 74/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
Moderate
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
C Why this grade threat 78 − adoption risk = 74/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 − 22 = 78. What the published surface and source actually contain:

PointsWhat was foundCategory
−22 Hardcoded GitHub token in server code MTC-SRC-008 exfiltration

2. Client adoption risk — 78 − 4 = 74. 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
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Grade capped: 1 confirmed high finding → grade capped at C. A hard gate overrides the point total — no amount of clean surface buys back a confirmed catastrophe.

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 4

high Hardcoded GitHub token in server code (dist/index.js)MTC-SRC-008

A hardcoded GitHub token (a live-looking credential hardcoded in shipped code) appears in `dist/index.js:46`. Secrets in source ship to everyone who installs the package and are a direct credential leak.

Evidence: GitHub token: ghp_…(redacted)

Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.

Location: server dist/index.js

medium Tool "delete_file" can modify the filesystemMTC-CAP-002

Tool "delete_file" can write, overwrite or delete files (keyword "delete_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool delete_file

low Mutating tool "delete_file" declares no destructiveHintMTC-CAP-005

Tool "delete_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool delete_file

low Unconstrained path parameter "path" on "delete_file"MTC-CAP-008

Tool "delete_file" takes a path parameter "path" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool delete_file · inputSchema.properties.path

Tools 24

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

  • create_issuenetwork egress
  • create_pull_requestnetwork egress
  • delete_filewrites files
  • upload_filenetwork egress
  • create_branchno sensitive capability
  • create_gistno sensitive capability
  • create_repositoryno sensitive capability
  • delete_branchno sensitive capability
  • delete_repositoryno sensitive capability
  • get_file_contentno sensitive capability
Show 14 more tools ↓
  • get_organizationno sensitive capability
  • get_repositoryno sensitive capability
  • get_user_infono sensitive capability
  • list_accountsno sensitive capability
  • list_branchesno sensitive capability
  • list_gistsno sensitive capability
  • list_issuesno sensitive capability
  • list_org_membersno sensitive capability
  • list_organizationsno sensitive capability
  • list_pull_requestsno sensitive capability
  • list_repositoriesno sensitive capability
  • merge_branchno sensitive capability
  • switch_accountno sensitive capability
  • update_fileno 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
v4.0.1 latest C 74/100 4 1.13.0 2026-09-07

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: C · 74/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/unified-github-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/unified-github-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/unified-github-mcp-server"><img src="https://mcptrustchecker.com/registry/unified-github-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/unified-github-mcp-server/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 unified-github-mcp-server --online

Use the free API → How scoring works

More in Developer Tools