SpecPilot
REMOTE · INIT.SPECPILOT.DEV
Generate and validate a .specs/ bundle for your repo, then hand it to your AI coding agent
Available components
Last scanned (7 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
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. How we score → Why this is hard to score →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 449 tokens (~224/item across 2 items; 2 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
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.
- 25 Oct 26 0
- Tool “specpilot_next_questions” rewrote its description, which is the text the model reads security
- Schema quality: 253 → 224 ▲ functional
- 24 Oct 26 +10
- Authorization: unverified → partial ▲ security
- Schema quality: 214 → 253 ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Tool “specpilot_next_questions” now declares an output schema ▲ functional
- Tool “specpilot_generate_specs” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Schema quality: good → excellent functional
- “specpilot_generate_specs” reworded the description of “answers” cosmetic
- “specpilot_next_questions” reworded the description of “answers” cosmetic
- 13 Oct 26 0
- Stability: 0.97 → pass security
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +3
No change was recorded against any check on this day. Stability & Change Management went from 70 to 90. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 5 Nov 2026 · Probed https://init.specpilot.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=specpilot.dev | CN=WE1,O=Google Trust Services,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 3901ea70426fd4e90e18fa99d3ad0989 |
| SANs: specpilot.dev, init.specpilot.dev, *.init.specpilot.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of init.specpilot.dev. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| specpilot.dev. | present | 2371 | 13 | Verified |
| init.specpilot.dev. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://init.specpilot.dev/mcp | Verified | 200 | |
| http (plaintext) | http://init.specpilot.dev/mcp | HTTPS enforced | 301 | https://init.specpilot.dev/mcp |
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 →
specpilot_generate_specs SpecPilot: generate the .specs/ files ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | yes | The complete SpecPilot answer set to generate from - everything collected through specpilot_next_questions, whose schema describes each field. projectName and projectDescription are required; every o… |
| Name | Type | Req | Description |
|---|---|---|---|
| fileCount | number | yes | How many files were generated. |
| files | array | yes | Every file to write - spec files, the .specs/ README, and IDE or repository config. |
| nextSteps | array | yes | What to do after writing the files, including where each path belongs. |
No examples provided.
specpilot_next_questions SpecPilot: next onboarding questions ~330
Returns the unanswered SpecPilot onboarding questions of the next incomplete step, gated by the answers so far: questions that do not apply are omitted, and options are filtered, badged or flagged as in the SpecPilot web chat. Stateless: send every answer collected so far on each call. Procedure: (1) Set `isNewBuild` from whether the repo already has real source code. (2) Infer what the repo answers instead of asking: `platforms` from the manifests and layout, `languageOverride`, `ideAgent` (you are the IDE), `handle` from git config or the origin remote, `projectName` from the manifest or folder name, `projectDescription` from the README only if it plainly says what the project is. (3) Call this tool, answer what the repo makes obvious and ask the developer the rest, a whole step per message. Send an empty value for a declined optional question or it is asked again; send `todoSentinel` verbatim when they do not know yet. For `projectDescription`, an exact returned chip label infers `projectCategory` and gates later questions; free prose infers nothing. Confirm pre-seeded values rather than accepting them silently. (4) Loop until `done` is true, then call specpilot_generate_specs and follow its `nextSteps` for where each file goes.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | – | Every SpecPilot onboarding answer collected so far. The server is stateless, so resend the whole object on every call; omit it entirely on the first call to get step 1. |
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | yes | Every answer as the server now understands it, including defaults and seeded values. Send this back on the next call. |
| done | boolean | yes | True when every applicable question is answered and specpilot_generate_specs can be called. |
| questions | array | yes | The still-unanswered questions of the next incomplete step. Empty when done. |
| step | number | – | Number of the step these questions belong to. |
| stepLabel | string | – | Human-readable name of that step, e.g. "Scale & deploy". |
No examples provided.
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.
remote · init.specpilot.dev
claude mcp add --transport http dev-specpilot-specpilot 'https://init.specpilot.dev/mcp'
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 87 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 449 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.