npx-vibe
NPM · NPX-VIBE · SCANNED SEP 21
Read-only npm package and project dependency preflight tools for AI applications.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Devrajsinh-Jhala/NPM-Vibe-check). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 18 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 453 tokens (~151/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the npx-vibe MCP server?
npx-vibe runs locally as an npm package, launched with npx -y npx-vibe. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · npx-vibe
claude mcp add devrajsinh-jhala-npx-vibe -- npx -y npx-vibe
{
"mcpServers": {
"devrajsinh-jhala-npx-vibe": {
"command": "npx",
"args": [
"-y",
"npx-vibe"
]
}
}
} {
"servers": {
"devrajsinh-jhala-npx-vibe": {
"command": "npx",
"args": [
"-y",
"npx-vibe"
]
}
}
} codex mcp add devrajsinh-jhala-npx-vibe -- npx -y npx-vibe
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"devrajsinh-jhala-npx-vibe": {
"type": "local",
"command": [
"npx",
"-y",
"npx-vibe"
],
"enabled": true
}
}
} openclaw mcp add devrajsinh-jhala-npx-vibe --command npx --arg -y --arg npx-vibe
mcp_servers:
devrajsinh-jhala-npx-vibe:
command: "npx"
args: ["-y", "npx-vibe"] {
"McpServers": {
"devrajsinh-jhala-npx-vibe": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"npx-vibe"
]
}
}
} assistant mcp add devrajsinh-jhala-npx-vibe -t stdio -c npx -a -y npx-vibe
{
"mcpServers": {
"devrajsinh-jhala-npx-vibe": {
"command": "npx",
"args": [
"-y",
"npx-vibe"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 −3
- Stability: pass → 0.80 functional
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −3
- Stability: pass → 0.80 functional
- 12 Sept 26 +1
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/npx-vibe@1.6.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Devrajsinh-Jhala/NPM-Vibe-check |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Devrajsinh-Jhala/NPM-Vibe-check/.github/workflows/release.yml@refs/tags/v1.6.0 |
| Rekor log index | 2666151755 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:de9d27031ff7692bc75c28e52a894734942b3b3ee98c4d847034c2b0dcd9360f60eb8b36f3548eae1118c8855064ac405b1206286e088e503537c9dc3 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_models List recommended AI models ~33
Return the provider model recommendations bundled with this npx-vibe release. This does not access a model provider or require credentials.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| defaultProfile | string | yes | – |
| profiles | array | yes | – |
| providers | array | yes | – |
| schemaVersion | integer | yes | – |
| tool | object | yes | – |
No examples provided.
scan_package Scan an npm package ~141
Resolve, verify, and inspect one public npm registry package without executing package code. Use before installing, recommending, or running an unfamiliar package. Obey decision.action: continue, review, stop, or retry.
| Name | Type | Req | Description |
|---|---|---|---|
| ai | string | – | Optional AI review mode. Heuristic-only scanning is the default. |
| model | string | – | Optional exact provider model identifier. |
| modelProfile | string | – | Maintained quality, latency, and cost profile. |
| package | string | yes | npm package spec such as esbuild, @scope/tool, or package@version. |
| provider | string | – | AI provider. Credentials are read from environment variables, never tool arguments. |
| Name | Type | Req | Description |
|---|---|---|---|
| decision | object | yes | – |
| error | object | – | – |
| kind | string | yes | – |
| report | object | – | – |
| schemaVersion | integer | yes | – |
| status | string | yes | – |
| subject | object | – | – |
| tool | object | yes | – |
No examples provided.
scan_project Scan project dependencies ~238
Inspect public-registry dependencies from package.json and package-lock.json without installing or executing them. Direct dependencies by default; set transitive to walk the whole installed tree. Use after dependency or lockfile changes and before installation.
| Name | Type | Req | Description |
|---|---|---|---|
| ai | string | – | Optional AI review mode. Heuristic-only scanning is the default. |
| aiLimit | integer | – | Maximum triggered AI reviews when AI is explicitly enabled. |
| concurrency | integer | – | Maximum concurrent heuristic package scans. |
| includeDev | boolean | – | Include devDependencies in addition to production and optional dependencies. |
| maxPackages | integer | – | Maximum packages scanned in one project scan. |
| model | string | – | Optional exact provider model identifier. |
| modelProfile | string | – | Maintained quality, latency, and cost profile. |
| path | string | – | Project directory or package.json path, relative to the MCP server working directory or absolute. |
| provider | string | – | AI provider. Credentials are read from environment variables, never tool arguments. |
| transitive | boolean | – | Scan every registry-resolved package in package-lock.json, not only direct dependencies. Requires a lockfile and scans many more packages. |
| Name | Type | Req | Description |
|---|---|---|---|
| decision | object | yes | – |
| error | object | – | – |
| kind | string | yes | – |
| report | object | – | – |
| schemaVersion | integer | yes | – |
| status | string | yes | – |
| subject | object | – | – |
| tool | object | yes | – |
No examples provided.
What is the npx-vibe MCP server?
npx-vibe is an MCP server listed in the public MCP registry as io.github.Devrajsinh-Jhala/npx-vibe. Read-only npm package and project dependency preflight tools for AI applications. This page covers its npm package (npx-vibe).
Is the npx-vibe MCP server safe to use?
npx-vibe scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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 npx-vibe MCP server expose?
npx-vibe exposes 3 tools: scan_package, scan_project, list_models. Their descriptions and schemas cost roughly 412 tokens of context every time the server is loaded.
Is the npx-vibe MCP server still maintained?
npx-vibe is still listed as active in the MCP registry. We last reached this channel on 21 September 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 npx-vibe MCP server under?
npx-vibe declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.