Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.mcparmory/github

PYPI · MCPARMORY-GITHUB · 2 COMPONENTS

Manage repositories, users, releases, and automate GitHub workflows

+12 this week 54 Trust /100

Last scanned (9 hours ago)

Scores higher than 56% of PyPI servers

Category Version Control

Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 2 of 46 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability0
  • Schema quality not yet verified: the captured schema was too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge it on a partial copy.Unverified
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage0
  • Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge them on a partial copy.Unverified
Tool Safety0
  • Tool safety not yet verified: the captured tool definitions were too large for us to store in full (the trim removes the very descriptions this category reads), or the server stopped listing its tools part-way.Unverified
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 3 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

What we tested

Checks we ran (11)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Stability
  • MCP protocol

Checks we could not complete (3)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: the captured schema was too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge it on a partial copy.
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge them on a partial copy.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: the captured tool definitions were too large for us to store in full (the trim removes the very descriptions this category reads), or the server stopped listing its tools part-way.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 5 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 4 Nov 26 −3
    • Stability: pass → 0.77 functional
  • 2 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 29 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.97 → pass security
  • 28 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.

  • 27 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 26 Oct 26 −14
    • Malware scan: pass → unverified ▼ security
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 5 Nov 2026 · Analysed pypi/mcparmory-github@1.0.6

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Dependencies 46 packages
Packages resolved 46
Stale 1
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 929 exposed · ~104,544 tokens partial

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 →

Tool Tokens
list_apps_with_protected_branch_access ~122

No description provided.

NameTypeReqDescription
branchstringyes–
ownerstringyes–
repostringyes–

No output schema declared.

No examples provided.

list_artifact_deployment_records ~98

No description provided.

NameTypeReqDescription
orgstringyes–
subject_digeststringyes–

No output schema declared.

No examples provided.

list_artifact_storage_records ~89

No description provided.

NameTypeReqDescription
orgstringyes–
subject_digeststringyes–

No output schema declared.

No examples provided.

list_artifacts ~86

No description provided.

NameTypeReqDescription
ownerstringyes–
repostringyes–

No output schema declared.

No examples provided.

list_assignees ~85

No description provided.

NameTypeReqDescription
ownerstringyes–
repostringyes–

No output schema declared.

No examples provided.

list_assignment_grades ~54

No description provided.

NameTypeReqDescription
assignment_idintegeryes–

No output schema declared.

No examples provided.

list_assignments ~49

No description provided.

NameTypeReqDescription
classroom_idintegeryes–

No output schema declared.

No examples provided.

list_attestation_repositories ~92

No description provided.

NameTypeReqDescription
orgstringyes–
predicate_typestring––

No output schema declared.

No examples provided.

list_attestations ~180

No description provided.

NameTypeReqDescription
ownerstringyes–
predicate_typestring––
repostringyes–
subject_digeststringyes–

No output schema declared.

No examples provided.

list_attestations_by_digests ~145

No description provided.

NameTypeReqDescription
orgstringyes–
predicate_typestring––
subject_digestsarrayyes–

No output schema declared.

No examples provided.

list_attestations_by_digests_user ~145

No description provided.

NameTypeReqDescription
predicate_typestring––
subject_digestsarrayyes–
usernamestringyes–

No output schema declared.

No examples provided.

list_attestations_organization ~114

No description provided.

NameTypeReqDescription
orgstringyes–
predicate_typestring––
subject_digeststringyes–

No output schema declared.

No examples provided.

list_attestations_user ~114

No description provided.

NameTypeReqDescription
predicate_typestring––
subject_digeststringyes–
usernamestringyes–

No output schema declared.

No examples provided.

list_autolinks ~87

No description provided.

NameTypeReqDescription
ownerstringyes–
repostringyes–

No output schema declared.

No examples provided.

list_blocked_users ~48

No description provided.

NameTypeReqDescription
orgstringyes–

No output schema declared.

No examples provided.

list_blocked_users_personal ~28

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_blocking_dependencies ~96

No description provided.

NameTypeReqDescription
issue_numberintegeryes–
ownerstringyes–
repostringyes–

No output schema declared.

No examples provided.

list_blocking_issues ~95

No description provided.

NameTypeReqDescription
issue_numberintegeryes–
ownerstringyes–
repostringyes–

No output schema declared.

No examples provided.

list_branch_access_restrictions ~100

No description provided.

NameTypeReqDescription
branchstringyes–
ownerstringyes–
repostringyes–

No output schema declared.

No examples provided.

list_branch_protection_users ~129

No description provided.

NameTypeReqDescription
branchstringyes–
ownerstringyes–
repostringyes–

No output schema declared.

No examples provided.

list_branch_rules ~108

No description provided.

NameTypeReqDescription
branchstringyes–
ownerstringyes–
repostringyes–

No output schema declared.

No examples provided.

list_branches ~133

No description provided.

NameTypeReqDescription
ownerstringyes–
protectedboolean––
repostringyes–

No output schema declared.

No examples provided.

list_branches_for_commit ~113

No description provided.

NameTypeReqDescription
commit_shastringyes–
ownerstringyes–
repostringyes–

No output schema declared.

No examples provided.

list_caches ~115

No description provided.

NameTypeReqDescription
directionstring––
keystring––
ownerstringyes–
repostringyes–

