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.

io.github.vola-trebla/tsconfig-inheritance-flattener-mcp

NPM · TSCONFIG-INHERITANCE-FLATTENER-MCP · SCANNED AUG 3

Resolves TypeScript config inheritance chains and returns effective compiler options per file.

+24 this week 70 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 Usability83
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 590 tokens (~98/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 · tsconfig-inheritance-flattener-mcp

# add to Claude Code
claude mcp add vola-trebla-tsconfig-inheritance-flattener-mcp -- npx -y tsconfig-inheritance-flattener-mcp
# add to Codex CLI
codex mcp add vola-trebla-tsconfig-inheritance-flattener-mcp -- npx -y tsconfig-inheritance-flattener-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vola-trebla-tsconfig-inheritance-flattener-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "tsconfig-inheritance-flattener-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add vola-trebla-tsconfig-inheritance-flattener-mcp --command npx --arg -y --arg tsconfig-inheritance-flattener-mcp
# ~/.hermes/config.yaml
mcp_servers:
  vola-trebla-tsconfig-inheritance-flattener-mcp:
    command: "npx"
    args: ["-y", "tsconfig-inheritance-flattener-mcp"]
// mcp.json
{
  "mcpServers": {
    "vola-trebla-tsconfig-inheritance-flattener-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tsconfig-inheritance-flattener-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 +65
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Dependency health: unverified → partial functional
    • Stability: unverified → 0.20 functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Schema quality: unverified → excellent functional
    • License: unverified → pass functional
    • Tool coverage: unverified → 100 functional
    • Licence: MIT functional
  • 31 Jul 26 −41
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 46

    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 · 94 deprecated · 29 stale.

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

MCP tools — 6 exposed · ~590 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
analyze_project_references ~71

Inspect a tsconfig.json's project references array and validate that each referenced package has composite:true enabled. Detects missing or broken cross-package references in TypeScript monorepos that would cause silent build failures.

NameTypeReqDescription
configPathstringyesAbsolute path to the tsconfig.json to analyze for project references

No output schema declared.

No examples provided.

detect_config_overlaps ~82

Find source files compiled by more than one tsconfig simultaneously and surface option conflicts (strict, module, target, etc.) between them. Essential for monorepos where tsconfig.app.json and tsconfig.spec.json share the same src/ tree with incompatible settings.

NameTypeReqDescription
configPathsarrayyesTwo or more absolute paths to tsconfig.json files to compare

No output schema declared.

No examples provided.

explain_emission_structure ~85

Build a virtual tree of what TypeScript will emit for each source file — compiled JS, declaration (.d.ts), and source map paths — without running the compiler. Useful when an agent needs to predict where output files will land or debug rootDir/outDir misconfigurations.

NameTypeReqDescription
configPathstringyesAbsolute path to the tsconfig.json to analyze for emission structure

No output schema declared.

No examples provided.

get_effective_compiler_options ~115

Resolve the full tsconfig.json inheritance chain and return the final merged compiler options that actually apply — including options inherited from extended base configs in node_modules or monorepo packages. Eliminates agent hallucinations about strict mode, moduleResolution, paths, and target.

NameTypeReqDescription
configPathstringyesAbsolute path to the tsconfig.json file to resolve, e.g. /project/tsconfig.json
includeRawbooleanIf true, also return the raw per-file options before merging. Default false.

No output schema declared.

No examples provided.

resolve_module_alias ~110

Map a TypeScript path alias (e.g. @/components/Button or @utils/format) to its physical file location on disk, using the paths and baseUrl from the resolved tsconfig. Useful when an agent needs to navigate to the actual file behind an import.

NameTypeReqDescription
aliasstringyesThe import alias to resolve, e.g. @/hooks/useAuth or ~lib/helpers
configPathstringyesAbsolute path to the tsconfig.json whose paths config should be used

No output schema declared.

No examples provided.

simulate_module_resolution ~127

Run TypeScript's exact module resolution algorithm for a given import and return the resolved file path plus every candidate path that was tried and rejected. Eliminates guesswork about why an import resolves (or fails to resolve) under Node16/NodeNext/Bundler strategies.

NameTypeReqDescription
configPathstringyesAbsolute path to the tsconfig.json to use for resolution settings
containingFilestringyesAbsolute path to the source file that contains the import
moduleNamestringyesThe import specifier to resolve, e.g. ./utils/helpers or @/components/Button

No output schema declared.

No examples provided.