json-render is a framework where AI produces user interfaces as structured JSON constrained by a developer-defined component catalogue. It is for building dynamic interfaces from natural-language prompts across web and mobile frameworks.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/vercel-labs/json-renderWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/vercel-labs/json-render/json-render)<a href="https://agentmods.dev/mcp/vercel-labs/json-render/json-render"><img src="https://agentmods.dev/badge/mcp/vercel-labs/json-render/json-render/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/vercel-labs/json-render/json-render"><img src="https://agentmods.dev/badge/mcp/vercel-labs/json-render/json-render.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
json-render scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
1 near-identical copy found in the catalogue:
- pith — 86% identical, 5 lines differ
What it actually says
{
"json-render": {
"command": "npx",
"args": [
"tsx",
"examples/mcp/server.ts",
"--stdio"
]
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 10 lines scan A d8e39b24b6c1
json-render is an MCP server published in the GitHub repository vercel-labs/json-render (16,147 stars, last pushed 4d ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-08.
Other mcp servers, from other repositories
callspec
Stop duct-taping your API stack. One TypeScript route → typed SDK, docs, OpenAPI, and MCP. Runs locally from the callspec npm package.
ts-graph
MCP server "ts-graph" as configured in couzic/ts-graph-mcp. Runs dist/main.js with node.
project-manager
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package.
elysia-mcp-starter
MCP server "elysia-mcp-starter" as configured in kerlos/elysia-mcp-starter. Runs locally from the elysia-mcp-starter npm package.
vdiff-mcp
Breaking-change diffs for npm packages: removed exports, changed signatures, migration notes. Runs locally from the vdiff-mcp npm package. Needs 1 environment variable to run.
mcp-search
MCP server "mcp-search" as configured in thedotmack/claude-mem. Runs const f=require('fs'),p=require('path'),o=require('os'),c=require('child_process');const h=o.homedir();const C=process.env.CLAUDE_CONFIG_DIR||p.join(h,'.claude');const E=process.env.CLAUDE_PLUGIN_ROOT||process.env.PLUGIN_ROOT||'';const…