TSUNAGI///Matrix — MAPPING
REMOTE · MATRIX-MCP.TSUNAGI.APP · 2 COMPONENTS
BMW E46 M3 DME and SMG II: VE and rf_korr from Testo logs, decode SMG calibrations. Local.
Available components
Last scanned (7 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
Category IoT and Hardware
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1541 tokens (~192/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 Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 0
- Server version: 0.3.0 → 0.4.0 functional
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 0
- Stability: unverified → 0.03 ▲ 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 5 Nov 2026 · Probed https://matrix-mcp.tsunagi.app/mcp/mapping
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=matrix-mcp.tsunagi.app | CN=WE1,O=Google Trust Services,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | ae58ae31aa72048a133053e1380b9c8f |
| SANs: matrix-mcp.tsunagi.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of matrix-mcp.tsunagi.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| tsunagi.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://matrix-mcp.tsunagi.app/mcp/mapping | Verified | 200 | |
| http (plaintext) | http://matrix-mcp.tsunagi.app/mcp/mapping | HTTPS enforced | 301 | https://matrix-mcp.tsunagi.app/mcp/mapping |
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 ~69
What TSUNAGI///Matrix is (BMW E46 M3 / S54 / MSS54HP / SMG II tools), which calculations exist, which app puts a result on the car, and how the WORKS builds and MILE on MESH work. Call this 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) ~165
BMW E46 M3 (S54) MSS54HP: from a DME image and a drive log with exhaust temperature, the rf_korr table (KF_RF_KORR_DRREL) the drive supports, with the evidence per cell. Experimental in the app; values only — the WORKS build of TUNER makes the file.
| Name | Type | Req | Description |
|---|---|---|---|
| bin_file | object | – | The 64 KB (65,536-byte) MSS54HP calibration partial ("0401 partial BIN"). |
| log_file | object | – | A drive log CSV: a Testo MSS54 export, or a CSV TUNER exported. |
| use_sample | boolean | – | Use the 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 ~173
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. Values only here; the free MSS54HP CSL CONVERT /// TUNER makes the tuned BIN from the same two files.
| Name | Type | Req | Description |
|---|---|---|---|
| bin_file | object | – | The 64 KB (65,536-byte) MSS54HP calibration partial ("0401 partial BIN"). |
| log_file | object | – | A drive log CSV: a Testo MSS54 export, or a CSV TUNER exported. |
| use_sample | boolean | – | Use the 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 ~137
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_file | object | – | The 64 KB (65,536-byte) MSS54HP calibration partial ("0401 partial BIN"). |
| use_sample | boolean | – | Use the 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 ~176
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. Attach the BIN it was driven on for the DME's own lambda thresholds.
| Name | Type | Req | Description |
|---|---|---|---|
| bin_file | object | – | The 64 KB (65,536-byte) MSS54HP calibration partial ("0401 partial BIN"). |
| log_file | object | – | A drive log CSV: a Testo MSS54 export, or a CSV TUNER exported. |
| use_sample | boolean | – | Use the 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 ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| image_file | object | yes | An SMG II 510 image: the 24 KiB calibration window or the 512 KiB full flash. |
| other_file | – | yes | – |
| xdf_file | object | yes | The MS4X definition: Siemens_SMG_II_510_24K.xdf for a window, _512K.xdf for a full read. It is MS4X's and the owner's own. |
No output schema declared.
No examples provided.
smg2_image Identify an SMG II image ~120
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_file | object | – | An SMG II 510 image: the 24 KiB calibration window or the 512 KiB full flash. |
| use_sample | boolean | – | Use the app's practice image (invented bytes). |
No output schema declared.
No examples provided.
smg2_read Decode an SMG II calibration ~193
BMW E46 M3 SMG II (Siemens SMG2 510): decode the calibration — shift speed thresholds per gear and program, gear ratios, clutch and launch settings — through the owner's MS4X definition with E46M3SMG2 /// MAPPING's corrections. Pass item for one item's full table and axes.
| Name | Type | Req | Description |
|---|---|---|---|
| image_file | object | yes | An SMG II 510 image: the 24 KiB calibration window or the 512 KiB full flash. |
| item | string | – | A uniqueId (e.g. 0x7695) or words of a title (e.g. "A1 Speed"). |
| xdf_file | object | yes | The MS4X definition: Siemens_SMG_II_510_24K.xdf for a window, _512K.xdf for a full read. It is MS4X's and the owner's own. |
No output schema declared.
No examples provided.
How do I install the TSUNAGI///Matrix — MAPPING MCP server?
TSUNAGI///Matrix — MAPPING is a hosted endpoint at https://matrix-mcp.tsunagi.app/mcp/mapping, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · matrix-mcp.tsunagi.app
claude mcp add --transport http mushitaro-matrix-tsunagi-mapping 'https://matrix-mcp.tsunagi.app/mcp/mapping'
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 hosted endpoint (https://matrix-mcp.tsunagi.app/mcp/mapping).
Is the TSUNAGI///Matrix — MAPPING MCP server safe to use?
TSUNAGI///Matrix — MAPPING scores 74 out of 100 on VerifyMCP. 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,169 tokens of context every time the server is loaded.
Does the TSUNAGI///Matrix — MAPPING MCP server require authentication?
No. We connected to TSUNAGI///Matrix — MAPPING without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.