io.github.vola-trebla/tsconfig-inheritance-flattener-mcp
NPM · TSCONFIG-INHERITANCE-FLATTENER-MCP · SCANNED SEP 20
Resolves TypeScript config inheritance chains and returns effective compiler options per file.
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 122 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- 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 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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 io.github.vola-trebla/tsconfig-inheritance-flattener-mcp server?
io.github.vola-trebla/tsconfig-inheritance-flattener-mcp runs locally as an npm package, launched with npx -y tsconfig-inheritance-flattener-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 · tsconfig-inheritance-flattener-mcp
claude mcp add vola-trebla-tsconfig-inheritance-flattener-mcp -- npx -y tsconfig-inheritance-flattener-mcp
{
"mcpServers": {
"vola-trebla-tsconfig-inheritance-flattener-mcp": {
"command": "npx",
"args": [
"-y",
"tsconfig-inheritance-flattener-mcp"
]
}
}
} {
"servers": {
"vola-trebla-tsconfig-inheritance-flattener-mcp": {
"command": "npx",
"args": [
"-y",
"tsconfig-inheritance-flattener-mcp"
]
}
}
} codex mcp add vola-trebla-tsconfig-inheritance-flattener-mcp -- npx -y tsconfig-inheritance-flattener-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vola-trebla-tsconfig-inheritance-flattener-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"tsconfig-inheritance-flattener-mcp"
],
"enabled": true
}
}
} openclaw mcp add vola-trebla-tsconfig-inheritance-flattener-mcp --command npx --arg -y --arg tsconfig-inheritance-flattener-mcp
mcp_servers:
vola-trebla-tsconfig-inheritance-flattener-mcp:
command: "npx"
args: ["-y", "tsconfig-inheritance-flattener-mcp"] {
"McpServers": {
"vola-trebla-tsconfig-inheritance-flattener-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"tsconfig-inheritance-flattener-mcp"
]
}
}
} assistant mcp add vola-trebla-tsconfig-inheritance-flattener-mcp -t stdio -c npx -a -y tsconfig-inheritance-flattener-mcp
{
"mcpServers": {
"vola-trebla-tsconfig-inheritance-flattener-mcp": {
"command": "npx",
"args": [
"-y",
"tsconfig-inheritance-flattener-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.
- 9 Sept 26 −3
- Stability: pass → 0.80 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/tsconfig-inheritance-flattener-mcp@0.2.0
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| configPath | string | yes | Absolute 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.
| Name | Type | Req | Description |
|---|---|---|---|
| configPaths | array | yes | Two 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.
| Name | Type | Req | Description |
|---|---|---|---|
| configPath | string | yes | Absolute 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.
| Name | Type | Req | Description |
|---|---|---|---|
| configPath | string | yes | Absolute path to the tsconfig.json file to resolve, e.g. /project/tsconfig.json |
| includeRaw | boolean | – | If 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.
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | yes | The import alias to resolve, e.g. @/hooks/useAuth or ~lib/helpers |
| configPath | string | yes | Absolute 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.
| Name | Type | Req | Description |
|---|---|---|---|
| configPath | string | yes | Absolute path to the tsconfig.json to use for resolution settings |
| containingFile | string | yes | Absolute path to the source file that contains the import |
| moduleName | string | yes | The import specifier to resolve, e.g. ./utils/helpers or @/components/Button |
No output schema declared.
No examples provided.
What is the io.github.vola-trebla/tsconfig-inheritance-flattener-mcp server?
io.github.vola-trebla/tsconfig-inheritance-flattener-mcp is listed in the public MCP registry as io.github.vola-trebla/tsconfig-inheritance-flattener-mcp. Resolves TypeScript config inheritance chains and returns effective compiler options per file. This page covers its npm package (tsconfig-inheritance-flattener-mcp).
Is the io.github.vola-trebla/tsconfig-inheritance-flattener-mcp server safe to use?
io.github.vola-trebla/tsconfig-inheritance-flattener-mcp 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 io.github.vola-trebla/tsconfig-inheritance-flattener-mcp server expose?
io.github.vola-trebla/tsconfig-inheritance-flattener-mcp exposes 6 tools: get_effective_compiler_options, resolve_module_alias, analyze_project_references, explain_emission_structure, simulate_module_resolution, detect_config_overlaps. Their descriptions and schemas cost roughly 590 tokens of context every time the server is loaded.
Is the io.github.vola-trebla/tsconfig-inheritance-flattener-mcp server still maintained?
io.github.vola-trebla/tsconfig-inheritance-flattener-mcp 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 io.github.vola-trebla/tsconfig-inheritance-flattener-mcp server under?
io.github.vola-trebla/tsconfig-inheritance-flattener-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.