Milestone by Ouroboros Apps
REMOTE · MILESTONE-CONTINUITY2.VERCEL.APP
Freelance project milestones and acceptance criteria for AI assistants
Available components
Last scanned (19 hours ago)
Scores higher than 97% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Project Management
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1300 tokens (~86/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Stability: 0.97 → pass security
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://milestone-continuity2.vercel.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 9c5f0e6a35c955e113044c86848e4cd5 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of milestone-continuity2.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://milestone-continuity2.vercel.app/.well-known/oauth-protected-resource/mcp"
Bearer resource_metadata="https://milestone-continuity2.vercel.app/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Protected resource metadata
| Document | https://milestone-continuity2.vercel.app/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://milestone-continuity2.vercel.app/mcp |
| Authorisation server | https://hbrrrrrelxcutkdaqlgf.supabase.co/auth/v1 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://milestone-continuity2.vercel.app/mcp | Verified | 200 | |
| http (plaintext) | http://milestone-continuity2.vercel.app/mcp | HTTPS enforced | 308 | https://milestone-continuity2.vercel.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
accept_milestone_change accept milestone change ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| changeId | – | yes | – |
| confirmed | boolean | yes | – |
| milestoneSetId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
approve_milestones approve milestones ~54
Approve the draft milestone definitions and acceptance criteria. Pass confirmed true only after the freelancer explicitly approves them. A draft is not a commitment.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | – |
| milestoneSetId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
declare_milestone_complete declare milestone complete ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| milestoneId | – | yes | – |
| milestoneSetId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
declare_next_payment_released declare next payment released ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| milestoneId | – | yes | – |
| milestoneSetId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
define_milestone define milestone ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| definition | string | yes | – |
| milestoneSetId | string | yes | – |
| title | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
list_milestone_sets list milestone sets ~44
List the signed-in freelancer's milestone sets. Use a returned id with read_milestone_set. Do not guess a set.
| Name | Type | Req | Description |
|---|---|---|---|
| offset | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
mark_work_done mark work done ~56
Mark one saved work item done. Refuses when the work item was not saved. Do not mark unsaved work done.
| Name | Type | Req | Description |
|---|---|---|---|
| milestoneId | – | yes | – |
| milestoneSetId | string | yes | – |
| workItemId | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
open_milestone_set open milestone set ~55
Open a draft milestone set for one client project. Draft definitions are not an approved commitment until approve_milestones.
| Name | Type | Req | Description |
|---|---|---|---|
| clientName | string | yes | – |
| projectTitle | – | yes | – |
| reference | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
read_milestone_set read milestone set ~95
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.
| Name | Type | Req | Description |
|---|---|---|---|
| milestoneSetId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
record_criterion_met record criterion met ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| criterionId | – | yes | – |
| milestoneId | – | yes | – |
| milestoneSetId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
save_acceptance_criterion save acceptance criterion ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| milestoneId | – | yes | – |
| milestoneSetId | string | yes | – |
| statement | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
save_deliverable save deliverable ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | yes | – |
| milestoneId | – | yes | – |
| milestoneSetId | string | yes | – |
| title | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
save_work_item save work item ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| milestoneId | – | yes | – |
| milestoneSetId | string | yes | – |
| title | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
suggest_milestone_change suggest milestone change ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| definition | string | – | – |
| detail | string | – | – |
| kind | string | yes | – |
| milestoneId | – | – | – |
| milestoneSetId | string | yes | – |
| statement | string | – | – |
| summary | string | yes | – |
| title | string | – | – |
| wording | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
write_client_wording write client wording ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| milestoneSetId | string | yes | – |
| wording | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
How do I install the Milestone by Ouroboros Apps MCP server?
Milestone by Ouroboros Apps is a hosted endpoint at https://milestone-continuity2.vercel.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · milestone-continuity2.vercel.app
claude mcp add --transport http lahutchins91-milestone 'https://milestone-continuity2.vercel.app/mcp'
What is the Milestone by Ouroboros Apps MCP server?
Milestone by Ouroboros Apps is an MCP server listed in the public MCP registry as io.github.LAHutchins91/milestone. Freelance project milestones and acceptance criteria for AI assistants. This page covers its hosted endpoint (https://milestone-continuity2.vercel.app/mcp).
Is the Milestone by Ouroboros Apps MCP server safe to use?
Milestone by Ouroboros Apps scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Milestone by Ouroboros Apps MCP server expose?
Milestone by Ouroboros Apps exposes 15 tools: list_milestone_sets, open_milestone_set, read_milestone_set, define_milestone, save_acceptance_criterion, and 10 more. Their descriptions and schemas cost roughly 1,117 tokens of context every time the server is loaded.
Does the Milestone by Ouroboros Apps MCP server require authentication?
Yes. Milestone by Ouroboros Apps asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Milestone by Ouroboros Apps MCP server still maintained?
Milestone by Ouroboros Apps is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.