Hoshin Kanri X-Matrix
NPM · HOSHIN-KANRI-MCP · 2 COMPONENTS · SCANNED SEP 20
Strategic memory agents can build, score and keep current: a living X-Matrix with review cadences.
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 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 51 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1847 tokens (~131/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "share_matrix" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 14 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 Hoshin Kanri X-Matrix MCP server?
Hoshin Kanri X-Matrix runs locally as an npm package, launched with npx -y hoshin-kanri-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 · hoshin-kanri-mcp
claude mcp add wellknownmcp-hoshin-kanri -- npx -y hoshin-kanri-mcp
{
"mcpServers": {
"wellknownmcp-hoshin-kanri": {
"command": "npx",
"args": [
"-y",
"hoshin-kanri-mcp"
]
}
}
} {
"servers": {
"wellknownmcp-hoshin-kanri": {
"command": "npx",
"args": [
"-y",
"hoshin-kanri-mcp"
]
}
}
} codex mcp add wellknownmcp-hoshin-kanri -- npx -y hoshin-kanri-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"wellknownmcp-hoshin-kanri": {
"type": "local",
"command": [
"npx",
"-y",
"hoshin-kanri-mcp"
],
"enabled": true
}
}
} openclaw mcp add wellknownmcp-hoshin-kanri --command npx --arg -y --arg hoshin-kanri-mcp
mcp_servers:
wellknownmcp-hoshin-kanri:
command: "npx"
args: ["-y", "hoshin-kanri-mcp"] {
"McpServers": {
"wellknownmcp-hoshin-kanri": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"hoshin-kanri-mcp"
]
}
}
} assistant mcp add wellknownmcp-hoshin-kanri -t stdio -c npx -a -y hoshin-kanri-mcp
{
"mcpServers": {
"wellknownmcp-hoshin-kanri": {
"command": "npx",
"args": [
"-y",
"hoshin-kanri-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.
- 20 Sept 26 −3
- Stability: pass → 0.80 functional
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 18 Sept 26 +1
- Security disclosure: unverified → pass ▲ functional
- 17 Sept 26 0
- Security disclosure: pass → unverified ▼ functional
- 15 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.
- 13 Sept 26 −3
- Stability: pass → 0.80 functional
- 12 Sept 26 +1
- Stability: 0.97 → pass security
- 10 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.
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/hoshin-kanri-mcp@3.0.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 95 packages
| Packages resolved | 95 |
|---|---|
| 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 →
add_idea ~109
Add a new idea to the Hoshin Kanri inbox. Ideas can be strategic initiatives, improvement suggestions, or action items that may later be linked to the X-Matrix.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Detailed description of the idea |
| priority | string | – | Priority level (default: medium) |
| source | string | – | Where this idea originated (default: conversation) |
| tags | array | – | Tags for categorization |
| title | string | yes | Title of the idea (required) |
No output schema declared.
No examples provided.
create_matrix ~156
Create a new X-Matrix. Use this to start a strategy from scratch: create the matrix, then add elements with upsert_element and wire them with set_correlation. The first matrix of an organization becomes the default one.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | What this deployment covers |
| is_default | boolean | – | Make this the default matrix of the organization |
| name | string | yes | Name of the matrix, e.g. "Strategy 2027" (required) |
| period_end | string | – | End of the period, ISO date (YYYY-MM-DD) |
| period_start | string | – | Start of the period, ISO date (YYYY-MM-DD) |
| period_type | string | – | Planning horizon (default: annual) |
No output schema declared.
No examples provided.
diagnose_theme_deployment ~76
Analyze if a strategic theme is properly deployed from vision down to operational meetings. Returns a deployment score, coverage per hierarchy level, and suggestions for improving deployment.
| Name | Type | Req | Description |
|---|---|---|---|
| theme_id | string | – | UUID of the strategic theme to analyze |
| theme_name | string | – | Name of the theme to search for (alternative to theme_id) |
No output schema declared.
No examples provided.
get_management_architecture ~70
Returns the complete management system architecture - all meeting cadences organized by hierarchy level (strategic, tactical, operational_mgmt, team_mgmt, execution). Shows the tree of meetings, their frequency, team scope, tracked quadrants, and how they cascade from strategic reviews down to daily stand-ups.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_matrix_completeness ~159
Analyze X-Matrix completeness and get AI-friendly score. Returns: - Coverage: elements per quadrant (min 3-5 recommended) - Density: correlation fill rate between adjacent quadrants - Orphans: elements without any links - Chains: complete Vision→Objective→Initiative→KPI paths - Indicator Balance: checks if objectives/initiatives have both RESULT (lagging - measures outcomes like revenue, NPS) AND PERFORMANCE (leading - measures process like calls/week, % completion) indicators linked. Ideal state: each objective and initiative should be linked to at least one result indicator AND one performance indicator.
| Name | Type | Req | Description |
|---|---|---|---|
| matrix_id | string | – | UUID of the matrix to analyze (optional, uses default matrix if not provided) |
No output schema declared.
No examples provided.
get_matrix_data ~139
Get the COMPLETE dataset of an X-Matrix in one call: every element of all four quadrants (id, title, status, progress, externalRef, indicator type), all correlations (from/to element ids and titles, strength), and the completeness score. Use this instead of get_matrix_summary when you need the full matrix — typically to render a view or build an interactive artifact (e.g. an X-Matrix cockpit for a leadership meeting, shareable with the team). The matrix_artifact prompt shows the recommended artifact layout.
| Name | Type | Req | Description |
|---|---|---|---|
| matrix_id | string | – | UUID of the matrix (optional, uses the first active matrix if not provided) |
No output schema declared.
No examples provided.
get_matrix_summary ~49
Get a summary of the current X-Matrix state including progress on objectives, key correlations, and attention items.
| Name | Type | Req | Description |
|---|---|---|---|
| include_correlations | boolean | – | Include element correlations in response (default: true) |
No output schema declared.
No examples provided.
list_objectives ~91
List strategic objectives from the X-Matrix. Can filter by quadrant (north=long-term objectives, east=annual objectives, south=actions/projects, west=KPIs).
| Name | Type | Req | Description |
|---|---|---|---|
| quadrant | string | – | Which quadrant to list (default: all). North=strategic, East=annual, South=actions, West=KPIs |
| status | string | – | Filter by status (default: all) |
No output schema declared.
No examples provided.
search_ideas ~91
Search through the ideas inbox with filters for status, priority, tags, or text search.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum results (default: 20) |
| priority | string | – | Filter by priority |
| query | string | – | Text search in title and description |
| status | string | – | Filter by status (default: all) |
| tags | array | – | Filter by tags (any match) |
No output schema declared.
No examples provided.
set_correlation ~149
Wire two elements of adjacent quadrants together, or unwire them with strength "none". Only adjacent pairs carry meaning: north↔east, east↔south, south↔west, north↔west. That constraint is what makes the matrix a deployment tool — a vision reaches a KPI through an objective and an initiative, never directly.
| Name | Type | Req | Description |
|---|---|---|---|
| from_element_id | string | yes | UUID of the first element (required) |
| matrix_id | string | – | UUID of the matrix (default: the organization default matrix) |
| strength | string | yes | How strongly they are linked. "none" removes the correlation. |
| to_element_id | string | yes | UUID of the second element (required) |
No output schema declared.
No examples provided.
share_matrix ~271
Publish a matrix as a public read-only web page and return the tokenized link — or list/revoke existing share links. Publication is a deliberate act: anyone with the link can view the matrix (title, elements, correlations, completeness score) until the link is revoked or expires. The page is never indexed by search engines. Use it to share the X-Matrix with people OUTSIDE the organization (board members, investors, partners) without creating accounts. For sharing inside a claude.ai Team organization, prefer the matrix_artifact prompt instead. Not available in local JSON mode (sovereign mode has no cloud page by design — export a snapshot artifact instead).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | create (default): publish and return the link. list: existing shares with status. revoke: kill a link (requires share_id). |
| expires_in_days | integer | – | Optional auto-expiry in days (default: no expiry, revocable manually) |
| label | string | – | Optional label to remember who this link was created for (e.g. "board Q3") |
| matrix_id | string | – | UUID of the matrix (optional, uses the first active matrix if not provided) |
| share_id | string | – | UUID of the share to revoke (required for action=revoke, from action=list) |
No output schema declared.
No examples provided.
suggest_meeting_for_topic ~76
Recommend the right meeting level and cadence for a given topic based on its nature and the X-Matrix quadrant it relates to.
| Name | Type | Req | Description |
|---|---|---|---|
| element_id | string | – | UUID of the X-Matrix element related to this topic (optional) |
| topic | string | yes | Description of the topic to find the right meeting for (required) |
No output schema declared.
No examples provided.
update_element_status ~110
Update the status or progress of a matrix element (objective, action, or KPI).
| Name | Type | Req | Description |
|---|---|---|---|
| element_id | string | yes | UUID of the element to update |
| external_ref | string | – | Link to the matching project in the execution tool (Linear/Jira URL or ID). Set it once; weekly syncs use it to pull progress. |
| notes | string | – | Update notes or comments |
| progress | integer | – | Progress percentage (0-100) |
| status | string | – | New status |
No output schema declared.
No examples provided.
upsert_element ~301
Create an X-Matrix element, or update one when element_id is given. Quadrants: north = 3-5 year vision, east = annual objectives, south = initiatives, west = KPIs. A west element should carry indicator_type so the completeness score can judge the leading/lagging balance.
| Name | Type | Req | Description |
|---|---|---|---|
| current_value | string | – | Where it stands today, e.g. "31" |
| description | string | – | Longer description, rationale, scope |
| element_id | string | – | UUID of an existing element to update. Omit to create a new one. |
| external_ref | string | – | URL or key of the project implementing this in your execution tool (Linear, Jira, GitHub) |
| indicator_type | string | – | For west elements only: result = lagging (measures outcomes), performance = leading (measures the process producing them). Every objective should be tracked by at least one of each. |
| matrix_id | string | – | UUID of the matrix (default: the organization default matrix) |
| quadrant | string | – | Quadrant of the element (required when creating) |
| status | string | – | Status of the element (default: active) |
| target_value | string | – | Target to reach, e.g. "38" |
| title | string | – | Title of the element (required when creating) |
| unit | string | – | Unit of the values, e.g. "%", "k€", "days" |
No output schema declared.
No examples provided.
What is the Hoshin Kanri X-Matrix MCP server?
Hoshin Kanri X-Matrix is an MCP server listed in the public MCP registry as io.github.wellknownmcp/hoshin-kanri. Strategic memory agents can build, score and keep current: a living X-Matrix with review cadences. This page covers its npm package (hoshin-kanri-mcp).
Is the Hoshin Kanri X-Matrix MCP server safe to use?
Hoshin Kanri X-Matrix scores 82 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 Hoshin Kanri X-Matrix MCP server expose?
Hoshin Kanri X-Matrix exposes 14 tools: add_idea, list_objectives, get_matrix_summary, update_element_status, search_ideas, and 9 more. Their descriptions and schemas cost roughly 1,847 tokens of context every time the server is loaded.
Is the Hoshin Kanri X-Matrix MCP server still maintained?
Hoshin Kanri X-Matrix 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 Hoshin Kanri X-Matrix MCP server under?
Hoshin Kanri X-Matrix declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.