Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AI-SDLC Prompts

NPM · AI-SDLC-PROMPTS-MCP

112 SDLC prompts (ES/EN) for AI coding agents, each with its operating contract.

Available components

79 Trust /100

Last scanned (17 hours ago)

Scores higher than 62% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

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
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency84
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to dleon55/ai-sdlc-prompts). View diagnostics → Pass
  • License check failed: the license (MIT AND CC-BY-4.0) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 3 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 579 tokens (~115/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 87% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 77

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Analysed npm/ai-sdlc-prompts-mcp@1.0.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo dleon55/ai-sdlc-prompts
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/dleon55/ai-sdlc-prompts/.github/workflows/publish-mcp.yml@refs/tags/mcp-v1.0.2
Rekor log index 3622653449
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:400b5ece1ec3ef6f07495e964548c10fc8ba5a969494f6d05a847b766ee00be2d389efaff27002c4b687edb30783414f4e9c3548a2d7a85660ba548ae

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~579 tokens

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 →

Tool Tokens
get_framework ~56

Devuelve el preámbulo obligatorio del framework AI-SDLC (principio operativo que se antepone a cualquier prompt de la biblioteca).

NameTypeReqDescription
langstring–Idioma de salida (es/en). Por defecto: es.

No output schema declared.

No examples provided.

get_prompt ~97

Devuelve el detalle completo de un prompt por id: título, descripción, texto crudo del prompt (con placeholders [ASI] sin resolver), fórmulas de uso, contrato editorial y siguiente(s) prompt(s) recomendado(s).

NameTypeReqDescription
idstringyesId del prompt, ej. '07-06-pruebas-performance-carga'.
langstring–Idioma de salida (es/en). Por defecto: es.

No output schema declared.

No examples provided.

list_prompts ~128

Lista los prompts de la biblioteca AI-SDLC Pro, con filtro opcional por sección (00-17), riesgo esperado (low/medium/high/variable), autonomía permitida (A0-A3) y texto libre (busca en título y descripción).

NameTypeReqDescription
autonomystring––
langstring–Idioma de salida (es/en). Por defecto: es.
querystring–Texto libre a buscar en título/descripción.
riskstring––
sectionstring–Código de sección, ej. '07', '16'.

No output schema declared.

No examples provided.

recommend_next ~57

Devuelve el/los prompt(s) que el contrato editorial recomienda usar después de uno dado.

NameTypeReqDescription
idstringyesId del prompt actual.
langstring–Idioma de salida (es/en). Por defecto: es.

No output schema declared.

No examples provided.

resolve_prompt ~241

Sustituye los placeholders del prompt (y opcionalmente del preámbulo del framework) con las variables provistas -- misma sustitución que hace el sitio. Las claves de 'variables' son los campos canónicos (repositorio, referencia, rama_actual, rama_destino, ambiente, componentes, modulo, stack, tipo_proyecto, metodologia, agentes, autonomia, entrada, objetivo, responsable, workspace, compliance, documentos, profundidad, adicionales), no los alias en mayúsculas del texto. Devuelve el texto resuelto y los placeholders obligatorios/opcionales que quedaron sin resolver.

NameTypeReqDescription
append_contractboolean–Anexa el contrato de operación del prompt -- techo de autonomía, herramientas permitidas, criterios de detención y evidencia mínima (default: true). Desactivarlo entrega el prompt sin sus límites.
idstringyesId del prompt a resolver.
langstring–Idioma de salida (es/en). Por defecto: es.
prepend_frameworkboolean–Antepone el preámbulo obligatorio del framework (default: true).
variablesobject–Campo canónico -> valor.

No output schema declared.

No examples provided.

Install

How do I install the AI-SDLC Prompts MCP server?

AI-SDLC Prompts runs locally as an npm package, launched with npx -y ai-sdlc-prompts-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 · ai-sdlc-prompts-mcp

# add to Claude Code
claude mcp add dleon55-ai-sdlc-prompts -- npx -y ai-sdlc-prompts-mcp
Common questions

What is the AI-SDLC Prompts MCP server?

AI-SDLC Prompts is an MCP server listed in the public MCP registry as io.github.dleon55/ai-sdlc-prompts. 112 SDLC prompts (ES/EN) for AI coding agents, each with its operating contract. This page covers its npm package (ai-sdlc-prompts-mcp).

Is the AI-SDLC Prompts MCP server safe to use?

AI-SDLC Prompts scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 AI-SDLC Prompts MCP server expose?

AI-SDLC Prompts exposes 5 tools: list_prompts, get_prompt, resolve_prompt, get_framework, recommend_next. Their descriptions and schemas cost roughly 579 tokens of context every time the server is loaded.

Is the AI-SDLC Prompts MCP server still maintained?

AI-SDLC Prompts is still listed as active in the MCP registry. We last reached this channel on 5 November 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 AI-SDLC Prompts MCP server under?

AI-SDLC Prompts declares the MIT AND CC-BY-4.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

What did VerifyMCP test on the AI-SDLC Prompts MCP server?

VerifyMCP ran 16 checks on AI-SDLC Prompts, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.