SpecPilot
REMOTE · INIT.SPECPILOT.DEV · SCANNED SEP 20
Generate and validate a .specs/ bundle for your repo, then hand it to your AI coding agent
Available components
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 Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- 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 Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
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
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'
{
"mcpServers": {
"dev-specpilot-specpilot": {
"url": "https://init.specpilot.dev/mcp"
}
}
} {
"servers": {
"dev-specpilot-specpilot": {
"type": "http",
"url": "https://init.specpilot.dev/mcp"
}
}
} [mcp_servers.dev-specpilot-specpilot] url = "https://init.specpilot.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-specpilot-specpilot": {
"type": "remote",
"url": "https://init.specpilot.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-specpilot-specpilot --url 'https://init.specpilot.dev/mcp' --transport streamable-http
mcp_servers:
dev-specpilot-specpilot:
url: "https://init.specpilot.dev/mcp" {
"McpServers": {
"dev-specpilot-specpilot": {
"Transport": "http",
"Url": "https://init.specpilot.dev/mcp"
}
}
} assistant mcp add dev-specpilot-specpilot -t streamable-http -u 'https://init.specpilot.dev/mcp'
{
"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.
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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 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.
- 14 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 13 Sept 26 63
First indexed and scored.
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 20 Sept 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 | 24 Aug 2026 | 22 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 46c1ec1d1f3d920f1358756fcd5fbf86 |
| 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 ~78
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 | – |
No output schema declared.
No examples provided.
specpilot_next_questions SpecPilot: next onboarding questions ~351
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.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | – | – |
No output schema declared.
No examples provided.
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.