# ngx-json-render UI (remote · ngx-json-render.vercel.app)

Renders dashboards, forms and tables inline in the chat as Angular Material components (MCP App).

- Trust score: 70/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `ngx-json-render.vercel.app`: 70/100 (this document), [markdown](https://verifymcp.io/servers/shteynu-ngx-json-render-ui/ngx-json-render.md), [page](https://verifymcp.io/servers/shteynu-ngx-json-render-ui/ngx-json-render)

## Channel facts

- Endpoint: `https://ngx-json-render.vercel.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 30/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 460 tokens (~230/item across 2 items; 1 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the ngx-json-render UI MCP server?

ngx-json-render UI is a hosted endpoint at https://ngx-json-render.vercel.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http shteynu-ngx-json-render-ui 'https://ngx-json-render.vercel.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "shteynu-ngx-json-render-ui": {
      "url": "https://ngx-json-render.vercel.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "shteynu-ngx-json-render-ui": {
      "type": "http",
      "url": "https://ngx-json-render.vercel.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.shteynu-ngx-json-render-ui]
url = "https://ngx-json-render.vercel.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shteynu-ngx-json-render-ui": {
      "type": "remote",
      "url": "https://ngx-json-render.vercel.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add shteynu-ngx-json-render-ui --url 'https://ngx-json-render.vercel.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  shteynu-ngx-json-render-ui:
    url: "https://ngx-json-render.vercel.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "shteynu-ngx-json-render-ui": {
      "Transport": "http",
      "Url": "https://ngx-json-render.vercel.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add shteynu-ngx-json-render-ui -t streamable-http -u 'https://ngx-json-render.vercel.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "shteynu-ngx-json-render-ui": {
      "type": "http",
      "url": "https://ngx-json-render.vercel.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-17 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-15 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-13 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-10 (score 64, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional improvement] Tool “render-ui” now declares an output schema
- [functional] First check of Tool coverage: 100

### 2026-10-09 (score 63)

First indexed and scored.

## MCP tools (1)

### `render-ui` (~451 tokens)

Render UI

Render an interactive Angular Material UI inline in the chat. Pass `spec`: one complete json-render spec object (not JSON Patch lines). The input schema lists every component, its props and allowed values, and every action; use only those.

\- `root` is the key of the top element. `elements` is a flat map of key → { type, props, children: [child keys] }; every child key must exist in `elements`.
\- `state` holds the data. Read it with {"$state":"/path"} rather than repeating values in props. Data-backed UI always needs `state`; use realistic sample data.
\- A prop can be dynamic: {"$state":"/p"} reads, {"$bindState":"/p"} binds a form field both ways, {"$template":"Hi ${/name}"} interpolates, {"$cond":{"$state":"/p"},"$then":a,"$else":b} picks.
\- Lists: on a container, "repeat":{"statePath":"/items","key":"id"}; its children render once per item and read {"$item":"field"}, or ${field} inside a $template.
\- `visible` and `on` sit next to `props`, never inside: "visible":{"$state":"/tab","eq":"home"}, "on":{"press":{"action":"setState","params":{"statePath":"/tab","value":"home"}}}.
\- Forms: give inputs props.validation {"checks":[{"type":"required","message":"..."}]} and submit with submitForm, which runs its inner action only when every field is valid.
\- To continue the conversation from a button, use sendMessage: {"action":"sendMessage","params":{"text":"Approve release 2.4.0","data":{"$state":"/release"}}}. The host puts `text` (and `data` as JSON) in the chat as the user's message, so write it in their voice. For a form: {"action":"submitForm","params":{"action":"sendMessage","params":{"text":"Sign me up","data":{"$state":"/form"}}}}.

Input parameters:

- `spec` (object, required)

Output parameters:

- `spec` (object): The json-render spec that was rendered.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/shteynu-ngx-json-render-ui/ngx-json-render#diagnostics

## Score history

- 2026-10-23: 70
- 2026-10-22: 69
- 2026-10-21: 69
- 2026-10-20: 68
- 2026-10-19: 68
- 2026-10-18: 67
- 2026-10-17: 67
- 2026-10-16: 66
- 2026-10-15: 66
- 2026-10-14: 65
- 2026-10-13: 65
- 2026-10-12: 64
- 2026-10-10: 64
- 2026-10-09: 63

## Common questions

### What is the ngx-json-render UI MCP server?

ngx-json-render UI is an MCP server listed in the public MCP registry as io.github.shteynu/ngx-json-render-ui. Renders dashboards, forms and tables inline in the chat as Angular Material components (MCP App). This page covers its hosted endpoint (https://ngx-json-render.vercel.app/mcp).

### Is the ngx-json-render UI MCP server safe to use?

ngx-json-render UI scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the ngx-json-render UI MCP server expose?

ngx-json-render UI exposes 1 tool: render-ui. Their descriptions and schemas cost roughly 451 tokens of context every time the server is loaded.

### Does the ngx-json-render UI MCP server require authentication?

No. We connected to ngx-json-render UI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ngx-json-render UI MCP server still maintained?

ngx-json-render UI is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://ngx-json-render.vercel.app/mcp
- Repository: https://github.com/shteynu/ngx-json-render
- Website: https://shteynu.github.io/ngx-json-render/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/shteynu-ngx-json-render-ui/ngx-json-render.xml
- Changelog JSON feed: https://verifymcp.io/servers/shteynu-ngx-json-render-ui/ngx-json-render.json
- HTML version of this page: https://verifymcp.io/servers/shteynu-ngx-json-render-ui/ngx-json-render