GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Computer or cloud
pinright
Overview
Description from the maker (original English)
Version-accurate library docs for coding agents, with a supply-chain check of each dependency.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiEarly↓ 551/wk · ★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Developer tools
- You need to fill in: GITHUB_TOKEN
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
GITHUB_TOKEN,PINRIGHT_GH_CLI
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"pinright": {
"command": "npx",
"args": [
"-y",
"pinright"
],
"env": {
"GITHUB_TOKEN": "your-value",
"PINRIGHT_GH_CLI": "your-value"
}
}
}
}Run this in your terminal
claude mcp add pinright --env GITHUB_TOKEN=your-value --env PINRIGHT_GH_CLI=your-value -- npx -y pinrightFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"pinright": {
"command": "npx",
"args": [
"-y",
"pinright"
],
"env": {
"GITHUB_TOKEN": "your-value",
"PINRIGHT_GH_CLI": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"pinright": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"pinright"
],
"env": {
"GITHUB_TOKEN": "your-value",
"PINRIGHT_GH_CLI": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
- Optional. Raises the GitHub API limit from 60 to 5,000 requests an hour (monorepo docs, upgrade guides). Read-only use.
PINRIGHT_GH_CLIenvOptional. 1 uses the GitHub CLI login (gh auth token) when GITHUB_TOKEN is not set.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Hiper-AI, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Developer toolsi
- More stars than 0% of the other 4929 servers in this category
- Published to the registry more recently than 88% of the other 4929 servers in this category
- Basic checks equal to or better than 100% of the other 4929 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is pinright safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: GITHUB_TOKEN
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 4 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Desktop Commander
MCP server for terminal commands, file operations, and process management
Runs on your computer
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
pinright
Version-accurate docs and a dependency check for coding agents. Your agent gets library versions from one of two places: its memory, where about 40% of the pins it wrote in our benchmark carried a known advisory, or a docs MCP server, which returns documentation and does not check the version against advisories. pinright gives it the docs for the exact version it installs and a verdict on every dependency it adds, before the install runs. MCP server, pre-install hook, CLI and GitHub Action, all local.
Install
Node 20.9 or newer. One line, then restart the agent:
npm i -g pinright && pinright init --user # just you, every project; the hook starts in about 0.2 snpx -y pinright init # your team: writes project files you commit
init wires the MCP server, the pre-install hook where the client has one, and a starter .pinright.json. 16 clients; six have a hook: Claude Code, Cursor, VS Code (GitHub Copilot), OpenAI Codex, Gemini CLI and Windsurf. The Cursor and VS Code buttons above add the MCP server only. Every client, scopes and pinright doctor.
Without pinright, with pinright
Without. The agent runs npm install lodash@4.17.20. It installs. The lockfile now carries five advisories, two of them high, and nobody is told.
With. The hook answers before the command runs, and the agent reads this:
pinright blocked this dependency change:- lodash@4.17.20 (npm) has 5 known advisories (CVE-2021-23337, CVE-2026-4800, CVE-2020-28500, HIGH). Use 4.x release 4.18.1: npm install lodash@4.18.1
Change the version (or the name) and try again. check-package and get-docs from the pinright MCP server explain each case.
The agent retries with 4.18.1, on the same release line. When it asks first, check-package and get-docs give it the same verdict with the full advisory list, the version to pin, and the docs for that version. Real output of pinright hook claude, 2026-11-01.
Why pinright
Docs MCP servers return documentation for a library. They do not check the version the agent pins, and they do not see the install. To measure that kind of server we ran pinright's own server with its security layer off (PINRIGHT_ABLATION=docs-only): docs for the version asked, no verdict. It is not another product. Claude Code with Sonnet 5.5, Haiku 5.5 and Opus 5.5, 2 runs per cell, on the 1.0.0 code; each cell gives the range over the three models.
| No docs | Docs-only context server | pinright | |
|---|---|---|---|
| Direct dependencies pinned with a known advisory | 40% to 42% | 0% to 2% | 0% |
Whole-tree alerts per project (npm audit, pip-audit) | 29.8 to 31.9 | 0.3 to 3.5 | 0.3 |
| Docs tasks that used the current API | 9 to 14 of 16 | 15 or 16 of 16 | 16 of 16 |
| Tokens per agent task | 15k to 21k | 56k to 94k | 42k to 74k |
| Tokens per docs task | 17k to 23k | 94k to 135k | 63k to 95k |
| Agent turns per agent task | 4.0 to 4.3 | 9.3 to 11.1 | 5.9 to 7.5 |
| MCP tool text read per agent task | none | 25k to 45k characters | 5k to 17k characters |
| Verdict on the version the agent pins | no | no | advisories, malware, lookalikes, versions that do not exist |
| Check when the install runs | no | no | pre-install hook in 6 clients |
| Whole-tree lockfile audit | no | no | check-manifest, SARIF, GitHub Action |
Current docs alone removed most alerts; the verdict removed the rest. Per model, pinright used 21% to 26% fewer tokens than the docs-only server on the 12 agent tasks and 26% to 33% fewer on the 8 docs tasks. Every paired interval stays above zero; the lowest bound is 2%. Tokens count everything the model processed, cache reads included. No tools at all costs less than either.
Why fewer tokens. With docs only, the agent looked versions up through the docs: it called get-docs once per package, 5.2 to 5.7 times per agent task, before writing a file. 87% of those calls named no version, so they returned the docs of the latest release, and 75% asked for "version" or "latest" in the query. With pinright, every agent-task run opened with check-packages for the whole list, about 600 characters of verdicts and versions to pin, then called get-docs 0.7 to 1.7 times per task, with a version in 86 of 87 calls.
Limits. The 0.3 left is nuxt, whose current release pulls packages with no fix published; installing with no version gets the same 0.3, and the docs-only and pinright alert intervals overlap. One vendor's models, tasks we wrote, no shell, two days of advisory data, small n. In a second run with a shell, the agents looked versions up with npm view or pip index before pinning, and every arm ended at the same 6 alerts per model: there pinright made no measurable difference to the pins. On APIs released after August 2026, 2 of 48 runs got the current API without docs, 45 of 48 with docs only and 46 of 48 with pinright. On 12 tasks taken from public GitHub issues, 25% to 29% of direct pins carried an advisory without docs and none with pinright. The hook blocked or asked on 1.46% of 25,077 public commands and misread 10 of 154,402 tool calls from a month of our own agent sessions. Per-model tables · results and caveats · technical report · reproduce it
Against a widely used docs MCP server
People ask how pinright compares with the docs MCP servers they already use. We added one, a widely used local server with a free API key, as an arm of the same benchmarks: run v8, 2026-11-04, every arm on the same day and the same advisory data. Range over Sonnet 5.5, Haiku 5.5 and Opus 5.5, 2 runs per cell.
| No tools | Docs MCP server | pinright | Both installed | |
|---|---|---|---|---|
| Direct deps pinned with a known advisory, our 12 tasks | 40% to 41% | 28% to 35% | 0% | 0% |
| Same, 12 tasks taken from GitHub issues | 27% to 32% | 15% to 21% | 0% | 0% |
| Whole-tree alerts per project, our 12 tasks | 29.4 to 33.0 | 14.7 to 18.6 | 0.3 | 0.3 |
| Docs tasks that used the current API (of 16) | 10 to 12 | 12 to 16 | 14 to 16 | n/a |
| Same, APIs released after the training cutoff (of 16) | 0 or 1 | 11 or 13 ¹ | 16 | n/a |
| Tokens per agent task | 15k to 21k | 47k to 61k | 43k to 80k | 53k to 84k |
| Tokens per docs task | 17k to 22k | 53k to 77k | 70k to 105k | n/a |
| Checks the version the agent pins | no | no | yes | yes |
| Stops the install of a vulnerable version | no | no | pre-install hook | pre-install hook |
¹ Sonnet and Haiku; the free key hit its monthly quota during the Opus runs.
The docs MCP server moved agents to newer versions and halved the alerts, but it does not check the version the agent picks: its most common vulnerable pin was next@16.2.9 (20 advisories, 11 runs), the Next.js version it served docs for. It used fewer tokens than pinright in most cells, because its answers are shorter. With both installed, the agent took its versions from pinright and called the docs server 6 times in 144 runs. One docs server, one release, tasks we wrote or picked, no shell. Per-model tables
Ask your agent
- "Add zod and pin a version with no known advisories."
- "Show me the docs for the version of next this project has installed."
- "Audit package-lock.json and tell me what to upgrade, on the same release lines."
- "What changed between express 4 and 5 before I move?"
Tools
| Tool | What it does |
|---|---|
check-packages | The verdict for up to 50 packages in one call: version to pin, short reason, full notice only where it matters |
check-package | One package in depth: advisories with CVE and fix, deprecation, license, lookalike names, policy violations |
get-docs | Docs from the published package and its repo at the release tag, for the version you name or the one installed |
find-library | Library name to registry package (next.js to npm:next), with the safe version |
upgrade-guide | What changes between two versions: breaking changes, renamed APIs, advisories the move fixes |
check-manifest | Whole-tree audit of a lockfile or manifest, with SARIF; the GitHub Action runs it in CI |
Ecosystems: npm, PyPI, Cargo, Go, Maven and Gradle, NuGet, RubyGems, Composer, GitHub Actions. Verdicts never say ok when a source did not answer. A committed .pinright.json sets allow and deny lists, license rules, severity threshold and what to do when a source is down. How it works · the hook · team policy · CLI · GitHub Action
Privacy and limits
No account, no telemetry. pinright sends package names and versions to deps.dev, OSV, the registries, jsDelivr and GitHub, never your code; SECURITY.md lists each host. The hook reads commands and files statically: it is a guardrail, not a sandbox, and the threat model lists what gets past it. When a source is down the built-in default lets the install through; the starter policy asks instead.
More
Install · prompt injection · benchmark · security review · changelog · contributing · release runbook
The report we value most is a false positive: a command the hook blocked, or a package it
Only the beginning is shown; read the rest in the repo