Is @modelcontextprotocol/server-github safe?
archived upstream, no fixes coming Facts from the Credenzo registry about the npm package @modelcontextprotocol/server-github. The same data is served as JSON.
Check it from your terminal
mcp-audit vet @modelcontextprotocol/server-githubOffline: it uses the registry bundled with Credenzo. mcp-audit update-registry fetches the newest one.
Registry facts
| Maintainer | Anthropic |
|---|---|
| Verified publisher | yes |
| Maintenance | Archived upstream (notice): no security fixes are coming. Successor: github/github-mcp-server. |
| Entry last checked | 2026-11-04 |
| Hash pins | yes; check them with mcp-audit scan --verify-hashes |
| Provenance expected | no |
| Repository | https://github.com/modelcontextprotocol/servers-archived |
Recorded advisories 0
No advisories are recorded for this package.
What it can do
- It can read or change git repositories.
- It can make outbound network requests.
- It can post to shared services such as GitHub issues, Slack or Jira.
Capability tags come from the registry. Credenzo uses them to find dangerous combinations with your other servers.
Check how you run it
This page describes the public package. What matters is your setup: which version you pin, which secrets you pass, and which other servers sit next to it.
mcp-audit checkBadge for your README
mcp-auditarchived · no fixes coming
Preview drawn by this page. The real badge is rendered by shields.io from this JSON and updates when the registry does.
[](https://mcp-audit.dev/servers/npm/at-modelcontextprotocol-server-github/)