https://init.specpilot.dev/mcp ↗
Generate and validate a .specs/ bundle for your repo, then hand it to your AI coding agent
SpecPilot is a remote MCP server published at init.specpilot.dev. It has been probed 6 times since 9/14/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 944 ms, a delay an agent will notice. It offers a narrow, focused set of 2 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
specpilot_next_questions — Parameter 'answers' type is too vague (generic object) without required propertiesspecpilot_generate_specs — Required parameters (projectName, projectDescription) not explicitly defined in schemaspecpilot_next_questions — Optional parameter may create ambiguity in usage contexttools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
specpilot_next_questionsReturns 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
answersobjectspecpilot_generate_specsGenerates 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.
answersobjectrequiredDerived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/dev-specpilot-specpilot)<a href="https://mcpmetrics.io/servers/dev-specpilot-specpilot"><img src="https://mcpmetrics.io/badge/dev.specpilot/specpilot/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeThe catalog entries whose name and description are closest to this one, found with the same index the search box uses.
Carrier MCP — natural language control of your MVNO/eSIM fleet. 52 tools (43 OCS API wrappers + 8 AI intelligence + 1 OCS event history), 5 prompts, OAuth 2.1 + PKCE. Streamable HTTP on Cloudflare Workers.
Let your AI agent hire a human for tasks it can't do — first post free.
Probe a signup URL you own and score whether an AI agent can sign up unaided.
Scan website AI readiness, understand the result and route customers to the right SYA package.
Design your site's AI avatar in the ASMI studio; your coding agent ships it into your repo.
Governed skills for every AI agent your team runs. Curate one approved library of agent skills, distribute it to developers, and expose it over MCP to remote agents without copying files across machines.
| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-14 14:41:53 | Legacy | 400 | 598 | 200 | 761 | 2025-11-25 |
| 2026-09-14 12:38:15 | Legacy | 400 | 944 | 200 | 952 | 2025-11-25 |
| 2026-09-14 10:35:25 | Legacy | 400 | 1588 | 200 | 1645 | 2025-11-25 |
| 2026-09-14 08:31:43 | Legacy | 400 | 444 | 200 | 355 | 2025-11-25 |
| 2026-09-14 06:26:32 | Legacy | 400 | 1503 | 200 | 1393 | 2025-11-25 |
| 2026-09-14 04:24:59 | Legacy | 400 | 917 | 200 | 935 | 2025-11-25 |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.
Comments
Sign in to write a comment
No comments yet. Be the first.