What's Inherited
NPM · WHATS-INHERITED-MCP · SCANNED SEP 20
What a checkout tells your agent to do: instruction files, hooks, declared MCP servers.
Available components
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 Security98
- 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
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 49 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- 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 Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
How do I install the What's Inherited MCP server?
What's Inherited runs locally as an npm package, launched with npx -y whats-inherited-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 · whats-inherited-mcp
claude mcp add stcmain-whats-inherited-mcp -- npx -y whats-inherited-mcp
{
"mcpServers": {
"stcmain-whats-inherited-mcp": {
"command": "npx",
"args": [
"-y",
"whats-inherited-mcp"
]
}
}
} {
"servers": {
"stcmain-whats-inherited-mcp": {
"command": "npx",
"args": [
"-y",
"whats-inherited-mcp"
]
}
}
} codex mcp add stcmain-whats-inherited-mcp -- npx -y whats-inherited-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"stcmain-whats-inherited-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"whats-inherited-mcp"
],
"enabled": true
}
}
} openclaw mcp add stcmain-whats-inherited-mcp --command npx --arg -y --arg whats-inherited-mcp
mcp_servers:
stcmain-whats-inherited-mcp:
command: "npx"
args: ["-y", "whats-inherited-mcp"] {
"McpServers": {
"stcmain-whats-inherited-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"whats-inherited-mcp"
]
}
}
} assistant mcp add stcmain-whats-inherited-mcp -t stdio -c npx -a -y whats-inherited-mcp
{
"mcpServers": {
"stcmain-whats-inherited-mcp": {
"command": "npx",
"args": [
"-y",
"whats-inherited-mcp"
]
}
}
} 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 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 −3
- Stability: pass → 0.77 functional
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 20 Sept 2026 · Analysed npm/whats-inherited-mcp@0.1.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
agent_extensions Skills, commands and subagents the repo ships ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Absolute 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 Commands this checkout wires to agent events ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Absolute 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 MCP servers this checkout declares ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Absolute 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 What this checkout hands your agent ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Absolute 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 Files that instruct the agent ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Absolute 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.
What is the What's Inherited MCP server?
What's Inherited is an MCP server listed in the public MCP registry as io.github.stcmain/whats-inherited-mcp. What a checkout tells your agent to do: instruction files, hooks, declared MCP servers. This page covers its npm package (whats-inherited-mcp).
Is the What's Inherited MCP server safe to use?
What's Inherited scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 What's Inherited MCP server expose?
What's Inherited exposes 5 tools: inherited_summary, instruction_files, auto_run_commands, declared_mcp_servers, agent_extensions. Their descriptions and schemas cost roughly 506 tokens of context every time the server is loaded.
Is the What's Inherited MCP server still maintained?
What's Inherited is still listed as active in the MCP registry. We last reached this channel on 20 September 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 What's Inherited MCP server under?
What's Inherited declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.