Skip to content

Milestone by Ouroboros Apps MCP server

io.github.LAHutchins91/milestoneLAHutchins91streamable-httpv1.0.3Scanned

Freelance project milestones and acceptance criteria for AI assistants

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

Tools: 11 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

11 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Milestone by Ouroboros Apps MCP server can do

The Milestone by Ouroboros Apps MCP server is published by the GitHub account LAHutchins91. It has 15 tools. It can delete or cancel things (11 tools: define_milestone, save_acceptance_criterion, save_deliverable, save_work_item and 7 more) and create or change data (2 tools: open_milestone_set and suggest_milestone_change). 2 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 16, 2026, version 1.0.3.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

15 tools

Deletes or cancels 11Claude 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 2Claude 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 2Show 2 read-only tools
  • 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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:58 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
13
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://milestone-continuity2.vercel.app/.well-known/oauth-protected-resource/mcp
Authorization servers
https://hbrrrrrelxcutkdaqlgf.supabase.co/auth/v1
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 13 tools that change things (11 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://milestone-continuity2.vercel.app/mcp: tools/list returned 15 tools to an anonymous client, including define_milestone (destructive), save_acceptance_criterion (destructive), save_deliverable (destructive), save_work_item (destructive), record_criterion_met (destructive) and 8 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

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
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 or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as milestone. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.LAHutchins91/milestone/verify?hash=70342f646944b7ac1e1a65a59846242eae0faf92c40c3a3795f0e8e0f2a6241b" | jq -e '.changed == false'

Pinned hash 70342f646944, from Nov 16, 2026, 00:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

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

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

Badge

Anlyon Radar badge for io.github.LAHutchins91/milestone
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.LAHutchins91/milestone.svg)](https://radar.anlyon.com/servers/io.github.LAHutchins91/milestone)

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

Milestone by Ouroboros Apps MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Milestone by Ouroboros Apps MCP server safe?

No scan can promise that. What its definitions show: 15 tools, 13 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Milestone by Ouroboros Apps MCP server delete data?

Yes. 11 tools can delete, cancel or revoke something: define_milestone, save_acceptance_criterion, save_deliverable, save_work_item, record_criterion_met, declare_milestone_complete and 5 more.

Can the Milestone by Ouroboros Apps MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Milestone by Ouroboros Apps MCP server have?

15 tools: 11 destructive, 2 write, 2 read. define_milestone, save_acceptance_criterion, save_deliverable, save_work_item, record_criterion_met, declare_milestone_complete, declare_next_payment_released, mark_work_done and 7 more.

Does the Milestone by Ouroboros Apps MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Milestone by Ouroboros Apps MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Milestone by Ouroboros Apps MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.