Home / MCP registry index / io.github.LAHutchins91/milestone

Milestone by Ouroboros Apps

io.github.LAHutchins91/milestone in the official MCP registry. Endpoint https://milestone-continuity2.vercel.app/mcp. Source: github.com/LAHutchins91/milestone-mcp.

The registry describes it as: Freelance project milestones and acceptance criteria for AI assistants

We read its 15 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

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

Cursor: ~/.cursor/mcp.json

{
  "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"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

list_milestone_sets open_milestone_set read_milestone_set define_milestone save_acceptance_criterion save_deliverable save_work_item record_criterion_met declare_milestone_complete declare_next_payment_released mark_work_done write_client_wording approve_milestones suggest_milestone_change accept_milestone_change

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-lahutchins91-milestone/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-lahutchins91-milestone)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.