Remote MCP · Endpoint

JANCTION Render MCP server

No. JANCTION Render answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://render.janction.jp/mcp?src=registry

The last check completed an MCP handshake.

Registry name
io.github.JasmyLab-JANCTION/janction-render
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
632 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Blender and GLB/FBX/USD/STL rendered on cloud GPUs for AI agents: product shots, turntables, MP4
Listing
From the official MCP registry (active).
Recent checks of JANCTION Render
CheckedResultHandshake
34 minutes agoHandshake completed632 ms
8 days agoHandshake completed552 ms
9 days agoHandshake completed549 ms
11 days agoHandshake completed578 ms
12 days agoHandshake completed594 ms
12 days agoHandshake completed596 ms
14 days agoHandshake completed579 ms
14 days agoHandshake completed569 ms
16 days agoHandshake completed570 ms
19 days agoHandshake completed578 ms
21 days agoHandshake completed549 ms
24 days agoHandshake completed583 ms
26 days agoHandshake completed586 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 JANCTION Render and makes no claim about it beyond what these checks measured.