matrix-tsunagi-mapping-remote
https://matrix-mcp.tsunagi.app
Registry code: 649cfe7e1aefceb6
TSUNAGI///Matrix is TSUNAGI's family of tools for the BMW E46 M3 (S54, MSS54HP DME, SMG II). https://m3.tsunagi.app
The calculations are open source (MIT) and free. This package runs them on your own machine and sends nothing anywhere.
- endpoint
- https://matrix-mcp.tsunagi.app/mcp/mapping
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is matrix-tsunagi-mapping-remote live?
- Yes — it answered the hub's last check (checked 11h ago). It answered 100% of checks over the last 30 days.
- Is matrix-tsunagi-mapping-remote free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does matrix-tsunagi-mapping-remote have?
- 8 tools: smg2_read, propose_rfkorr, read_bin, smg2_compare, read_log, smg2_image, propose_ve, about_matrix.
- Is matrix-tsunagi-mapping-remote safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 8 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
about_matrix open 11h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linessmg2_read unknown never probed
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "image_file", "xdf_file" ], "properties": { "item": { "type": "string", "description": "A uniqueId (e.g. 0x7695) or words of a title (e.g. \"A1 Speed\")." }, "xdf_file": { "type": "object", "required": [ "download_url", "file_id" ], "properties": { "file_id": { "type": "string" }, "file_name": { "type": "string" }, "mime_type": { "type": "string" }, "download_url": { "type": "string", "description": "Temporary download URL for the file, as the assistant provides it." } }, "description": "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.", "additionalProperties": false }, "image_file": { "type": "object", "required": [ "download_url", "file_id" ], "properties": { "file_id": { "type": "string" }, "file_name": { "type": "string" }, "mime_type": { "type": "string" }, "download_url": { "type": "string", "description": "Temporary download URL for the file, as the assistant provides it." } }, "description": "An SMG II 510 image: the 24 KiB calibration window or the 512 KiB full flash.", "additionalProperties": false } }, "additionalProperties": false }arguments 63 linespropose_rfkorr unknown 11h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "bin_file": { "type": "object", "required": [ "download_url", "file_id" ], "properties": { "file_id": { "type": "string" }, "file_name": { "type": "string" }, "mime_type": { "type": "string" }, "download_url": { "type": "string", "description": "Temporary download URL for the file, as the assistant provides it." } }, "description": "The 64 KB (65,536-byte) MSS54HP calibration partial (\"0401 partial BIN\").", "additionalProperties": false }, "log_file": { "type": "object", "required": [ "download_url", "file_id" ], "properties": { "file_id": { "type": "string" }, "file_name": { "type": "string" }, "mime_type": { "type": "string" }, "download_url": { "type": "string", "description": "Temporary download URL for the file, as the assistant provides it." } }, "description": "A drive log CSV: a Testo MSS54 export, or a CSV TUNER exported.", "additionalProperties": false }, "use_sample": { "type": "boolean", "description": "Use the practice BIN and practice drive instead of files — to show what the tool does before the owner has files." } }, "additionalProperties": false }arguments 59 linesread_bin unknown never probed
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "bin_file": { "type": "object", "required": [ "download_url", "file_id" ], "properties": { "file_id": { "type": "string" }, "file_name": { "type": "string" }, "mime_type": { "type": "string" }, "download_url": { "type": "string", "description": "Temporary download URL for the file, as the assistant provides it." } }, "description": "The 64 KB (65,536-byte) MSS54HP calibration partial (\"0401 partial BIN\").", "additionalProperties": false }, "use_sample": { "type": "boolean", "description": "Use the practice BIN and practice drive instead of files — to show what the tool does before the owner has files." } }, "additionalProperties": false }arguments 35 linessmg2_compare unknown never probed
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "image_file", "other_file", "xdf_file" ], "properties": { "xdf_file": { "type": "object", "required": [ "download_url", "file_id" ], "properties": { "file_id": { "type": "string" }, "file_name": { "type": "string" }, "mime_type": { "type": "string" }, "download_url": { "type": "string", "description": "Temporary download URL for the file, as the assistant provides it." } }, "description": "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.", "additionalProperties": false }, "image_file": { "type": "object", "required": [ "download_url", "file_id" ], "properties": { "file_id": { "type": "string" }, "file_name": { "type": "string" }, "mime_type": { "type": "string" }, "download_url": { "type": "string", "description": "Temporary download URL for the file, as the assistant provides it." } }, "description": "An SMG II 510 image: the 24 KiB calibration window or the 512 KiB full flash.", "additionalProperties": false }, "other_file": { "$ref": "#/properties/image_file" } }, "additionalProperties": false }arguments 63 linesread_log unknown never probed
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "bin_file": { "type": "object", "required": [ "download_url", "file_id" ], "properties": { "file_id": { "type": "string" }, "file_name": { "type": "string" }, "mime_type": { "type": "string" }, "download_url": { "type": "string", "description": "Temporary download URL for the file, as the assistant provides it." } }, "description": "The 64 KB (65,536-byte) MSS54HP calibration partial (\"0401 partial BIN\").", "additionalProperties": false }, "log_file": { "type": "object", "required": [ "download_url", "file_id" ], "properties": { "file_id": { "type": "string" }, "file_name": { "type": "string" }, "mime_type": { "type": "string" }, "download_url": { "type": "string", "description": "Temporary download URL for the file, as the assistant provides it." } }, "description": "A drive log CSV: a Testo MSS54 export, or a CSV TUNER exported.", "additionalProperties": false }, "use_sample": { "type": "boolean", "description": "Use the practice BIN and practice drive instead of files — to show what the tool does before the owner has files." } }, "additionalProperties": false }arguments 59 linessmg2_image unknown never probed
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "image_file": { "type": "object", "required": [ "download_url", "file_id" ], "properties": { "file_id": { "type": "string" }, "file_name": { "type": "string" }, "mime_type": { "type": "string" }, "download_url": { "type": "string", "description": "Temporary download URL for the file, as the assistant provides it." } }, "description": "An SMG II 510 image: the 24 KiB calibration window or the 512 KiB full flash.", "additionalProperties": false }, "use_sample": { "type": "boolean", "description": "Use the app's practice image (invented bytes)." } }, "additionalProperties": false }arguments 35 linespropose_ve unknown 11h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "bin_file": { "type": "object", "required": [ "download_url", "file_id" ], "properties": { "file_id": { "type": "string" }, "file_name": { "type": "string" }, "mime_type": { "type": "string" }, "download_url": { "type": "string", "description": "Temporary download URL for the file, as the assistant provides it." } }, "description": "The 64 KB (65,536-byte) MSS54HP calibration partial (\"0401 partial BIN\").", "additionalProperties": false }, "log_file": { "type": "object", "required": [ "download_url", "file_id" ], "properties": { "file_id": { "type": "string" }, "file_name": { "type": "string" }, "mime_type": { "type": "string" }, "download_url": { "type": "string", "description": "Temporary download URL for the file, as the assistant provides it." } }, "description": "A drive log CSV: a Testo MSS54 export, or a CSV TUNER exported.", "additionalProperties": false }, "use_sample": { "type": "boolean", "description": "Use the practice BIN and practice drive instead of files — to show what the tool does before the owner has files." } }, "additionalProperties": false }arguments 59 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id649cfe7e1aefceb6.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/649cfe7e1aefceb6/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/649cfe7e1aefceb6?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.