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/EYamanS/chiselWrote 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/eyamans/chisel/chisel-mcp)<a href="https://agentmods.dev/mcp/eyamans/chisel/chisel-mcp"><img src="https://agentmods.dev/badge/mcp/eyamans/chisel/chisel-mcp/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/eyamans/chisel/chisel-mcp"><img src="https://agentmods.dev/badge/mcp/eyamans/chisel/chisel-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
chisel-mcp 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 1mo 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
{ "chisel-mcp": { "command": "npx", "args": [ "-y", "chisel-mcp" ] } }
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.
- 1mo ago First seen · 9 lines scan A 4993cac1fb6f
chisel-mcp is an MCP server published in the GitHub repository EYamanS/chisel (7 stars, last pushed 3mo 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
sceneview
MCP server for SceneView — cross-platform 3D & AR SDK for Android and iOS. Gives your AI coding assistant the full SceneView SDK so it writes correct, compilable code. Runs locally from the sceneview-mcp npm package.
sceneview
3D & AR SDK for Android, iOS, Web — API docs, samples, validation, and code generation. Runs locally from the sceneview-mcp npm package.
blender-agent-studio
MCP server "blender-agent-studio" as configured in ifBars/blender-agent-studio. Launched with bun ./mcp/server.ts.
TwelveLabs
TwelveLabs MCP Server. Runs locally from the twelvelabs-mcp npm package. Needs 1 environment variable to run.
Pexels
An MCP server for Pexels. Runs locally from the pexels-mcp-server Python package. Needs 1 environment variable to run.
game-assets
Generate game assets with AI: sprites, 3D models, animations, sound effects, music, and voices. Remote server at mcp.ludo.ai.