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/sharozdawa/schema-genWrote 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/sharozdawa/schema-gen/schema-gen)<a href="https://agentmods.dev/mcp/sharozdawa/schema-gen/schema-gen"><img src="https://agentmods.dev/badge/mcp/sharozdawa/schema-gen/schema-gen.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
schema-gen 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 6d 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.
What it actually says
{
"schema-gen": {
"command": "npx",
"args": [
"-y",
"schema-gen-mcp"
],
"env": {}
}
}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.
- 6d ago First seen · 10 lines scan A 8187c88efec7
schema-gen is an MCP server published in the GitHub repository sharozdawa/schema-gen (0 stars, last pushed 5mo ago), licensed MIT. 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-08-31.
Other mcp servers, from other repositories
nx-mcp
Nx's MCP server: lets the agent read the Nx project graph, look up generators and run tasks in an Nx monorepo. Runs locally from the nx npm package.
copilotkit-docs
CopilotKit's hosted docs server: lets the agent search CopilotKit documentation and examples. Remote server at mcp.copilotkit.ai.
iso27001-mcp
ISO 27001 compliance workspace for Claude. Risks, policies, SoA, evidence, and audit workflows. Runs locally from the iso27001-mcp npm package. Needs 4 environment variables to run.
puppeteer
Lets the agent control a headless Chrome browser with Puppeteer: navigate, click, fill forms and screenshot. Runs locally from the @modelcontextprotocol/server-puppeteer npm package.
wet-mcp
Open-source MCP Server for web search, extract, crawl, academic research, and library docs with embedded SearXNG. Runs locally from the wet-mcp Python package. Needs 2 environment variables to run.
clerk
MCP server "clerk", hosted remotely at mcp.clerk.com, as configured in FloB95/qrcodly.