# Scope by Ouroboros Apps (remote · scope-continuity2.vercel.app)

Freelance scope of work, rates, deadlines, and change orders for AI assistants

- Trust score: 89/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `scope-continuity2.vercel.app`: 89/100 (this document), [markdown](https://verifymcp.io/servers/lahutchins91-scope/scope-continuity2.md), [page](https://verifymcp.io/servers/lahutchins91-scope/scope-continuity2)

## Channel facts

- Endpoint: `https://scope-continuity2.vercel.app/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 784 tokens (~87/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Scope by Ouroboros Apps MCP server?

Scope by Ouroboros Apps is a hosted endpoint at https://scope-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.

### Claude

```bash
claude mcp add --transport http lahutchins91-scope 'https://scope-continuity2.vercel.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "lahutchins91-scope": {
      "url": "https://scope-continuity2.vercel.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lahutchins91-scope": {
      "type": "http",
      "url": "https://scope-continuity2.vercel.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.lahutchins91-scope]
url = "https://scope-continuity2.vercel.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "lahutchins91-scope": {
      "type": "remote",
      "url": "https://scope-continuity2.vercel.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add lahutchins91-scope --url 'https://scope-continuity2.vercel.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  lahutchins91-scope:
    url: "https://scope-continuity2.vercel.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "lahutchins91-scope": {
      "Transport": "http",
      "Url": "https://scope-continuity2.vercel.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add lahutchins91-scope -t streamable-http -u 'https://scope-continuity2.vercel.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "lahutchins91-scope": {
      "type": "http",
      "url": "https://scope-continuity2.vercel.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 89, 0)

- [security] Stability: 0.97 → pass

### 2026-11-03 (score 89, +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.

### 2026-10-31 (score 88, +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.

### 2026-10-29 (score 87, +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.

### 2026-10-27 (score 86, +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.

### 2026-10-25 (score 85, +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.

### 2026-10-23 (score 84, +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.

### 2026-10-21 (score 83, +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.

## MCP tools (9)

### `list_engagements` (~41 tokens)

list engagements

List the signed-in freelancer's engagements. Use a returned id with get_approved_record. Do not guess an engagement.

Input parameters:

- `offset` (integer)

Output parameters:

- `data`

### `create_engagement` (~52 tokens)

create engagement

Create a draft engagement. Draft terms are not an approved commitment until approve_scope.

Input parameters:

- `clientName` (string, required)
- `currency` (string, required)
- `summary` (string)
- `title` (required)

Output parameters:

- `data`

### `get_approved_record` (~58 tokens)

get approved record

Read the approved scope, rates, deadlines, and change orders before answering. Quote only this record. Draft status is not an approved commitment. Proposed change orders do not authorize a discount or extra work.

Input parameters:

- `engagementId` (string, required)

Output parameters:

- `data`

### `save_scope_item` (~72 tokens)

save scope item

Add or update a scope item the freelancer has accepted. After approval, a new item is refused until approve_change_order adds that work. Renaming approved work is refused.

Input parameters:

- `description` (string, required)
- `engagementId` (string, required)
- `scopeItemId`
- `title` (string, required)

Output parameters:

- `data`

### `save_rate` (~93 tokens)

save rate

Set a draft rate, or update an approved rate without lowering it or changing its unit. A lower amount is a discount and is refused. A new rate code after approval is refused. Use file_change_order and approve_change_order for those.

Input parameters:

- `amountMinor` (integer, required)
- `code` (string, required)
- `engagementId` (string, required)
- `label` (string, required)
- `unit` (string, required)

Output parameters:

- `data`

### `save_deadline` (~54 tokens)

save deadline

Set or move the deadline for one scope item. The date is a calendar day in YYYY-MM-DD form.

Input parameters:

- `dueOn` (string, required)
- `engagementId` (string, required)
- `scopeItemId` (required)

Output parameters:

- `data`

### `approve_scope` (~50 tokens)

approve scope

Mark the current draft as the approved scope. Pass confirmed true only after the freelancer explicitly approves the current items, rates, and deadlines.

Input parameters:

- `confirmed` (boolean, required)
- `engagementId` (string, required)

Output parameters:

- `data`

### `file_change_order` (~158 tokens)

file change order

Record a proposed change order. This does not change scope, rates, or deadlines. kind add_work requires workTitle and workDescription. kind discount_rate requires rateCode and a lower amountMinor. kind add_rate requires rateCode, rateLabel, amountMinor, and unit. kind move_deadline requires scopeItemId and dueOn.

Input parameters:

- `amountMinor` (integer)
- `dueOn` (string)
- `engagementId` (string, required)
- `kind` (string, required)
- `rateCode` (string)
- `rateLabel`
- `scopeItemId`
- `summary` (string, required)
- `unit` (string)
- `workDescription` (string)
- `workTitle` (string)

Output parameters:

- `data`

### `approve_change_order` (~75 tokens)

approve change order

Apply one proposed change order after the freelancer explicitly approves that order. Pass confirmed true only then. This is the path that may discount a rate or add work. Calling it is not a substitute for the freelancer's approval.

Input parameters:

- `changeOrderId` (required)
- `confirmed` (boolean, required)
- `engagementId` (string, required)

Output parameters:

- `data`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/lahutchins91-scope/scope-continuity2#diagnostics

## Score history

- 2026-11-04: 89
- 2026-11-03: 89
- 2026-11-02: 88
- 2026-11-01: 88
- 2026-10-31: 88
- 2026-10-30: 87
- 2026-10-29: 87
- 2026-10-28: 86
- 2026-10-27: 86
- 2026-10-26: 85
- 2026-10-25: 85
- 2026-10-24: 84
- 2026-10-23: 84
- 2026-10-22: 83
- 2026-10-21: 83
- 2026-10-20: 82
- 2026-10-19: 82
- 2026-10-18: 81
- 2026-10-17: 81
- 2026-10-16: 81
- 2026-10-15: 80
- 2026-10-14: 80
- 2026-10-13: 79
- 2026-10-12: 79
- 2026-10-10: 78
- 2026-10-07: 76

## Common questions

### What is the Scope by Ouroboros Apps MCP server?

Scope by Ouroboros Apps is an MCP server listed in the public MCP registry as io.github.LAHutchins91/scope. Freelance scope of work, rates, deadlines, and change orders for AI assistants. This page covers its hosted endpoint (https://scope-continuity2.vercel.app/mcp).

### Is the Scope by Ouroboros Apps MCP server safe to use?

Scope 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 Scope by Ouroboros Apps MCP server expose?

Scope by Ouroboros Apps exposes 9 tools: list_engagements, create_engagement, get_approved_record, save_scope_item, save_rate, and 4 more. Their descriptions and schemas cost roughly 653 tokens of context every time the server is loaded.

### Does the Scope by Ouroboros Apps MCP server require authentication?

Yes. Scope 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 Scope by Ouroboros Apps MCP server still maintained?

Scope 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.

## Links

- Remote endpoint: https://scope-continuity2.vercel.app/mcp
- Repository: https://github.com/LAHutchins91/scope-mcp
- Website: https://ouroborosapps.com/docs/scope
- Changelog RSS feed: https://verifymcp.io/servers/lahutchins91-scope/scope-continuity2.xml
- Changelog JSON feed: https://verifymcp.io/servers/lahutchins91-scope/scope-continuity2.json
- HTML version of this page: https://verifymcp.io/servers/lahutchins91-scope/scope-continuity2