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

What's Inherited

NPM · WHATS-INHERITED-MCP · SCANNED AUG 3

What a checkout tells your agent to do: instruction files, hooks, declared MCP servers.

Available components

66 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 Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 506 tokens (~101/item across 5 items; 5 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 · whats-inherited-mcp

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

  • 2 Aug 26 +61
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Dependency health: unverified → partial functional
    • Tool coverage: unverified → 100 functional
    • License: unverified → pass functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • First check of Schema quality: excellent functional
    • First check of Schema quality: pass functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: fail functional
    • Licence: MIT functional
  • 1 Aug 26 5

    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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 95 packages

95 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 5 exposed · ~506 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
agent_extensions ~113

Skills, slash commands, subagent definitions and plugin markers shipped inside the checkout's `.claude/` or `.agents/` directories (root, or one to two levels down — monorepos put them per package). These become available to an agent working in this directory. Counts distinct extensions and the markdown files they carry. Names and sizes only — contents are never returned.

NameTypeReqDescription
dirstringAbsolute path to the checkout to inspect. Defaults to WI_DEFAULT_ROOT if set, otherwise the server's working directory.

No output schema declared.

No examples provided.

auto_run_commands ~99

Hook commands declared in the checkout's .claude/settings.json and settings.local.json — shell commands wired to fire on agent events such as tool use, session start or prompt submit. Shows the command, its trigger, and whether the script it references lives inside the repo, outside it, or is missing.

NameTypeReqDescription
dirstringAbsolute path to the checkout to inspect. Defaults to WI_DEFAULT_ROOT if set, otherwise the server's working directory.

No output schema declared.

No examples provided.

declared_mcp_servers ~94

MCP servers declared by the checkout (.mcp.json and equivalents) — the launch command, whether it fetches code from a package registry at start time, filesystem paths it is granted outside the repo, and the NAMES of environment variables it expects. Values are never read.

NameTypeReqDescription
dirstringAbsolute path to the checkout to inspect. Defaults to WI_DEFAULT_ROOT if set, otherwise the server's working directory.

No output schema declared.

No examples provided.

inherited_summary ~106

Start here. Headline count of everything in a directory that is addressed to an AI agent rather than to you: instruction files, hook commands wired to run automatically, MCP servers the repo declares, and skills/commands/subagents it ships. Use before working in a repo you did not write, or when reviewing a PR that touches agent config.

NameTypeReqDescription
dirstringAbsolute path to the checkout to inspect. Defaults to WI_DEFAULT_ROOT if set, otherwise the server's working directory.

No output schema declared.

No examples provided.

instruction_files ~94

Every CLAUDE.md, AGENTS.md, .cursorrules and equivalent in the checkout, with size, estimated token cost, and what each one's @import lines pull in — including imports that resolve outside the repo. File contents are never returned; open the paths yourself.

NameTypeReqDescription
dirstringAbsolute path to the checkout to inspect. Defaults to WI_DEFAULT_ROOT if set, otherwise the server's working directory.

No output schema declared.

No examples provided.