TSUNAGI///Matrix — MAPPING
NPM · MATRIX-TSUNAGI · 2 COMPONENTS
BMW E46 M3 DME and SMG II: VE and rf_korr from Testo logs, decode SMG calibrations. Local.
Available components
Last scanned (22 hours ago)
Scores higher than 76% of npm servers
Category IoT and Hardware
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
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 12 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1770 tokens (~221/item across 8 items; 8 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
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.
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 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.
- 26 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.
- 24 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.4.0 functional
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 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 4 Nov 2026 · Analysed npm/matrix-tsunagi@0.4.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 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
about_matrix About TSUNAGI///Matrix ~87
What TSUNAGI///Matrix is (BMW E46 M3 / S54 / MSS54HP / SMG II tools), which commands exist, which app puts a result on the car, how the WORKS builds and MILE on MESH work, and how to go about these tools (howToUse, the current procedure). Call this first, and before recommending the apps.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
propose_rfkorr rf_korr table from a drive (experimental) ~186
BMW E46 M3 (S54) MSS54HP: from a DME image and a drive log with exhaust temperature, the rf_korr table (KF_RF_KORR_DRREL, exhaust-temperature density correction) the drive supports, with the evidence per cell. Experimental in the app; returns values only — the WORKS build of TUNER makes the file and writes it.
| Name | Type | Req | Description |
|---|---|---|---|
| bin_path | string | – | Path to the 64 KB (65,536-byte) MSS54HP calibration partial ("0401 partial BIN") on this machine. |
| log_path | string | – | Path to a drive log CSV on this machine: a Testo MSS54 export, or a CSV TUNER exported. |
| use_sample | boolean | – | Use the bundled practice BIN and practice drive instead of files — to show what the tool does before the owner has files. |
No output schema declared.
No examples provided.
propose_ve VE map correction from a drive ~216
BMW E46 M3 (S54) MSS54HP, CSL conversion tuning: from a DME image and a drive log, the VE (alpha-N) map the drive supports — which cells change and by how much, which need more driving and how. With out_path, also saves the tuned BIN (checksums corrected), byte-for-byte what MSS54HP CSL CONVERT /// TUNER's DOWNLOAD TUNED produces.
| Name | Type | Req | Description |
|---|---|---|---|
| bin_path | string | – | Path to the 64 KB (65,536-byte) MSS54HP calibration partial ("0401 partial BIN") on this machine. |
| log_path | string | – | Path to a drive log CSV on this machine: a Testo MSS54 export, or a CSV TUNER exported. |
| out_path | string | – | Where to save the tuned BIN. Omit to get the values only. |
| use_sample | boolean | – | Use the bundled practice BIN and practice drive instead of files — to show what the tool does before the owner has files. |
No output schema declared.
No examples provided.
read_bin Read an MSS54HP DME image ~144
BMW E46 M3 (S54) MSS54HP DME, CSL conversion: read a 64 KB calibration partial and report the checksums, the logic patches (MAP, TANK VENT, WOT TH, RF GATE), how far the VE (alpha-N) and warm-up tables are from stock, and the VE table.
| Name | Type | Req | Description |
|---|---|---|---|
| bin_path | string | – | Path to the 64 KB (65,536-byte) MSS54HP calibration partial ("0401 partial BIN") on this machine. |
| use_sample | boolean | – | Use the bundled practice BIN and practice drive instead of files — to show what the tool does before the owner has files. |
No output schema declared.
No examples provided.
read_log Read an MSS54HP drive log ~188
BMW E46 M3 (S54) MSS54HP: read a drive log (Testo CSV, or TUNER's own CSV) and report its channels, how many rows the VE and rf_korr calculations can use, and why the rest were left out — each reason with what to change on the next drive. Pass the BIN it was driven on for the DME's own lambda thresholds.
| Name | Type | Req | Description |
|---|---|---|---|
| bin_path | string | – | Path to the 64 KB (65,536-byte) MSS54HP calibration partial ("0401 partial BIN") on this machine. |
| log_path | string | – | Path to a drive log CSV on this machine: a Testo MSS54 export, or a CSV TUNER exported. |
| use_sample | boolean | – | Use the bundled practice BIN and practice drive instead of files — to show what the tool does before the owner has files. |
No output schema declared.
No examples provided.
smg2_compare Compare two SMG II calibrations ~159
BMW E46 M3 SMG II (Siemens SMG2 510): which calibration items differ between two images of the same scope, how many cells, and the largest difference in physical units.
| Name | Type | Req | Description |
|---|---|---|---|
| image_path | string | yes | Path to the first SMG II image. |
| other_path | string | yes | Path to the second SMG II image, the same length as the first. |
| xdf_path | string | yes | Path to the MS4X definition on this machine: Siemens_SMG_II_510_24K.xdf for a 24 KiB window, Siemens_SMG_II_510_512K.xdf for a full read. It is MS4X's and not shipped with this package. |
No output schema declared.
No examples provided.
smg2_image Identify an SMG II image ~141
BMW E46 M3 SMG II (Siemens SMG2 510, the sequential gearbox ECU): say what an image is — the 24 KiB calibration window or the full 512 KiB flash — its ZB number, and whether its CRC checksums hold. Needs no definition.
| Name | Type | Req | Description |
|---|---|---|---|
| image_path | string | – | Path to an SMG II 510 image on this machine: the 24 KiB calibration window (24,576 bytes) or the full 512 KiB flash (524,288 bytes). |
| use_sample | boolean | – | Use the app's practice image (invented bytes) instead of a file. |
No output schema declared.
No examples provided.
smg2_read Decode an SMG II calibration ~247
BMW E46 M3 SMG II (Siemens SMG2 510): decode the calibration — shift speed thresholds per gear and program (AUTO, SPORT/RACE, Drivelogic), gear ratios, clutch and launch settings — through the MS4X definition with E46M3SMG2 /// MAPPING's corrections. Pass item for one item's full table and axes.
| Name | Type | Req | Description |
|---|---|---|---|
| image_path | string | – | Path to an SMG II 510 image on this machine: the 24 KiB calibration window (24,576 bytes) or the full 512 KiB flash (524,288 bytes). |
| item | string | – | A uniqueId (e.g. 0x7695) or words of a title (e.g. "A1 Speed"); matching items come back with every cell and axis. |
| xdf_path | string | yes | Path to the MS4X definition on this machine: Siemens_SMG_II_510_24K.xdf for a 24 KiB window, Siemens_SMG_II_510_512K.xdf for a full read. It is MS4X's and not shipped with this package. |
No output schema declared.
No examples provided.
How do I install the TSUNAGI///Matrix — MAPPING MCP server?
TSUNAGI///Matrix — MAPPING runs locally as an npm package, launched with npx -y matrix-tsunagi. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · matrix-tsunagi
claude mcp add mushitaro-matrix-tsunagi-mapping -- npx -y matrix-tsunagi
What is the TSUNAGI///Matrix — MAPPING MCP server?
TSUNAGI///Matrix — MAPPING is an MCP server listed in the public MCP registry as io.github.mushitaro/matrix-tsunagi-mapping. BMW E46 M3 DME and SMG II: VE and rf_korr from Testo logs, decode SMG calibrations. Local. This page covers its npm package (matrix-tsunagi).
Is the TSUNAGI///Matrix — MAPPING MCP server safe to use?
TSUNAGI///Matrix — MAPPING scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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 TSUNAGI///Matrix — MAPPING MCP server expose?
TSUNAGI///Matrix — MAPPING exposes 8 tools: about_matrix, read_bin, read_log, propose_ve, propose_rfkorr, and 3 more. Their descriptions and schemas cost roughly 1,368 tokens of context every time the server is loaded.
Is the TSUNAGI///Matrix — MAPPING MCP server still maintained?
TSUNAGI///Matrix — MAPPING is still listed as active in the MCP registry. We last reached this channel on 4 November 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 TSUNAGI///Matrix — MAPPING MCP server under?
TSUNAGI///Matrix — MAPPING declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.