why-no-tools
Diagnose why your MCP server shows Connected but no tools appear in Claude Code. Detects npx cold-cache installs that exceed the 30s startup limit.
Description supplied by the publisher; it is a claim, not verified evidence.
- Name
- npm:why-no-tools
- Listed in
- npm registry
- Publisher
- serxav
- Latest version
- 0.1.0
- Published
- 2026-07-05
- Evidence
- Listed only, not analyzed yet
What a full analysis of why-no-tools checks
Not checked yet. About 60 tools are analyzed every hour; each check links to its source when it runs:
- Publisher identity: not checked yet
- Repository ownership: not checked yet
- Organization verification: not checked yet
- Artifact provenance: not checked yet
- Source availability: not checked yet
- Version evidence: not checked yet
- Known vulnerabilities: not checked yet
- Install scripts: not checked yet
- Maintenance: not checked yet
- License: not checked yet
Before you install it
- Open the repository and confirm the account is the one you expect: look-alike names are common.
- Read what it asks for: files, accounts, network access and credentials it needs.
- Prefer a version from a verified publisher when one exists.