Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

zoxide-doctor

NPM · @AGOES/ZOXIDE-DOCTOR-MCP

Read-only local zoxide diagnostics for MCP clients.

0 this week 96 Trust /100

Last scanned (19 hours ago)

Scores higher than 98% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

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
  • 0 of 4 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to jiankn/zoxide-doctor-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 103 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 85 tokens (~85/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 19 Nov 26 +1
    • Stability: 0.97 → pass security
  • 18 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 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.

  • 9 Nov 26 −2
    • Stability: pass → 0.90 functional
  • 3 Nov 26 +1
    • Stability: 0.97 → pass security
  • 2 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 27 Oct 26 +1
    • Stability: 0.97 → pass security
Diagnostics

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 Nov 2026 · Analysed npm/@agoes/zoxide-doctor-mcp@0.1.2

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 jiankn/zoxide-doctor-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/jiankn/zoxide-doctor-mcp/.github/workflows/publish.yml@refs/tags/v0.1.2
Rekor log index 2389663911
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:73e051620da4516075f946227f18065bcae1a1133a6cbd4372051f3fe084dd2d5a62990ca7a974a5c430a6baec81ddc9d71272d5eee47dd2dc0351045

Background: How many MCP packages publish verified provenance →

Dependencies 4 packages
Packages resolved 4
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~85 tokens

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 →

Tool Tokens
diagnose_zoxide ~85

Run read-only local diagnostics for zoxide PATH availability, shell initialization, and optional fzf support. Shell profile content is read only when scan_config is true.

NameTypeReqDescription
scan_configboolean–When true, read conventional shell profile paths to check for zoxide initialization. Defaults to false.
shellstring–Shell to diagnose. Omit to use local shell detection.

No output schema declared.

No examples provided.

Install

How do I install the zoxide-doctor MCP server?

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

npm · @agoes/zoxide-doctor-mcp

# add to Claude Code
claude mcp add jiankn-zoxide-doctor -- npx -y @agoes/zoxide-doctor-mcp
Common questions

What is the zoxide-doctor MCP server?

zoxide-doctor is an MCP server listed in the public MCP registry as io.github.jiankn/zoxide-doctor. Read-only local zoxide diagnostics for MCP clients. This page covers its npm package (@agoes/zoxide-doctor-mcp).

Is the zoxide-doctor MCP server safe to use?

zoxide-doctor scores 96 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 zoxide-doctor MCP server expose?

zoxide-doctor exposes 1 tool: diagnose_zoxide. Their descriptions and schemas cost roughly 85 tokens of context every time the server is loaded.

Is the zoxide-doctor MCP server still maintained?

zoxide-doctor 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 zoxide-doctor MCP server under?

zoxide-doctor 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 zoxide-doctor MCP server?

VerifyMCP ran 16 checks on zoxide-doctor, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.