Milestone by Ouroboros Apps
io.github.LAHutchins91/milestoneVersion 1.0.3Freelance project milestones and acceptance criteria for AI assistants
Status
Responds211 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:39 UTC
- Latency
- 211 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://milestone-continuity2.vercel.app/mcpResponds211 msNo sign-in
Claude Code
claude mcp add --transport http milestone https://milestone-continuity2.vercel.app/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: milestone
Remote MCP server URL: https://milestone-continuity2.vercel.app/mcpCursor
{
"mcpServers": {
"milestone": {
"url": "https://milestone-continuity2.vercel.app/mcp"
}
}
}VS Code
code --add-mcp '{"name":"milestone","type":"http","url":"https://milestone-continuity2.vercel.app/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
15 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
accept_milestone_changeApply 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 not a substitute for the freelancer's approval. | Yes | No | Yes | No |
approve_milestonesApprove the draft milestone definitions and acceptance criteria. Pass confirmed true only after the freelancer explicitly approves them. A draft is not a commitment. | Yes | No | Yes | No |
declare_milestone_completeState 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. | Yes | No | Yes | No |
declare_next_payment_releasedState 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 released when this tool refuses. | Yes | No | Yes | No |
define_milestoneAdd 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. | Yes | No | No | No |
list_milestone_setsList the signed-in freelancer's milestone sets. Use a returned id with read_milestone_set. Do not guess a set. | No | Yes | Yes | No |
mark_work_doneMark one saved work item done. Refuses when the work item was not saved. Do not mark unsaved work done. | Yes | No | Yes | No |
open_milestone_setOpen a draft milestone set for one client project. Draft definitions are not an approved commitment until approve_milestones. | No | No | No | No |
read_milestone_setRead 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 unless paymentReleased is true. Do not invent a deliverable. Do not mark unsaved work done. Proposed changes are not authorization. | No | Yes | Yes | No |
record_criterion_metRecord 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. | Yes | No | Yes | No |
save_acceptance_criterionSave 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. | Yes | No | No | No |
save_deliverableSave 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. | Yes | No | No | No |
save_work_itemSave 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. | Yes | No | Yes | No |
suggest_milestone_changeRecord 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_work_item requires milestoneId and title. kind revise_client_wording requires wording. | No | No | No | No |
write_client_wordingRecord 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 beyond this wording and the facts in read_milestone_set. | Yes | No | No | No |
Details
- Registry status
- Active
- Published
- Oct 8, 2026
- Updated
- Oct 8, 2026
- Categories (suggested)
- Project managementSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared