# pinright (npm · pinright)

Version-accurate library docs for coding agents, with a supply-chain check of each dependency.

- Trust score: 79/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `pinright`: 79/100 (this document), [markdown](https://verifymcp.io/servers/hiper-ai-pinright/pinright.md), [page](https://verifymcp.io/servers/hiper-ai-pinright/pinright)

## Channel facts

- Registry: `npm`
- Package: `pinright`
- Version: `1.0.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 5 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to Hiper-AI/pinright).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 17 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1682 tokens (~280/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 96% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the pinright MCP server?

pinright runs locally as an npm package, launched with npx -y pinright. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add hiper-ai-pinright -- npx -y pinright
```

### Cursor

```json
{
  "mcpServers": {
    "hiper-ai-pinright": {
      "command": "npx",
      "args": [
        "-y",
        "pinright"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "hiper-ai-pinright": {
      "command": "npx",
      "args": [
        "-y",
        "pinright"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add hiper-ai-pinright -- npx -y pinright
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hiper-ai-pinright": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "pinright"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add hiper-ai-pinright --command npx --arg -y --arg pinright
```

### Hermes

```yaml
mcp_servers:
  hiper-ai-pinright:
    command: "npx"
    args: ["-y", "pinright"]
```

### Netclaw

```json
{
  "McpServers": {
    "hiper-ai-pinright": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "pinright"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add hiper-ai-pinright -t stdio -c npx -a -y pinright
```

### Other

```json
{
  "mcpServers": {
    "hiper-ai-pinright": {
      "command": "npx",
      "args": [
        "-y",
        "pinright"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 79, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 64)

First indexed and scored.

## MCP tools (6)

### `find-library` (~175 tokens)

Find a library (with security verdict)

Finds the registry package for a library name ("next.js" -> npm:next, "pytorch" -> pypi:torch) and returns ids for get-docs, with the newest version that has no known advisories (safe) and a verdict. Skip it when you know the registry name: get-docs takes "npm:next" or "pypi:requests" directly, and check-packages takes plain names.

Input parameters:

- `ecosystem` (string): npm, pypi, cargo, go, maven, nuget, rubygems or composer, when you know it.
- `libraryName` (string, required): Library name, e.g. "next.js", "requests", "tokio".
- `query` (string, required): What you want to do with it; also used to guess the language.

### `get-docs` (~293 tokens)

Documentation for the version you will use (security-checked)

Returns the documentation sections that answer your question, taken from the package at a specific version (its published files and its repo at the release tag) and the project site. Without a version it documents the newest version with no known advisories. With a vulnerable version it starts with a SECURITY NOTICE and documents the safe version on the same release line, so the code you write keeps working after the upgrade.

Input parameters:

- `ecosystem` (string): Registry, when the id does not say it or says the wrong one; overrides the id.
- `libraryId` (string): Id from find-library, e.g. "npm:next" or "npm:next@15.1.0". A GitHub repo ("/vercel/next.js") also works. Or pass name and ecosystem instead.
- `name` (string): Package name with ecosystem, as check-package takes them, instead of libraryId.
- `packageName` (string): Registry package name, when it differs from the id; overrides the id.
- `query` (string): The question or task, e.g. "protect routes with middleware". Without it: setup and main API.
- `tokens` (integer): Approximate size of the answer in tokens (default 2500; raise it only when the answer was cut short).
- `version` (string): Version the project uses or pins, if any. Overrides the one in libraryId.

### `check-package` (~177 tokens)

Check a package before installing it

Supply-chain verdict for one package, no docs: known advisories (CVE/GHSA, malware), deprecation, license, newest version with no known advisories, the safe version on the same release line as the one you pass, and typosquat lookalikes. For several packages use check-packages, one call for the whole list.

Input parameters:

- `detail` (boolean): Return the full JSON report (every advisory, dates, sources) instead of the summary.
- `ecosystem` (string, required): npm, pypi, cargo, go, maven, nuget, rubygems or composer (aliases like "python" work).
- `name` (string, required): Package name as the registry knows it, e.g. "lodash", "requests".
- `version` (string): Version you intend to install or already use.

### `check-packages` (~128 tokens)

Check a whole dependency list in one call

Supply-chain verdict for up to 50 packages at once: one table row per package (verdict, version to pin, short reason) and the full notice only for the ones that need attention. Call it once with every dependency you plan to add, before writing the manifest, instead of one check per package. Packages already in the project are checked at their installed version when you omit it.

Input parameters:

- `ecosystem` (string): Default for every package: npm, pypi, cargo, go, maven, nuget, rubygems or composer.
- `packages` (array, required)

### `check-manifest` (~285 tokens)

Audit a whole dependency tree

Audits every package in a lockfile (direct and transitive) against OSV, the way Dependabot would, and says how to fix each finding: the direct upgrade on the same release line, the parent upgrade that clears a transitive one, or an override. Pass a project directory or a file path, or the file content with its name. Supported: package-lock.json, npm-shrinkwrap.json, pnpm-lock.yaml, yarn.lock, package.json, requirements.txt, poetry.lock, uv.lock, pdm.lock, pyproject.toml, Cargo.lock, Cargo.toml, go.mod, Gemfile.lock, packages.lock.json, gradle.lockfile, pom.xml, build.gradle, build.gradle.kts, libs.versions.toml, composer.lock, composer.json, requirements*.txt. Without a lockfile the tree is resolved through deps.dev. GitHub workflows (.github/workflows/*.yml, action.yml, or the directory) get an Actions check: advisories and SHA pinning.

Input parameters:

- `content` (string): File content, when the file is not on disk yet.
- `fileName` (string): Name of the file in content, e.g. "package-lock.json".
- `includeDev` (boolean): Include dev dependencies (default true).
- `path` (string): Project directory or path to a lockfile/manifest.

### `upgrade-guide` (~299 tokens)

What changes between two versions

Breaking changes, removed or renamed APIs, config and default changes, packages that split off, deprecations, and the advisories fixed, between the version a project uses and the one to move to. Sources: changelogs and GitHub release notes for the versions in between, migration guides when a major is crossed, and (npm) a diff of the exported .d.ts API. Call it before upgrading across a major, when a SECURITY NOTICE recommends a new major, or to fix a Dependabot PR. Without "to" it uses the version pinright recommends.

Input parameters:

- `ecosystem` (string): npm, pypi, cargo, go, maven, nuget or rubygems.
- `from` (string): Version the project uses now, e.g. "15.5.28" (a range like "4.x" picks its newest release).
- `libraryId` (string): Id like "npm:next" or "pypi:langchain" (a version in it is used as "from").
- `package` (string): Package name, with ecosystem, instead of libraryId.
- `query` (string): What you are changing, e.g. "middleware auth redirect"; ranks entries about it first.
- `to` (string): Version to move to. Default: the recommended safe version.
- `tokens` (integer): Approximate size of the answer in tokens (default 5000).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/hiper-ai-pinright/pinright#diagnostics

## Score history

- 2026-11-21: 79
- 2026-11-20: 79
- 2026-11-19: 79
- 2026-11-18: 79
- 2026-11-17: 79
- 2026-11-16: 79
- 2026-11-15: 79
- 2026-11-14: 79
- 2026-11-13: 79
- 2026-11-12: 79
- 2026-11-11: 79
- 2026-11-10: 79
- 2026-11-09: 79
- 2026-11-08: 79
- 2026-11-07: 79
- 2026-11-06: 79
- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 64

## Common questions

### What is the pinright MCP server?

pinright is an MCP server listed in the public MCP registry as io.github.Hiper-AI/pinright. Version-accurate library docs for coding agents, with a supply-chain check of each dependency. This page covers its npm package (pinright).

### Is the pinright MCP server safe to use?

pinright scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the pinright MCP server expose?

pinright exposes 6 tools: find-library, get-docs, check-package, check-packages, check-manifest, upgrade-guide. Their descriptions and schemas cost roughly 1,357 tokens of context every time the server is loaded.

### Is the pinright MCP server still maintained?

pinright is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the pinright MCP server under?

pinright declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the pinright MCP server?

VerifyMCP ran 15 checks on pinright, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about pinright: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/pinright
- Socket report: https://socket.dev/npm/package/pinright
- Repository: https://github.com/Hiper-AI/pinright
- Website: https://pinright.dev/
- Changelog RSS feed: https://verifymcp.io/servers/hiper-ai-pinright/pinright.xml
- Changelog JSON feed: https://verifymcp.io/servers/hiper-ai-pinright/pinright/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/hiper-ai-pinright/pinright.json
- HTML version of this page: https://verifymcp.io/servers/hiper-ai-pinright/pinright
