Milestone by Ouroboros Apps

by LAHutchins91 · remote · no sign-in to list tools · v1.0.3 · published by GitHub user LAHutchins91

Freelance project milestones and acceptance criteria for AI assistants

Deletes · 11Changes · 2

Compare Registry entry

15 tools: 11 can delete or cancel things, 2 change things and 2 only read.

Scanned Oct 21, 2026

Deletes or cancels11Claude Code: deny: see these tools
Can't be undone0Claude Code: ask
Changes things2Claude Code: ask: see these tools
Only reads2Claude Code: allow: see these tools

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http milestone https://milestone-continuity2.vercel.app/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

15 tools

Deletes or cancels 11Removes, cancels or revokes something.Claude Code: deny

accept_milestone_changeApply one suggested milestone change after the freelancer explicitly approves that change.No findings
Why it is in this group
- The description's first verb is "apply": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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 not a substitute for the freelancer's approval.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
approve_milestonesApprove the draft milestone definitions and acceptance criteria.No findings
Why it is in this group
- The name "approve_milestones" says "approve": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
Approve the draft milestone definitions and acceptance criteria. Pass confirmed true only after the freelancer explicitly approves them. A draft is not a commitment.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
declare_milestone_completeState that a milestone is complete.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
declare_next_payment_releasedState that the next payment for a milestone is released.No findings
Why it is in this group
- The name "declare_next_payment_released" says "payment": a word that usually means money moves, which cannot be taken back.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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 released when this tool refuses.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
define_milestoneAdd one milestone to a draft set: a title and the definition of that milestone.No findings
Why it is in this group
- The description's first verb is "add": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
mark_work_doneMark one saved work item done.No findings
Why it is in this group
- The name "mark_work_done" says "mark": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
Mark one saved work item done. Refuses when the work item was not saved. Do not mark unsaved work done.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
record_criterion_metRecord that one saved acceptance criterion was met.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
save_acceptance_criterionSave one acceptance criterion, which is what done means for that milestone.No findings
Why it is in this group
- The name "save_acceptance_criterion" says "save": a word for a change.
- The input takes a statement or command to run (input.statement), which can change anything it can reach.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
save_deliverableSave one deliverable that belongs to a milestone.No findings
Why it is in this group
- The name "save_deliverable" says "save": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
save_work_itemSave one piece of work under a milestone so it can later be marked done.No findings
Why it is in this group
- The name "save_work_item" says "save": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
write_client_wordingRecord what the assistant may tell the client about milestones, what done means, completion, and payment release.No findings
Why it is in this group
- The name "write_client_wording" says "write": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
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 beyond this wording and the facts in read_milestone_set.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false

Changes things 2Creates or changes something that can be changed back.Claude Code: ask

open_milestone_setOpen a draft milestone set for one client project.No findings
Why it is in this group
- The name "open_milestone_set" says "open": a word for a change.
Description, as the server wrote it
Open a draft milestone set for one client project. Draft definitions are not an approved commitment until approve_milestones.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
suggest_milestone_changeRecord a suggested change.No findings
Why it is in this group
- The input takes a statement or command to run (input.statement), which can change anything it can reach.
Description, as the server wrote it
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_work_item requires milestoneId and title. kind revise_client_wording requires wording.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false

Only reads 2Looks things up and changes nothing.Claude Code: allow

list_milestone_setsList the signed-in freelancer's milestone sets.No findings
Why it is in this group
- The name "list_milestone_sets" says "list": a word for reading.
Description, as the server wrote it
List the signed-in freelancer's milestone sets. Use a returned id with read_milestone_set. Do not guess a set.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
read_milestone_setRead the milestone set before answering.No findings
Why it is in this group
- The name "read_milestone_set" says "read": a word for reading.
Description, as the server wrote it
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 unless paymentReleased is true. Do not invent a deliverable. Do not mark unsaved work done. Proposed changes are not authorization.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http milestone https://milestone-continuity2.vercel.app/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__milestone__list_milestone_sets",
      "mcp__milestone__read_milestone_set"
    ],
    "ask": [
      "mcp__milestone__open_milestone_set",
      "mcp__milestone__suggest_milestone_change"
    ],
    "deny": [
      "mcp__milestone__define_milestone",
      "mcp__milestone__save_acceptance_criterion",
      "mcp__milestone__save_deliverable",
      "mcp__milestone__save_work_item",
      "mcp__milestone__record_criterion_met",
      "mcp__milestone__declare_milestone_complete",
      "mcp__milestone__declare_next_payment_released",
      "mcp__milestone__mark_work_done",
      "mcp__milestone__write_client_wording",
      "mcp__milestone__approve_milestones",
      "mcp__milestone__accept_milestone_change"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as milestone. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.github.LAHutchins91/milestone/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Anlyon alternative

13 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Compare with other servers for the same product.

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:17 UTC.

For agents: Markdown · JSON · report this listing