No output schema declared.

No examples provided.

list_campaigns ~82

No description provided.

NameTypeReqDescription
directionstring––
orgstringyes–
statestring––

No output schema declared.

No examples provided.

list_check_run_annotations ~105

No description provided.

NameTypeReqDescription
check_run_idintegeryes–
ownerstringyes–
repostringyes–

No output schema declared.

No examples provided.

list_check_runs ~157

No description provided.

NameTypeReqDescription
check_namestring––
check_suite_idintegeryes–
filterstring––
ownerstringyes–
repostringyes–

No output schema declared.

No examples provided.

list_check_runs_for_ref ~180

No description provided.

NameTypeReqDescription
check_namestring––
filterstring––
ownerstringyes–
refstringyes–
repostringyes–

No output schema declared.

No examples provided.

list_check_suites ~161

No description provided.

NameTypeReqDescription
check_namestring––
ownerstringyes–
refstringyes–
repostringyes–

No output schema declared.

No examples provided.

list_child_teams ~81

No description provided.

NameTypeReqDescription
orgstringyes–
team_slugstringyes–

No output schema declared.

No examples provided.

list_classrooms ~36

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_code_scanning_alert_instances ~153

No description provided.

NameTypeReqDescription
alert_numberintegeryes–
ownerstringyes–
repostringyes–

No output schema declared.

No examples provided.

list_code_scanning_alerts ~133

No description provided.

NameTypeReqDescription
assigneesstring––
directionstring––
orgstringyes–
statestring––

No output schema declared.

No examples provided.

list_code_scanning_alerts_repository ~189

No description provided.

NameTypeReqDescription
assigneesstring––
directionstring––
ownerstringyes–
repostringyes–
statestring––

No output schema declared.

No examples provided.

list_code_scanning_analyses ~111

No description provided.

NameTypeReqDescription
directionstring––
ownerstringyes–
repostringyes–
sarif_idstring––

No output schema declared.

No examples provided.

list_code_security_configuration_repositories ~88

No description provided.

NameTypeReqDescription
configuration_idintegeryes–
enterprisestringyes–

No output schema declared.

No examples provided.

list_code_security_configurations ~60

No description provided.

NameTypeReqDescription
enterprisestringyes–

No output schema declared.

No examples provided.

list_code_security_configurations_for_org ~89

No description provided.

NameTypeReqDescription
orgstringyes–
target_typestring––

No output schema declared.

No examples provided.

list_codeowners_errors ~84

No description provided.

NameTypeReqDescription
ownerstringyes–
repostringyes–

No output schema declared.

No examples provided.

list_codeql_databases ~84

No description provided.

NameTypeReqDescription
ownerstringyes–
repostringyes–

No output schema declared.

No examples provided.

list_codes_of_conduct ~34

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_codespace_machines ~90

No description provided.

NameTypeReqDescription
ownerstringyes–
repostringyes–

No output schema declared.

No examples provided.

list_codespace_machines_available ~61

No description provided.

NameTypeReqDescription
codespace_namestringyes–

No output schema declared.

No examples provided.

list_codespace_secrets ~87

No description provided.

NameTypeReqDescription
ownerstringyes–
repostringyes–

No output schema declared.

No examples provided.

list_codespace_secrets_for_user ~40

No description provided.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_codespaces ~49

No description provided.

NameTypeReqDescription
repository_idinteger––

No output schema declared.

No examples provided.

list_codespaces_in_repository ~88

No description provided.

NameTypeReqDescription
ownerstringyes–
repostringyes–

No output schema declared.

No examples provided.

list_collaborators ~163

No description provided.

NameTypeReqDescription
affiliationstring––
ownerstringyes–
permissionstring––
repostringyes–

No output schema declared.

No examples provided.

list_comment_reactions ~129

No description provided.

NameTypeReqDescription
comment_idstringyes–
contentstring––
ownerstringyes–
repostringyes–

No output schema declared.

No examples provided.

list_commit_activity_stats ~82

No description provided.

NameTypeReqDescription
ownerstringyes–
repostringyes–

No output schema declared.

No examples provided.

Install

How do I install the com.mcparmory/github MCP server?

com.mcparmory/github runs locally as a PyPI package, launched with uvx mcparmory-github. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcparmory-github

# add to Claude Code
claude mcp add com-mcparmory-github -- uvx mcparmory-github
Common questions

What is the com.mcparmory/github MCP server?

com.mcparmory/github is an MCP server listed in the public MCP registry as com.mcparmory/github. Manage repositories, users, releases, and automate GitHub workflows. This page covers its PyPI package (mcparmory-github).

Is the com.mcparmory/github MCP server safe to use?

com.mcparmory/github scores 54 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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.

Is the com.mcparmory/github MCP server still maintained?

com.mcparmory/github is still listed as active in the MCP registry. We last reached this channel on 5 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 com.mcparmory/github MCP server under?

com.mcparmory/github declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the com.mcparmory/github MCP server?

VerifyMCP ran 11 checks on com.mcparmory/github, covering Malware scan, Known CVEs, Install scripts, Dependency health and 7 more. 3 items could not be completed, a gap on our side rather than a finding about com.mcparmory/github: Schema quality, Tool coverage and Tool safety. 3 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.