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/etoyama/insight-blueprintWrote 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/etoyama/insight-blueprint/spec-workflow)<a href="https://agentmods.dev/mcp/etoyama/insight-blueprint/spec-workflow"><img src="https://agentmods.dev/badge/mcp/etoyama/insight-blueprint/spec-workflow.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
spec-workflow 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
{
"spec-workflow": {
"command": "npx",
"args": [
"-y",
"@pimzino/spec-workflow-mcp@latest",
"."
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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 30c5fea56f69
spec-workflow is an MCP server published in the GitHub repository etoyama/insight-blueprint (0 stars, last pushed 13d 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
email-dev
MCP server "email-dev" as configured in Wh1isper/mcp-email-server. Launched with {{ PWD }}/.venv/bin/python {{ PWD }}/mcp_email_server/cli.py stdio.
unraid-mcp
MCP Server for Unraid API - provides tools to interact with an Unraid server's GraphQL API. Runs locally from the unraid-mcp Python package. Needs 3 environment variables to run.
RivalSearchMCP
MCP server "RivalSearchMCP", hosted remotely at rivalsearchmcp.fastmcp.app, as configured in damionrashford/RivalSearchMCP.
admin-procedures
This package name is reserved by Microsoft Corporation. Runs locally from the excel Python package.
mcp-outline
A Model Context Protocol (MCP) server for Outline (https://www.getoutline.com). Runs locally from the mcp-outline Python package. Needs 6 environment variables to run.
inkscape-mcp
MCP server "inkscape-mcp" as configured in sandraschi/inkscape-mcp. Launched with uv --directory D:/Dev/repos/inkscape-mcp run inkscape-mcp.