What a checkout tells your agent to do: instruction files, hooks, declared MCP servers.
MCPpedia last refreshed this data
io.github.stcmain/whats-inherited-mcp is an MCP server that what a checkout tells your agent to do: instruction files, hooks, declared MCP servers. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 59/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"whats-inherited": {
"args": [
"-y",
"whats-inherited-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
You review the code you clone. Almost nobody reviews the part of it that talks to your agent. An MCP server that enumerates everything in a checkout addressed to an AI agent rather than to you: instruction files, hook commands wired to agent events, MCP servers the repo declares, and the skills and subagents it ships.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'whats-inherited-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked whats-inherited-mcp against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ecommerce
Девять российских маркетплейсов и китайский Taobao как MCP-серверы: Wildberries, Ozon, Яндекс Маркет, Детский мир, Авито, Мегамаркет, Lamoda, DNS, Ситилинк. Плюс сравнение цен по всем сразу. Только чтение, ключи не нужны.
Monetize any MCP server: x402 paywall, pay-per-call billing in USDC on Base, agent marketplace.
MCP server for the Shopify Admin API: products, orders, customers, inventory, discounts.
MCP server for Salesforce B2C Commerce Cloud development assistance
MCP Security Weekly
Get CVE alerts and security updates for io.github.stcmain/whats-inherited-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
You review the code you clone. Almost nobody reviews the part of it that talks to your agent. An MCP server that enumerates everything in a checkout addressed to an AI agent rather than to you: instruction files, hook commands wired to agent events, MCP servers the repo declares, and the skills and subagents it ships.
git diff shows you code, and you read code. It also shows you three added lines in a CLAUDE.md, and you skim those, because they look like documentation. They are not documentation — they are instructions your model will follow.
The surface is bigger than most people picture. A directory you cloned can carry:
CLAUDE.md / AGENTS.md / .cursorrules — loaded into context and treated as instructions, including nested copies deep in the tree that only apply when the agent works in that subdirectory.claude/settings.json — shell wired to fire on tool use, session start, or prompt submit.mcp.json — MCP servers the repo asks to add, often launched with npx -y <package>, which means the code that runs is downloaded at start time and is not the code you reviewed.claude/skills, .claude/commands, .claude/agents — capabilities the repo hands the agentNothing collects that in one place. This does.
Run against a checkout of langfuse/langfuse at 7d2afa4 — an ordinary, reputable open-source repo, picked precisely because there is nothing wrong with it:
# Inherited agent surface
**12 item(s) in this checkout are addressed to an agent, not to you.**
| Surface | Count | Detail |
|-------------------------------|------:|--------------------------------------------------------------|
| Instruction files | 12 | ~41,848 est. tokens, 5,593 lines your agent is told to follow |
| Hook commands | 0 | configured to run on agent events |
| MCP servers declared | 0 | 0 fetch code from a registry at launch |
| Skills / commands / subagents | 33 extensions (196 files) | shipped under `.agents/`, available to the agent |
## Worth a look
- 11 instruction file(s) are **not at the repo root** — they apply when the agent
works in those subdirectories and are easy to miss in review.
and instruction_files adds:
> Counted once, reachable under more than one name (symlinks):
> - `AGENTS.md` ← also `.agents/AGENTS.md`, `CLAUDE.md`
Five and a half thousand lines of standing instruction, most of it in files you would never open, in a repo nobody has any reason to distrust. That is the point: the number is large even in the benign case, which is exactly why an unusual entry in it goes unnoticed.
| Tool | What it answers |
|---|---|
inherited_summary | The headline: everything in this checkout addressed to an agent. Start here |
instruction_files | Every CLAUDE.md/AGENTS.md/.cursorrules, its size and token cost, and what its @import lines pull in — including imports that resolve outside the repo |
auto_run_commands | Hook commands the checkout wires to agent events, and whether the script each references is inside the repo, outside it, or missing |
declared_mcp_servers | MCP servers the repo declares, which of them fetch code at launch, and filesystem paths they are granted outside the checkout |
agent_extensions | Skills, slash commands and subagents the repo ships |
Every tool takes an optional dir. When it is omitted the server falls back to
WI_DEFAULT_ROOT if that