KalelAufa/github-mcp-server (KalelAufa/github-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 97 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
10 days ago

KalelAufa/github-mcp-server

Production-ready GitHub MCP Server with full GitHub API coverage

→ KalelAufa/github-mcp-server· npm: @kalelaufa/github-mcp-server· listed on npm

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

KalelAufa

Source: npm

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

npmscored separately

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 5 credentials: GH_TOKEN, GITHUB_APP_PRIVATE_KEY, GITHUB_MCP_SECRET, GITHUB_OAUTH_CLIENT_SECRET, GITHUB_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretGH_TOKENGITHUB_TOKEN / GH_TOKEN / GITHUB_PAT or auth store
configGITHUB_APP_ID
configGITHUB_APP_INSTALLATION_ID
🔐 secretGITHUB_APP_PRIVATE_KEY
configGITHUB_APP_PRIVATE_KEY_PATH
configGITHUB_CLONE_DIRDirectory for cloned repos
configGITHUB_DEFAULT_OWNERDefault repo owner when a tool omits owner
configGITHUB_DEFAULT_REPODefault repo when a tool omits repo
configGITHUB_MCP_CONFIG$ (if set)
configGITHUB_MCP_LOG_LEVELtrace debug info warn error
configGITHUB_MCP_PORTFor http/sse, also set (default 3000).
🔐 secretGITHUB_MCP_SECRET
configGITHUB_MCP_TIMEOUTRequest timeout (ms)
configGITHUB_MCP_TRANSPORTThe server supports three transports, selected via
configGITHUB_OAUTH_CLIENT_ID
🔐 secretGITHUB_OAUTH_CLIENT_SECRET
configGITHUB_OAUTH_SCOPES
configGITHUB_ORGDefault organization
configGITHUB_PATGITHUB_TOKEN / GH_TOKEN / GITHUB_PAT or auth store
configGITHUB_PROXYOutbound proxy URL
🔐 secretGITHUB_TOKENGITHUB_TOKEN / GH_TOKEN / GITHUB_PAT or auth store
configGITHUB_WORKSPACEWorkspace path
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

97/97 tools missing one or more hints — create_repository (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); delete_repository (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_repository (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +94 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tool test coverage

Only 3/97 tools referenced in tests (3%)

Write tests that reference each tool by name so every tool has at least one test.

Dependency freshness

1/10 production deps stale: tweetnacl@2023-04-12 (3.4y)

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/kalelaufa/github-mcp-server)](https://m8ven.ai/mcp/kalelaufa/github-mcp-server)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 6f8668636544590e293783e62eddbd29231c9ba6
code hash: 5aa4e70509c23dc68185c7494f1ef3b8705da6c019079bb82876b4e8dad014f7
verified: 9/3/2026, 5:21:46 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client