io.github.jaimenbell/github-mcp
PYPI · JAIMENBELL-GITHUB-MCP · SCANNED SEP 20
MCP server for the GitHub REST API: issues, PRs, repos; read always on, write env-gated.
Available components
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 22 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 78 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 773 tokens (~55/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.jaimenbell/github-mcp server?
io.github.jaimenbell/github-mcp runs locally as a PyPI package, launched with uvx jaimenbell-github-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · jaimenbell-github-mcp
claude mcp add jaimenbell-github-mcp -- uvx jaimenbell-github-mcp
{
"mcpServers": {
"jaimenbell-github-mcp": {
"command": "uvx",
"args": [
"jaimenbell-github-mcp"
]
}
}
} {
"servers": {
"jaimenbell-github-mcp": {
"command": "uvx",
"args": [
"jaimenbell-github-mcp"
]
}
}
} codex mcp add jaimenbell-github-mcp -- uvx jaimenbell-github-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jaimenbell-github-mcp": {
"type": "local",
"command": [
"uvx",
"jaimenbell-github-mcp"
],
"enabled": true
}
}
} openclaw mcp add jaimenbell-github-mcp --command uvx --arg jaimenbell-github-mcp
mcp_servers:
jaimenbell-github-mcp:
command: "uvx"
args: ["jaimenbell-github-mcp"] {
"McpServers": {
"jaimenbell-github-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"jaimenbell-github-mcp"
]
}
}
} assistant mcp add jaimenbell-github-mcp -t stdio -c uvx -a jaimenbell-github-mcp
{
"mcpServers": {
"jaimenbell-github-mcp": {
"command": "uvx",
"args": [
"jaimenbell-github-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −18
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.80 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed pypi/jaimenbell-github-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 22 packages
| Packages resolved | 22 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
add_labels ~63
Add one or more labels to an issue or pull request. Requires GITHUB_MCP_ENABLE_WRITE=1 and GITHUB_TOKEN.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_number | integer | yes | – |
| labels | array | yes | – |
| owner | string | yes | – |
| repo | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
comment_on_issue ~62
Post a comment on an issue or pull request. Requires GITHUB_MCP_ENABLE_WRITE=1 and GITHUB_TOKEN.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| issue_number | integer | yes | – |
| owner | string | yes | – |
| repo | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
create_issue ~61
Open a new issue on a repository. Requires GITHUB_MCP_ENABLE_WRITE=1 and GITHUB_TOKEN.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | – |
| labels | – | – | – |
| owner | string | yes | – |
| repo | string | yes | – |
| title | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
create_pr_review_comment ~90
Create a review comment on a specific line of a pull request's diff. Requires GITHUB_MCP_ENABLE_WRITE=1 and GITHUB_TOKEN.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| commit_id | string | yes | – |
| line | integer | yes | – |
| owner | string | yes | – |
| path | string | yes | – |
| pr_number | integer | yes | – |
| repo | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_file_content ~63
Read a UTF-8 text file from a repo at a given path (base64-decoded). Reports binary files rather than decoding them.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | – |
| path | string | yes | – |
| ref | – | – | – |
| repo | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_issue ~49
Fetch a single issue's full detail: title, body, state, labels, comment count.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_number | integer | yes | – |
| owner | string | yes | – |
| repo | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_pull_request ~44
Fetch a single pull request's full detail, including merge state.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | – |
| pr_number | integer | yes | – |
| repo | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_repo ~52
Get metadata for a repository: description, language, stars, forks, open issues, default branch, archived flag, license, last-push time.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | – |
| repo | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_user ~27
Get a public profile for a GitHub user or organization.
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_commits ~52
List commits on a repo's default branch (or a given ref), newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| owner | string | yes | – |
| repo | string | yes | – |
| sha | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_issues ~56
List issues for a repository (pull requests filtered out), most-recently-updated first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| owner | string | yes | – |
| repo | string | yes | – |
| state | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_pull_requests ~52
List pull requests for a repository, most-recently-updated first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| owner | string | yes | – |
| repo | string | yes | – |
| state | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_repos ~37
Search public repositories by keyword/qualifiers, sorted by best match.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
update_issue_state ~65
Set an issue's state to 'open' or 'closed'. Requires GITHUB_MCP_ENABLE_WRITE=1 and GITHUB_TOKEN.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_number | integer | yes | – |
| owner | string | yes | – |
| repo | string | yes | – |
| state | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the io.github.jaimenbell/github-mcp server?
io.github.jaimenbell/github-mcp is listed in the public MCP registry as io.github.jaimenbell/github-mcp. MCP server for the GitHub REST API: issues, PRs, repos; read always on, write env-gated. This page covers its PyPI package (jaimenbell-github-mcp).
Is the io.github.jaimenbell/github-mcp server safe to use?
io.github.jaimenbell/github-mcp scores 62 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.
What tools does the io.github.jaimenbell/github-mcp server expose?
io.github.jaimenbell/github-mcp exposes 14 tools: get_repo, list_issues, get_issue, list_pull_requests, get_pull_request, and 9 more. Their descriptions and schemas cost roughly 773 tokens of context every time the server is loaded.
Is the io.github.jaimenbell/github-mcp server still maintained?
io.github.jaimenbell/github-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.