GitHub PR Context MCP (paarths-collab/github-pr-context-mcp) is an MCP server listed on the M8ven Trust Index. It scores 0 out of 100, grade F. It declares 21 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
F
Warning
0/100

GitHub PR Context MCP

Retrieves historical pull request context from GitHub repositories and provides it to IDE agents for reasoning, review, and code generation without modifying files.

→ paarths-collab/github-pr-context-mcp· listed on glama

Warning. Serious findings were identified. Review the full report before connecting. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code 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

paarths-collab

Source: Glama

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

Glamanot scored here

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.

⏳ This MCP is queued for scoring. Check back in a few minutes.
// key findings
🚨
Reads files from sensitive locations
Touches: ~/.config
🔐
You'll be asked for 6 credentials: GITHUB_TRAFFIC_TOKEN, REGISTRATION_SECRET, USAGE_METRICS_TOKEN, GITHUB_WEBHOOK_SECRET, GITHUB_TOKEN, GROQ_API_KEY
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.
configHOST
configMCP_HTTP_PATH
configGITHUB_TRAFFIC_REPO
🔐 secretGITHUB_TRAFFIC_TOKEN
configUSAGE_TRACKING_ENABLED
configAUTH_REQUIRED
configGITHUB_PR_CONTEXT_RUNTIME
🔐 secretREGISTRATION_SECRET
configMCP_PUBLIC_URL
configAUTH_REGISTRY_PATH
🔐 secretUSAGE_METRICS_TOKEN
configUSAGE_STATS_PATH
configMCP_NAMESPACE
configAUTH_SERVICE_DOC_URL
configGITHUB_APP_CLIENT_ID
configGITHUB_APP_SLUG
configGITHUB_CREDENTIAL_PROFILE
configKEEP_ALIVE_URL
configTELEMETRY
configTELEMETRY_ENDPOINT
configMCP_MODE
configUV_PROJECT_ENVIRONMENT
configPIPX_HOME
configPIPX_LOCAL_VENVS
🔐 secretGITHUB_WEBHOOK_SECRET
🔐 secretGITHUB_TOKEN
🔐 secretGROQ_API_KEY
configCURSOR_DB_PATH
configCHROMA_PERSIST_DIR
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// 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

21/21 tools missing one or more hints — update_settings (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_usage_stats (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); semantic_search_reviews (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +18 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.

Tool inputs are validated

17/21 tool handlers declare input schemas (81%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 6/21 tool handlers wrap calls in try/catch (29%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests exist

No test files found

Add tests that exercise each declared tool.

No access to sensitive paths

Reads sensitive paths: ~/.config

Remove reads of sensitive system paths. If you genuinely need them, document why in the README.

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 6 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 Verified](https://m8ven.ai/badge/mcp/paarths-collab/github-pr-context-mcp?variant=verified)](https://m8ven.ai/mcp/paarths-collab/github-pr-context-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 86537c035a3f5ba9cc897f2c046a9280fee8a27e
code hash: 50383a9ef93e9fa8687b82caf8e557c1004dbbbb37c6462d6d364780d8ef0885
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