TRIZ
NPM · TRIZ-MCP · SCANNED OCT 4
Deterministic, read-only TRIZ knowledge: parameters, principles, matrix, tool routing, effects.
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 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- 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 47 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 701 tokens (~63/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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 TRIZ MCP server?
TRIZ runs locally as an npm package, launched with npx -y triz-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 · triz-mcp
claude mcp add sv-triz -- npx -y triz-mcp
{
"mcpServers": {
"sv-triz": {
"command": "npx",
"args": [
"-y",
"triz-mcp"
]
}
}
} {
"servers": {
"sv-triz": {
"command": "npx",
"args": [
"-y",
"triz-mcp"
]
}
}
} codex mcp add sv-triz -- npx -y triz-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sv-triz": {
"type": "local",
"command": [
"npx",
"-y",
"triz-mcp"
],
"enabled": true
}
}
} openclaw mcp add sv-triz --command npx --arg -y --arg triz-mcp
mcp_servers:
sv-triz:
command: "npx"
args: ["-y", "triz-mcp"] {
"McpServers": {
"sv-triz": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"triz-mcp"
]
}
}
} assistant mcp add sv-triz -t stdio -c npx -a -y triz-mcp
{
"mcpServers": {
"sv-triz": {
"command": "npx",
"args": [
"-y",
"triz-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.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 −3
- Stability: pass → 0.80 functional
- 1 Oct 26 +1
- Stability: 0.97 → pass security
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
- Stability: 0.97 → pass security
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 4 Oct 2026 · Analysed npm/triz-mcp@0.3.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 92 packages
| Packages resolved | 92 |
|---|---|
| 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 →
triz_effects ~108
Search the curated effects database by required function (e.g. 'convert temperature difference into voltage', 'store heat', 'sense strain') or list by category: physical, chemical, geometric. Effects are classical textbook phenomena; selecting and substantiating one remains a synthesis step, never a lookup verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Restrict results to one category |
| query | string | – | Function keywords to search for, e.g. 'store heat' or 'sense magnetic field' |
No output schema declared.
No examples provided.
triz_evals ~25
Return the domain-neutral TRIZ lookup regressions and cross-domain reasoning cases.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
triz_graph ~51
Optional project extension: analyse an OTSM Network of Problems (contradiction graph) and its verifier-backed purpose gates. Requires a project graph via TRIZ_GRAPH; not part of the neutral skill core.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
triz_matrix ~64
Look up the canonical contradiction matrix for an improving and worsening engineering parameter. Blank and diagonal cells fail closed; never guess a recommendation.
| Name | Type | Req | Description |
|---|---|---|---|
| improving | integer | yes | Parameter to improve (1-39) |
| worsening | integer | yes | Parameter that worsens (1-39) |
No output schema declared.
No examples provided.
triz_matrix_multi ~124
Multi-parameter contradiction lookup: every (improving x worsening) matrix cell with the principles aggregated by how many cells recommend each (ties broken by mean position). Use when a conflict involves several parameters on either side; per-cell detail is returned so nothing is hidden. All-blank or diagonal-only results fail closed like triz_matrix.
| Name | Type | Req | Description |
|---|---|---|---|
| improving | array | yes | Parameters to improve (1-39), e.g. [9, 14] |
| worsening | array | yes | Parameters that worsen (1-39), e.g. [25, 33] |
No output schema declared.
No examples provided.
triz_parameter ~48
Get a canonical TRIZ engineering parameter (1-39). Omit id to list all 39.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | – | Parameter number 1-39; omit to list all |
No output schema declared.
No examples provided.
triz_principle ~61
Get a canonical TRIZ inventive principle (1-40). Omit id to list all 40. Look up principle numbers instead of recalling them from memory.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | – | Principle number 1-40; omit to list all |
No output schema declared.
No examples provided.
triz_purpose ~50
Optional project extension: inspect the invariant and purpose gate for one contradiction node of the project graph.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Node id as used in the project graph, e.g. S1 |
No output schema declared.
No examples provided.
triz_resolve ~63
Look up a contradiction-matrix cell and expand its recommended principles and both engineering parameters. Fails closed on blank cells.
| Name | Type | Req | Description |
|---|---|---|---|
| improving | integer | yes | Parameter to improve (1-39) |
| worsening | integer | yes | Parameter that worsens (1-39) |
No output schema declared.
No examples provided.
triz_route ~65
Route a problem stage and optional observable signals to candidate TRIZ tools. Routing is deterministic and returns only tools registered for that stage.
| Name | Type | Req | Description |
|---|---|---|---|
| signals | array | – | Problem signals such as bottleneck, stakeholder conflict, or harmful interaction |
| stage | string | yes | Current workflow stage |
No output schema declared.
No examples provided.
triz_tool_catalog ~42
List the domain-neutral TRIZ tool catalog, optionally restricted to problem analysis, task modeling, or solution synthesis.
| Name | Type | Req | Description |
|---|---|---|---|
| stage | string | – | Optional workflow stage |
No output schema declared.
No examples provided.
What is the TRIZ MCP server?
TRIZ is an MCP server listed in the public MCP registry as io.github.sv/triz. Deterministic, read-only TRIZ knowledge: parameters, principles, matrix, tool routing, effects. This page covers its npm package (triz-mcp).
Is the TRIZ MCP server safe to use?
TRIZ scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 October 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 TRIZ MCP server expose?
TRIZ exposes 11 tools: triz_parameter, triz_principle, triz_matrix, triz_matrix_multi, triz_resolve, and 6 more. Their descriptions and schemas cost roughly 701 tokens of context every time the server is loaded.
Is the TRIZ MCP server still maintained?
TRIZ is still listed as active in the MCP registry. We last reached this channel on 4 October 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 TRIZ MCP server under?
TRIZ declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.