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 · SCANNED AUG 12

Read-only local zoxide diagnostics for MCP clients.

Available components

npm · @agoes/zoxide-doctor-mcp 80
80 Trust /100
Trust breakdown (6 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 →

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 2 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

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

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @agoes/zoxide-doctor-mcp

# add to Claude Code
claude mcp add jiankn-zoxide-doctor -- npx -y @agoes/zoxide-doctor-mcp
# add to Codex CLI
codex mcp add jiankn-zoxide-doctor -- npx -y @agoes/zoxide-doctor-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jiankn-zoxide-doctor": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@agoes/zoxide-doctor-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add jiankn-zoxide-doctor --command npx --arg -y --arg @agoes/zoxide-doctor-mcp
# ~/.hermes/config.yaml
mcp_servers:
  jiankn-zoxide-doctor:
    command: "npx"
    args: ["-y", "@agoes/zoxide-doctor-mcp"]
// mcp.json
{
  "mcpServers": {
    "jiankn-zoxide-doctor": {
      "command": "npx",
      "args": [
        "-y",
        "@agoes/zoxide-doctor-mcp"
      ]
    }
  }
}
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.

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 9 Aug 26 80

    First indexed and scored.

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 12 Aug 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 https://slsa.dev/provenance/v1
Subject digest sha512:73e051620da4516075f946227f18065bcae1a1133a6cbd4372051f3fe084dd2d5a62990ca7a974a5c430a6baec81ddc9d71272d5eee47dd2dc0351045
Dependencies 4 packages
Packages resolved 4
Tree resolution Complete
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.

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.