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/nutriandrea/adobe-indesign-mcpWrote 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/nutriandrea/adobe-indesign-mcp/indesign-nutria-mcp)<a href="https://agentmods.dev/mcp/nutriandrea/adobe-indesign-mcp/indesign-nutria-mcp"><img src="https://agentmods.dev/badge/mcp/nutriandrea/adobe-indesign-mcp/indesign-nutria-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/nutriandrea/adobe-indesign-mcp/indesign-nutria-mcp"><img src="https://agentmods.dev/badge/mcp/nutriandrea/adobe-indesign-mcp/indesign-nutria-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
indesign-nutria-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 2d 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
{
"indesign-nutria-mcp": {
"command": "npx",
"args": [
"-y",
"indesign-nutria-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.
- 2d ago First seen · 10 lines scan A 74b55e4ccb55
indesign-nutria-mcp is an MCP server published in the GitHub repository nutriandrea/adobe-indesign-mcp (37 stars, last pushed yesterday), 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-10-26.
Other mcp servers, from other repositories
mcp-indesign
MCP server for Adobe InDesign automation on Windows. Runs locally from the mcp-indesign npm package.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.
Figma-Context-MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot. Runs locally from the figma-developer-mcp npm package. Needs 1 environment variable to run.
photoshop-mcp
MCP server for Adobe Photoshop — 118 tools (generative AI + recipes), standalone web UI. Control Ph… Runs locally from the @alisaitteke/photoshop-mcp npm package.
premiere-pro
MCP server for Adobe Premiere Pro with 384 core AI video editing tools, a guarded After Effects MOGRT studio, and a capability-aware UXP bridge for supported Premiere workflows. Runs locally from the premiere-pro-mcp npm package.
premiere-pro
Local-first MCP for supported Adobe Premiere Pro workflows; start with a read-only connection check. Runs locally from the premiere-pro-mcp npm package.