agentmods.dev

spec-workflow

spec-workflow is an MCP server for Claude Code from etoyama/insight-blueprint. Its token cost is not measured, scanned A, original, MIT.

A local server for spec-driven development, where software is planned and built from written requirements. It also provides a live web dashboard for following that work.

In plain words
What is it for?
Use it to manage a requirements-led development workflow and view its current state in a browser dashboard.
Why use it?
It helps keep implementation connected to explicit specifications and makes progress visible.

MCP server for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: listed in a Claude config.

Part of the insight-blueprint plugin — 10 skills, 2 MCP servers shipped together

One of 2 entries in .mcp.json upstream. Installing this one merges just its entry into your config; the other 1 are separate, each on its own page.

not rated 0repo 12d ago A scan tokens not measured original MIT

Good fit Use it to manage a requirements-led development workflow and view its current state in a browser dashboard.

Compare 6 mcp servers from other repositories ↓
Install with agentmods
npx agentmods add mcp/etoyama/insight-blueprint/spec-workflow
View source ↗ etoyama/insight-blueprint pypi.org
Install

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.

Clone the repo
git clone --depth 1 https://github.com/etoyama/insight-blueprint

Made for: Claude Code.

Or install insight-blueprint, the plugin that ships this one along with the rest of its 10 skills, 2 MCP servers.

Wrote 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.

agentmods badge for spec-workflow

README.md
[![agentmods](https://agentmods.dev/badge/mcp/etoyama/insight-blueprint/spec-workflow/github.svg)](https://agentmods.dev/mcp/etoyama/insight-blueprint/spec-workflow)
Your own site
<a href="https://agentmods.dev/mcp/etoyama/insight-blueprint/spec-workflow"><img src="https://agentmods.dev/badge/mcp/etoyama/insight-blueprint/spec-workflow/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.

agentmods 80×15 button for spec-workflow

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

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 2mo 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.

.mcp.json · 10 lines

What it actually says

{
  "spec-workflow": {
    "command": "npx",
    "args": [
      "-y",
      "@pimzino/spec-workflow-mcp@latest",
      "."
    ]
  }
}
Same file

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.

Changes

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.

  1. 2mo ago First seen · 10 lines scan A 30c5fea56f69

Subscribe to this mod's changes

spec-workflow is an MCP server published in the GitHub repository etoyama/insight-blueprint (0 stars, last pushed 12d 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.

Claude CodePlanningdata-analysisfastmcphypothesis-drivenmcpmcp-server
Related

spec-workflow compared with mcp servers from other repositories

spec-workflow next to 6 mcp servers from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
spec-workflowetoyama/insight-blueprintMCP server012d agoMITA—Claude Code
mcp-outlineVortiago/mcp-outlineMCP server1597d agoMITA—Claude Code
unraid-mcpdinglebear-ai/unraidMCP server1504d agoMITA—Claude Code
RivalSearchMCPdamionrashford/RivalSearchMCPMCP server1372d agoMITA—Claude Code, Codex, Cursor, Gemini CLI, OpenCode
inkscape-mcpsandraschi/inkscape-mcpMCP server9714d agoMITA—Claude Code
ActiveDirectoryMCPalpadalar/ActiveDirectoryMCPMCP server523d agoMITA—Claude Code, Codex, Cursor, Gemini CLI, OpenCode
AynOpsAynOps/AynOpsMCP server29yesterdayMITA—Claude Code, Codex, Cursor, Gemini CLI, OpenCode