Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

MCPSense

by fayzkk889version 0.5.1i★ 3iRuns on your computerOfficial site ↗
Registry nameio.github.fayzkk889/mcpsense

How to install

What it does

Inspect MCP configurations, tool metadata, and changes from your coding assistant.

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Developer tools

Use together with

Skills that teach the AI this kind of work; they work alongside this one

rea

Reverse engineer anything with agents, from app behavior down to native binaries.

by morluto★ 468,7331 skills

Skill · How-to guide

andrej-karpathy-skills

A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.

by multica-ai★ 234,3321 skills

Skill · How-to guideNo license stated

graphify

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.

by Graphify-Labs★ 150,2871 skills

Skill · How-to guide

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity8/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score20/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install MCPSense. Follow https://mcp.popnx.com/i/fayzkk889-mcpsense.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 15, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server MCPSense for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "mcpsense": { "command": "npx", "args": [ "-y", "mcpsense", "mcp", "serve", "--root", "your-value" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the MCPSense tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "mcpsense": {
          "command": "npx",
          "args": [
            "-y",
            "mcpsense",
            "mcp",
            "serve",
            "--root",
            "your-value"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use MCPSense and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using MCPSense or shows a MCPSense tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect MCPSense yet

MCPSense runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect MCPSense

  • Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself
  • Install Node.js on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself

B · Others in Developer tools that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server MCPSense for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user mcpsense -- npx -y mcpsense mcp serve --root your-value 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the MCPSense tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user mcpsense -- npx -y mcpsense mcp serve --root your-value
  4. Type /mcp in Claude Code

    You should see MCPSense listed as connected

  5. Try it

    Use MCPSense and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using MCPSense or shows a MCPSense tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Node.js on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server MCPSense for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "mcpsense": { "command": "npx", "args": [ "-y", "mcpsense", "mcp", "serve", "--root", "your-value" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the MCPSense tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open Cursor’s MCP settings file

    ~/.cursor/mcp.json

    Paste these settings, fill in the empty values and save

    {
      "mcpServers": {
        "mcpsense": {
          "command": "npx",
          "args": [
            "-y",
            "mcpsense",
            "mcp",
            "serve",
            "--root",
            "your-value"
          ]
        }
      }
    }
  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use MCPSense and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using MCPSense or shows a MCPSense tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Node.js on your computer first (one time) · No one-click button: paste the settings and fill in the values yourself

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server MCPSense for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "mcpsense": { "type": "stdio", "command": "npx", "args": [ "-y", "mcpsense", "mcp", "serve", "--root", "your-value" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the MCPSense tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open VS Code’s MCP settings file

    MCP: Open User Configuration

    Paste these settings, fill in the empty values and save

    {
      "servers": {
        "mcpsense": {
          "type": "stdio",
          "command": "npx",
          "args": [
            "-y",
            "mcpsense",
            "mcp",
            "serve",
            "--root",
            "your-value"
          ]
        }
      }
    }
  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use MCPSense and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using MCPSense or shows a MCPSense tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use MCPSense💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user mcpsense -- npx -y mcpsense mcp serve --root your-value

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "mcpsense": {
      "command": "npx",
      "args": [
        "-y",
        "mcpsense",
        "mcp",
        "serve",
        "--root",
        "your-value"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "mcpsense": {
      "command": "npx",
      "args": [
        "-y",
        "mcpsense",
        "mcp",
        "serve",
        "--root",
        "your-value"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "mcpsense": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "mcpsense",
        "mcp",
        "serve",
        "--root",
        "your-value"
      ]
    }
  }
}

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
309/wk
Connection
Runs on your computer
Latest versioni
0.5.1
Published to registryi
Nov 15, 2026
Code last changedi
Nov 17, 2026
Maker
fayzkk889
Packages
npm: mcpsense
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

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 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account fayzkk889, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 2 days ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – 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

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for mcpsense@0.5.1

Checks only this package version, not every dependency · checked Nov 15, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/fayzkk889-mcpsense.svg)](https://mcp.popnx.com/en/servers/fayzkk889-mcpsense)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Developer toolsi

  • More stars than 81% of the other 6136 servers in this category
  • Published to the registry more recently than 90% of the other 6136 servers in this category
  • Basic checks equal to or better than 99% of the other 6136 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 MCPSense safe?

It passed 3 of 3 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?

The registry does not list a required key, though some servers ask you to sign in on first use.

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 2 days ago, and the latest version (0.5.1) 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: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitDiagram

Architecture diagrams, explanations and Mermaid source for public GitHub repositories.

by ahmedkhaleel2004Widely used★ 19KUpdated 2 months ago

Runs in the cloud✓ service owner · gitdiagram.comTried by the PopNx team

Appllama

Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.

by AppllamaWidely used★ 5.2KUpdated 3 months ago

Runs in the cloud✓ service owner · appllama.io

Repowise

Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.

by repowise-devWidely used↓ 6.5K/wk★ 8.2K Stars for the whole repoUpdated 6 days ago

Computer or cloud✓ service owner · repowise.dev
Compared with similar ones
This one
MCPSense
GitDiagramAppllamaCloudflare MCPOmnaraRepowise
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installCloud or install on your computer
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoYesNoNo
Basic checks3/34/44/44/44/45/5
LicenseMITMITMITApache-2.0Apache-2.0AGPL-3.0
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

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.

MCPSense

MIT-licensed local security inspection for MCP configurations, source code, agent instructions, and advertised server metadata. Findings are review signals; metadata alone cannot prove exploitability or absence of compromise.

Install the latest published release from npm or GitHub/Go, using either independent route below. The linked version badges and mcpsense version --check report public availability. A source checkout or pull request can contain newer unreleased work; a source push does not update @latest. See the release-readiness record for release status.

Published 0.5.0: use the existing scanner from the terminal or your coding assistant. Both interfaces share the installed engine, every registered scanner check and the same update lifecycle. This release also rejects ambiguous JSON before inspection and retains reviewed AWS advisory evidence when the public feed is quiet. See the connection guide, release notes and verified release record.

Interactive human-readable scans/version can announce updates on stderr with a one-hour cache and two-second lookup budget. Offline scans, JSON/SARIF, CI and pipes skip automatic checks. Opt out with --no-update-check or MCPSENSE_NO_UPDATE_CHECK=1. Notices never install automatically.

Historical audits and earlier release evidence

Published 0.4.5: npm and Go deliver verified command updates and terminal update notices. A guarded Node-only global npm hook repairs an identified older Go executable taking precedence on PATH, preserving it as a backup. Use mcpsense update --check to inspect availability and mcpsense update to install deliberately. The release record identifies the published artifacts and public user verification; the implementation verification preserves development evidence.

Published 0.4.4: npm and Go deliver shared metadata trust analysis addressing the reproduced context, value-identity and control-effect failures. The release record identifies the published artifacts; the verification record preserves failed intermediate evaluations and the complete native/npm rerun. All 718 frozen observations per route pass the mandatory boundary gate; reaching analysis capacity requires manual review. These are bounded regression results, not universal protection. Rerun your preferred installation command to update an older package.

Verification history: the beginner/expert retest exposed first-run gaps, missed attack paraphrases, unexamined metadata fields and source-analysis false alarms. Follow-up fixes and their measured limits are tracked in the release-blocker report. The published-version user retest records fresh installation and complete product journeys. Earlier corpus scores and corrected regressions do not establish general detection reliability.

Preserved 0.4.2 audit: the 27 October audit of public 0.4.2 missed 11 of 16 newly authored hostile descriptions and falsely flagged two benign descriptions, identically through npm and native Go. Version 0.4.3 corrects these reproduced cases involving credential relays, monitoring changes, reporting integrity and quoted/negated text. This is a targeted audit, not a field-accuracy estimate. A clean scan must not be treated as authorization to trust a server.

0.4.3 release history: this version introduced bounded source/transform/destination tracking, safeguard-state checks, corrected negation/literal-query scope and explicit advisory-source conflicts. See its release record and the 28 October investigation for historical results and limits.

Preserved 0.4.3 product-test failures: the 31 October audit passed existing workflows but missed 15 of 24 newly authored hostile descriptions in at least one supported metadata field and falsely flagged six of 24 benign controls. Native Go and npm agreed; representative failures also reproduced through live discovery. These targeted results are not a field-accuracy estimate. A reviewed baseline detects subsequent changes, not initial safety.

Start safely

Choose one installation route for a published release:

# npm: Node.js 22+; no Go compiler required

npm install -g mcpsense@latest

Go users: no Node.js/npm required

go install github.com/fayzkk889/MCPSense/cmd/mcpsense@latest

For a first offline walkthrough, open an empty project directory and run:

mcpsense init --example

mcpsense scan ./mcp.json --offline --no-baseline

This creates a synthetic example manifest and refuses to overwrite an existing mcp.json. It does not connect to or configure your real MCP server. For a real inspection, replace the target path with your existing manifest or client MCP configuration. mcpsense init without --example creates scanner settings; it does not create a scan target.

Check installation with mcpsense version and mcpsense --help. mcpsense version --check contacts only GitHub/npm for published-version metadata and prints both versions, channel disagreement, and update commands. It never installs automatically. Version 0.4.5 adds the interactive notices described above. Offline scans do not perform version lookups. An installed development preview can be newer than the published stable release.

Use MCPSense from your assistant (0.5.0+)

For desktop VS Code, open the project-scoped setup to review the server configuration in the editor.

MCPSense 0.5.0 adds an MCP interface to the same CLI engine. Earlier 0.4.5 installations do not include it; check mcpsense version and public availability before connecting. See the MCP setup guide for supported clients, permissions, and natural-language scan examples. CLI and MCP ship together; an installed MCPSense update updates both, and restarting the MCP connection loads the new engine.

Share a scan outcome

If you try MCPSense, share a short scan outcome. Tell us whether you tried the demo, scanned your own integration, ran it again after a change, or hit a blocker. GitHub posts your response publicly. Keep configurations, reports, server URLs, and credentials on your device.

From a source checkout

From this checkout, with Go 1.22 or newer:

go run ./cmd/mcpsense scan ./testdata/compliant_server/manifest.json --offline --no-baseline

Build for repeated use:

# Linux/macOS

go build -o bin/mcpsense ./cmd/mcpsense ./bin/mcpsense scan ./manifest.json --offline --no-baseline

# Windows

go build -o bin/mcpsense.exe ./cmd/mcpsense .\bin\mcpsense.exe scan .\manifest.json --offline --no-baseline

Since 0.4.0, the npm package bundles the same Go scanning engine compiled to WebAssembly. It runs inside Node.js 22+ on Windows, Linux and macOS. Installing it needs no Go compiler, platform archive utility, postinstall download or MCPSense native executable. Go users keep the independent native source-install route. Use @latest for the newest published version. If reproducibility requires an exact version, select one from the public release list and confirm it with mcpsense version.

Windows installation

On Windows, the npm package needs Node.js 22+ and npm only. It bundles WebAssembly and JavaScript rather than an unsigned MCPSense .exe. The separate Go route needs Go 1.22 or newer only. The optional standalone PowerShell installer below is a convenience for Go users: it builds from source, verifies startup, installs without administrator privileges, and adds its directory to your user PATH. No installation route changes Windows protection settings. Device policies can restrict Node.js, scripts or native programs; no universal warning-free guarantee is made.

Earlier unsigned candidates and the published 0.3.0 npm executable were blocked by local Code Integrity policy. The new npm architecture removes that executable from delivery, without waiting for a signing certificate. Its offline installation, Windows command shim and installed user workflows are checked separately from native archives; see the npm runtime verification record. Native Windows archives remain unsigned and their signing work remains open; ZIP packaging or installing Go does not supply a publisher signature. See the earlier Windows readiness record.

From a downloaded or cloned checkout:

# Latest published version

.\install.ps1

Preview an authorized exact commit without changing PATH

.\install.ps1 -Version -InstallDir C:\dev\mcpsense-preview -NoPathUpdate

Update the owning installation with mcpsense update, or rerun npm install -g mcpsense@latest / the Go install command. Package users do not need an npm account. The npm package supports Windows/Linux/macOS x64/arm64 where Node.js 22+ is available. Existing npm users on Node.js 14–21 must update Node.js for this package. NVM is optional; npm never installs a second language toolchain.

On Linux/macOS, sh install.sh installs the latest published release into ~/.local/bin, verifies its SHA-256 manifest before installation and checks startup. Set MCPSENSE_VERSION only when selecting a specific published version; MCPSENSE_INSTALL_DIR selects a writable directory. Add that directory to PATH when instructed. No automatic sudo or Windows-binary fallback is used. Go1.22 is the source language-compatibility floor; use a current patched Go compiler for native installations.

Scope and permissions

SelectionBehavior

| Auto directory | Reads supported source, recognized MCP JSON/conf

Only the beginning is shown; read the rest in the repo