Github Security (rickardhf) MCP Server
@rickardhf/github-security-mcp-server
npm
v1.2.0
Published by @rickardhf — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.
Started at 100 and nothing was deducted: the deterministic scan raised no scored threat in the published surface it inspected. Capability observations and advisory notes are recorded but never lower the score.
Findings 7
high Shell/command execution in server code (dist/common/utils.js)MTC-SRC-002
In the server's implementation (`dist/common/utils.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: child_process
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/common/utils.js
medium Hardcoded egress to an external endpoint (dist/index.js)MTC-SRC-003
In the server's implementation (`dist/index.js:24`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: fetch(`https://api.github.com/users/${username}`
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/index.js
medium Hardcoded egress to an external endpoint (dist/operations/api/branch.js)MTC-SRC-003
In the server's implementation (`dist/operations/api/branch.js:13`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: fetch(`https://api.github.com/repos/${owner}/${repository}/git/refs/heads/${branchName}`
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/operations/api/branch.js
medium Hardcoded egress to an external endpoint (dist/operations/api/issues.js)MTC-SRC-003
In the server's implementation (`dist/operations/api/issues.js:6`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: fetch(`https://api.github.com/repos/${owner}/${repository}/issues`
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/operations/api/issues.js
medium Hardcoded egress to an external endpoint (dist/operations/api/pull-requests.js)MTC-SRC-003
In the server's implementation (`dist/operations/api/pull-requests.js:6`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: fetch(`https://api.github.com/repos/${owner}/${repository}/pulls`
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/operations/api/pull-requests.js
medium Hardcoded egress to an external endpoint (dist/operations/api/repo.js)MTC-SRC-003
In the server's implementation (`dist/operations/api/repo.js:6`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: fetch(`https://api.github.com/repos/${owner}/${repository}`
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/operations/api/repo.js
medium Hardcoded egress to an external endpoint (dist/operations/security.js)MTC-SRC-003
In the server's implementation (`dist/operations/security.js:7`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: fetch(`https://api.github.com/repos/${owner}/${repository}/dependabot/alerts`
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/operations/security.js
What this scan could not see
- No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Versions
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.2.0 latest |
A 100/100 | 7 | 1.5.0 | 2026-07-22 |
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.
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 @rickardhf/github-security-mcp-server --onlineOther implementations of Github Security 1
Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →
More in Security & Testing
Security scan results for the 1claw MCP server.
Security scan results for the 1password MCP server.
Security scan results for the 1password MCP server.
Security scan results for the A11y MCP server.
Security scan results for the A11y Tools MCP server.
Security scan results for the Abuseipdb MCP server.