Remote MCP · Endpoint
ngx-json-render UI MCP server
No. ngx-json-render UI answered an MCP handshake 3 hours ago.
UpLast checked 3 hours ago
Server URL
https://ngx-json-render.angular-generative-ui-chat.workers.dev/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.shteynu/ngx-json-render-ui
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 441 ms
- Tools exposed
- 1 tool
- Uptime, last 30 days
- 100% from 11 checks
- Described by its publisher as
- Renders dashboards, forms and tables inline in the chat as Angular Material components (MCP App).
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 3 hours ago | Handshake completed | 441 ms |
| 4 days ago | Handshake completed | 613 ms |
| 14 days ago | Handshake completed | 309 ms |
| 15 days ago | Handshake completed | 616 ms |
| 15 days ago | Handshake completed | 286 ms |
| 17 days ago | Handshake completed | 435 ms |
| 18 days ago | Handshake completed | 214 ms |
| 19 days ago | Handshake completed | 296 ms |
| 20 days ago | Handshake completed | 372 ms |
| 21 days ago | Handshake completed | 201 ms |
| 23 days ago | Handshake completed | 105 ms |
The last 11 checks. Full history is kept for 30 days; the all-time counter stands at 11 responding of 11.
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 ngx-json-render UI and makes no claim about it beyond what these checks measured.