Remote MCP · Endpoint

TSUNAGI///Matrix — MAPPING MCP server

No. TSUNAGI///Matrix — MAPPING answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://matrix-mcp.tsunagi.app/mcp/mapping

The last check completed an MCP handshake.

Registry name
io.github.mushitaro/matrix-tsunagi-mapping
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
212 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
BMW E46 M3 DME and SMG II: VE and rf_korr from Testo logs, decode SMG calibrations. Local.
Listing
From the official MCP registry (active).
Recent checks of TSUNAGI///Matrix — MAPPING
CheckedResultHandshake
20 minutes agoHandshake completed212 ms
3 days agoHandshake completed151 ms
14 days agoHandshake completed237 ms
14 days agoHandshake completed243 ms
15 days agoHandshake completed356 ms
16 days agoHandshake completed890 ms
18 days agoHandshake completed193 ms
18 days agoHandshake completed49 ms
19 days agoHandshake completed230 ms
21 days agoHandshake completed183 ms
23 days agoHandshake completed517 ms
25 days agoHandshake completed229 ms
28 days agoHandshake completed165 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with TSUNAGI///Matrix — MAPPING and makes no claim about it beyond what these checks measured.