com.seanwinslow/intent-engineering
NPM · @SWINS/INTENT-ENGINEERING-MCP · SCANNED SEP 21
Audit, scaffold, and triage agent intent specs against a 9-section template.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 94 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 485 tokens (~161/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.seanwinslow/intent-engineering MCP server?
com.seanwinslow/intent-engineering runs locally as an npm package, launched with npx -y @swins/intent-engineering-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @swins/intent-engineering-mcp
claude mcp add com-seanwinslow-intent-engineering -- npx -y @swins/intent-engineering-mcp
{
"mcpServers": {
"com-seanwinslow-intent-engineering": {
"command": "npx",
"args": [
"-y",
"@swins/intent-engineering-mcp"
]
}
}
} {
"servers": {
"com-seanwinslow-intent-engineering": {
"command": "npx",
"args": [
"-y",
"@swins/intent-engineering-mcp"
]
}
}
} codex mcp add com-seanwinslow-intent-engineering -- npx -y @swins/intent-engineering-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-seanwinslow-intent-engineering": {
"type": "local",
"command": [
"npx",
"-y",
"@swins/intent-engineering-mcp"
],
"enabled": true
}
}
} openclaw mcp add com-seanwinslow-intent-engineering --command npx --arg -y --arg @swins/intent-engineering-mcp
mcp_servers:
com-seanwinslow-intent-engineering:
command: "npx"
args: ["-y", "@swins/intent-engineering-mcp"] {
"McpServers": {
"com-seanwinslow-intent-engineering": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@swins/intent-engineering-mcp"
]
}
}
} assistant mcp add com-seanwinslow-intent-engineering -t stdio -c npx -a -y @swins/intent-engineering-mcp
{
"mcpServers": {
"com-seanwinslow-intent-engineering": {
"command": "npx",
"args": [
"-y",
"@swins/intent-engineering-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +1
- Stability: 0.97 → pass security
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 −3
- Stability: pass → 0.80 functional
- 14 Sept 26 +1
- Stability: 0.97 → pass security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.83 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/@swins/intent-engineering-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
assess_retrofit_level Assess Retrofit Level ~127
Look at an existing prompt or SKILL.md and recommend the right retrofit level (L1-mvr / L2-structured / L3-full) with reasoning grounded in the intent-engineering skill's blast-radius / complexity / autonomy framework. Provide either skill_text (raw text) OR file_path (absolute path to an existing SKILL.md or prompt file).
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | – | Absolute path to an existing SKILL.md or prompt file. |
| skill_text | string | – | The existing prompt or SKILL.md text. Provide this OR file_path, not both. |
No output schema declared.
No examples provided.
audit_intent_spec Audit Intent Spec ~171
Audit an intent spec against the 25-item validation checklist and the 5 fatal anti-patterns from the intent-engineering skill. Provide either spec_text (raw spec) OR file_path (absolute path to a markdown or YAML file). For long inputs, use start_index + max_length to paginate; the response includes next_chunk_token when more content remains.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | – | Absolute path to a markdown or YAML intent spec file. Provide this OR spec_text, not both. |
| max_length | integer | – | Max characters of input to process this call. Default 10000. |
| spec_text | string | – | The raw intent spec text. Provide this OR file_path, not both. |
| start_index | integer | – | Zero-based character offset for paginated input. Default 0. |
No output schema declared.
No examples provided.
generate_intent_spec_scaffold Generate Intent Spec Scaffold ~187
Return the appropriate intent-spec template (blank, Level-1 MVR, or full 9-section) with optional pre-filled objective_hint, autonomy_level, and agent_name. Use this when starting a new agent/skill or retrofitting an existing one.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | – | Optional agent/skill name. Used in the YAML header. |
| autonomy_level | string | – | Optional autonomy level. Pre-fills the Decision Authority section with the matching architecture pattern. |
| kind | string | – | Which scaffold to return. 'blank' = empty 9-section template; 'level-1-mvr' = 3-section minimum-viable retrofit; 'full-9-section' = full template with prompts. |
| objective_hint | string | – | Optional one-sentence hint about what the agent should do. Pre-fills the objective field with a starter draft. |
No output schema declared.
No examples provided.
What is the com.seanwinslow/intent-engineering MCP server?
com.seanwinslow/intent-engineering is an MCP server listed in the public MCP registry as com.seanwinslow/intent-engineering. Audit, scaffold, and triage agent intent specs against a 9-section template. This page covers its npm package (@swins/intent-engineering-mcp).
Is the com.seanwinslow/intent-engineering MCP server safe to use?
com.seanwinslow/intent-engineering scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.seanwinslow/intent-engineering MCP server expose?
com.seanwinslow/intent-engineering exposes 3 tools: audit_intent_spec, generate_intent_spec_scaffold, assess_retrofit_level. Their descriptions and schemas cost roughly 485 tokens of context every time the server is loaded.
Is the com.seanwinslow/intent-engineering MCP server still maintained?
com.seanwinslow/intent-engineering is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.seanwinslow/intent-engineering MCP server under?
com.seanwinslow/intent-engineering declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.