Milestone by Ouroboros Apps is an MCP server with 15 tools an agent can call, among them accept_milestone_change, approve_milestones, declare_milestone_complete. It answers at https://milestone-continuity2.vercel.app/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 3 of 3 times since 6 October 2026; the last check, on 8 November 2026, succeeded.
Approved freelance milestone definitions and what done means, shared with AI assistants over MCP.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
accept_milestone_change | Apply one suggested milestone change after the freelancer explicitly approves that change. Pass confirmed true only then. This is the path for an extra deliverable, a new acceptance criterion, or new saved work after approval. Calling it is Inputs: milestoneSetId, changeId, confirmed |
approve_milestones | Approve the draft milestone definitions and acceptance criteria. Pass confirmed true only after the freelancer explicitly approves them. A draft is not a commitment. Inputs: milestoneSetId, confirmed |
declare_milestone_complete | State that a milestone is complete. Refuses unless the milestones are approved and every saved acceptance criterion on that milestone was met. Do not tell the client a milestone is complete when this tool refuses. Inputs: milestoneSetId, milestoneId |
declare_next_payment_released | State that the next payment for a milestone is released. Refuses unless the milestones are approved, every saved acceptance criterion on that milestone was met, and the milestone is complete. Do not tell the client the next payment is relea Inputs: milestoneSetId, milestoneId |
define_milestone | Add one milestone to a draft set: a title and the definition of that milestone. After milestones are approved, a new milestone is refused until accept_milestone_change applies an add_milestone suggestion. Inputs: milestoneSetId, title, definition |
list_milestone_sets | List the signed-in freelancer's milestone sets. Use a returned id with read_milestone_set. Do not guess a set. Inputs: offset |
mark_work_done | Mark one saved work item done. Refuses when the work item was not saved. Do not mark unsaved work done. Inputs: milestoneSetId, milestoneId, workItemId |
open_milestone_set | Open a draft milestone set for one client project. Draft definitions are not an approved commitment until approve_milestones. Inputs: clientName, projectTitle, reference |
read_milestone_set | Read the milestone set before answering. Quote only this record. mayTellClient and clientWording are what the assistant may tell the client. Do not say a milestone is complete unless complete is true. Do not say the next payment is released Inputs: milestoneSetId |
record_criterion_met | Record that one saved acceptance criterion was met. The criterion must already be saved. This does not by itself tell the client the milestone is complete or that the next payment is released. Inputs: milestoneSetId, milestoneId, criterionId |
save_acceptance_criterion | Save one acceptance criterion, which is what done means for that milestone. After milestones are approved, a new criterion is refused until an accepted add_criterion suggestion. This does not mark the milestone complete. Inputs: milestoneSetId, milestoneId, statement |
save_deliverable | Save one deliverable that belongs to a milestone. After milestones are approved, an extra deliverable is refused until an accepted add_deliverable suggestion. Do not invent a deliverable that was not saved. Inputs: milestoneSetId, milestoneId, title, detail |
save_work_item | Save one piece of work under a milestone so it can later be marked done. After milestones are approved, new work is refused until an accepted add_work_item suggestion. Unsaved work cannot be marked done. Inputs: milestoneSetId, milestoneId, title |
suggest_milestone_change | Record a suggested change. This does not change the milestones. kind add_milestone requires title and definition. kind add_criterion requires milestoneId and statement. kind add_deliverable requires milestoneId, title, and detail. kind add_ Inputs: milestoneSetId, kind, summary, milestoneId, title, definition |
write_client_wording | Record what the assistant may tell the client about milestones, what done means, completion, and payment release. After approval, different wording is refused until an accepted revise_client_wording suggestion. The assistant must not go bey Inputs: milestoneSetId, wording |
Every block below points at https://milestone-continuity2.vercel.app/mcp. Pick your client and copy.
claude mcp add --transport http milestone-by-ouroboros-apps https://milestone-continuity2.vercel.app/mcp
{
"mcpServers": {
"milestone-by-ouroboros-apps": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://milestone-continuity2.vercel.app/mcp"]
}
}
}{
"mcpServers": {
"milestone-by-ouroboros-apps": {
"url": "https://milestone-continuity2.vercel.app/mcp"
}
}
}{
"servers": {
"milestone-by-ouroboros-apps": {
"type": "http",
"url": "https://milestone-continuity2.vercel.app/mcp"
}
}
}{
"context_servers": {
"milestone-by-ouroboros-apps": {
"url": "https://milestone-continuity2.vercel.app/mcp"
}
}
}{
"mcpServers": {
"milestone-by-ouroboros-apps": {
"serverUrl": "https://milestone-continuity2.vercel.app/mcp"
}
}
}{
"mcpServers": {
"milestone-by-ouroboros-apps": {
"url": "https://milestone-continuity2.vercel.app/mcp"
}
}
}name: Milestone by Ouroboros Apps
version: 0.0.1
schema: v1
mcpServers:
- name: Milestone by Ouroboros Apps
type: streamable-http
url: https://milestone-continuity2.vercel.app/mcp{
"mcpServers": {
"milestone-by-ouroboros-apps": {
"httpUrl": "https://milestone-continuity2.vercel.app/mcp"
}
}
}{
"mcpServers": {
"milestone-by-ouroboros-apps": {
"type": "http",
"url": "https://milestone-continuity2.vercel.app/mcp"
}
}
}{
"mcpServers": {
"milestone-by-ouroboros-apps": {
"url": "https://milestone-continuity2.vercel.app/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmilestone-continuity2.vercel.app%2Fmcp&type=streamable_http&id=milestone-by-ouroboros-apps&name=Milestone%20by%20Ouroboros%20Apps
It answered our last check on 8 November 2026 in 185 ms. Over 3 checks since 6 October 2026 it answered 3. Status here comes from Neuronto's own probes, not from the publisher.
15, as returned by the server's own tools/list on 22 November 2026: accept_milestone_change, approve_milestones, declare_milestone_complete, declare_next_payment_released, define_milestone, list_milestone_sets, mark_work_done, open_milestone_set, and 7 more.
It answered our last check on 8 November 2026 in 185 ms. Over 3 checks since 6 October 2026 it answered 3.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://milestone-continuity2.vercel.app/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: io.github.lahutchins91. Endpoint host: milestone-continuity2.vercel.app. ARD identifier: urn:air:io.github.lahutchins91:mcp:milestone.
First indexed 5 October 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.