# SpecPilot (remote · init.specpilot.dev)

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

- Trust score: 67/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `init.specpilot.dev`: 67/100 (this document), [markdown](https://verifymcp.io/servers/dev-specpilot-specpilot/init.md), [page](https://verifymcp.io/servers/dev-specpilot-specpilot/init)

## Channel facts

- Endpoint: `https://init.specpilot.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 429 tokens (~214/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the SpecPilot MCP server?

SpecPilot is a hosted endpoint at https://init.specpilot.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-specpilot-specpilot 'https://init.specpilot.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-specpilot-specpilot": {
      "url": "https://init.specpilot.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-specpilot-specpilot": {
      "type": "http",
      "url": "https://init.specpilot.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-specpilot-specpilot]
url = "https://init.specpilot.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-specpilot-specpilot": {
      "type": "remote",
      "url": "https://init.specpilot.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-specpilot-specpilot --url 'https://init.specpilot.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-specpilot-specpilot:
    url: "https://init.specpilot.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-specpilot-specpilot": {
      "Transport": "http",
      "Url": "https://init.specpilot.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-specpilot-specpilot -t streamable-http -u 'https://init.specpilot.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-specpilot-specpilot": {
      "type": "http",
      "url": "https://init.specpilot.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 67, +1)

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

### 2026-09-18 (score 66, +1)

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

### 2026-09-16 (score 65, +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.

### 2026-09-14 (score 64, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-13 (score 63)

First indexed and scored.

## MCP tools (2)

### `specpilot_next_questions` (~351 tokens)

SpecPilot: next onboarding questions

Returns the still-unanswered SpecPilot onboarding questions of the next incomplete step, gated by the answers supplied so far - questions that do not apply to this kind of project are omitted, and options are filtered, badged or flagged the same way the SpecPilot web chat would. Stateless: send every answer collected so far on each call.

Procedure: (1) Decide whether the repository already has real source code and set `isNewBuild` accordingly - it changes which onboarding analysis is generated at the end. (2) Infer what the repo already answers rather than asking: `platforms` from the dependency manifests and layout, `languageOverride`, `ideAgent` (you are the IDE - claudecode, cursor, copilot, codex, windsurf), `handle` from git config or the origin remote, `projectName` from the package manifest or folder name, and `projectDescription` from the README only if it plainly says what the project is. (3) Call this tool with what you have; answer what the repo makes obvious and ask the developer the rest, a whole step per message. Send an empty value for an optional question the developer declines, or it will be asked again; send `todoSentinel` verbatim when they do not know yet. For `projectDescription`, sending one of the returned chip labels exactly is what infers `projectCategory` and gates every later question - free prose infers nothing. Confirm any pre-seeded value rather than accepting it silently. (4) Loop until `done` is true, then call specpilot_generate_specs and follow its `nextSteps` for where each file goes.

Input parameters:

- `answers` (object)

### `specpilot_generate_specs` (~78 tokens)

SpecPilot: generate the .specs/ files

Generates the complete SpecPilot .specs/ file set plus the matching IDE rules and slash-command files from a full answer set - identical to what the SpecPilot web chat produces for the same answers. Requires projectName and projectDescription. Returns the files to write and the steps to follow after writing them.

Input parameters:

- `answers` (object, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-specpilot-specpilot/init#diagnostics

## Score history

- 2026-09-20: 67
- 2026-09-19: 66
- 2026-09-18: 66
- 2026-09-17: 65
- 2026-09-16: 65
- 2026-09-15: 64
- 2026-09-14: 64
- 2026-09-13: 63

## Common questions

### What is the SpecPilot MCP server?

SpecPilot is an MCP server listed in the public MCP registry as dev.specpilot/specpilot. Generate and validate a .specs/ bundle for your repo, then hand it to your AI coding agent. This page covers its hosted endpoint (https://init.specpilot.dev/mcp).

### Is the SpecPilot MCP server safe to use?

SpecPilot scores 67 out of 100 on VerifyMCP. 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 SpecPilot MCP server expose?

SpecPilot exposes 2 tools: specpilot_next_questions, specpilot_generate_specs. Their descriptions and schemas cost roughly 429 tokens of context every time the server is loaded.

### Does the SpecPilot MCP server require authentication?

No. We connected to SpecPilot without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the SpecPilot MCP server still maintained?

SpecPilot is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://init.specpilot.dev/mcp
- Repository: https://github.com/girishr/SpecPilot
- Website: https://specpilot.dev/mcp-setup
- Changelog RSS feed: https://verifymcp.io/servers/dev-specpilot-specpilot/init.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-specpilot-specpilot/init.json
- HTML version of this page: https://verifymcp.io/servers/dev-specpilot-specpilot/init