# dev.specpilot/specpilot

Generate and validate a .specs/ bundle for your repo, then hand it to your AI coding agent

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.0
- **Author:** dev.specpilot
- **License:** Unknown
- **Endpoints:** streamable-http https://init.specpilot.dev/mcp
- **Source:** https://github.com/girishr/SpecPilot
- **Endpoint health:** reachable (last checked 2026-09-24T15:02:02.050Z, 2 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 20 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-14T18:35:41.734Z
- **Version scanned:** HEAD
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

20 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `status` — Show sprint status
- `refine` — Refine specs
- `reanchor` — Restore full project context after losing it mid-session
- `report` — Run the Spec-First review gate: classify the change, update specs, then wait for confirmation before coding
- `sync` — Compare .specs/ against actual project state and propose fixes for drift
- `validate` — Validate .specs/ structure, front-matter, and cross-references; suggest fixes without auto-applying
- `archive` — Archive oversized .specs/ files (tasks.md Completed section, prompts.md) with a branch safety guard
- `backfill` — Append missing mandate sections (Critical Mandates, Code Philosophy, Code Rules, Re-Anchor) to existing IDE files
- `api.yaml` — CLI / REST API / GraphQL interface spec
- `architecture.md` — system design decisions and patterns
- `context.md` — development memory, decisions, learnings
- `prompts.md` — AI interaction log — MANDATED, update every session
- `onboarding.md` — one-time onboarding prompt — delete after first use
- `roadmap.md` — release milestones and objectives
- `tasks.md` — sprint tracker (backlog / current / completed)
- `project.yaml` — project config, rules, AI context (MANDATED)
- `requirements.md` — functional and non-functional requirements
- `tests.md` — test strategy and coverage targets
- `security-decisions.md` — security ADR log (mitigations and rationale)
- `threat-model.md` — threat model and attack surface analysis

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"specpilot\": {\n      \"type\": \"http\",\n      \"url\": \"https://init.specpilot.dev/mcp\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/dev.specpilot%2Fspecpilot
- Install plan: https://forgeregistry.com/api/v1/packages/dev.specpilot%2Fspecpilot/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/dev.specpilot%2Fspecpilot
- HTML page: https://forgeregistry.com/registry/dev.specpilot%2Fspecpilot
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.