Remote MCP · Endpoint

Rengi Forge MCP server

No. Rengi Forge answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://rengi.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.MRRengi/rengi-forge
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
346 ms
Tools exposed
85 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Gamedev tools for AI agents: level design, renders, sprites, GLB optimizer. Pay per call with x402.
Listing
From the official MCP registry (active).
Recent checks of Rengi Forge
CheckedResultHandshake
35 minutes agoHandshake completed346 ms
9 days agoHandshake completed321 ms
10 days agoHandshake completed328 ms
11 days agoHandshake completed315 ms
12 days agoHandshake completed309 ms
14 days agoHandshake completed313 ms
14 days agoHandshake completed323 ms
15 days agoHandshake completed313 ms
17 days agoHandshake completed316 ms
19 days agoHandshake completed322 ms
21 days agoHandshake completed313 ms
24 days agoHandshake completed311 ms
26 days agoHandshake completed311 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Rengi Forge and makes no claim about it beyond what these checks measured.