Scope by Ouroboros Apps
REMOTE · SCOPE-CONTINUITY2.VERCEL.APP
Freelance scope of work, rates, deadlines, and change orders for AI assistants
Available components
Last scanned (17 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 784 tokens (~87/item across 9 items; 9 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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://scope-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 scope-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://scope-continuity2.vercel.app/.well-known/oauth-protected-resource/mcp"
Bearer resource_metadata="https://scope-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://scope-continuity2.vercel.app/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://scope-continuity2.vercel.app/mcp |
| Authorisation server | https://bhisudppkapmmgvtturl.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://scope-continuity2.vercel.app/mcp | Verified | 200 | |
| http (plaintext) | http://scope-continuity2.vercel.app/mcp | HTTPS enforced | 308 | https://scope-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 →
approve_change_order approve change order ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| changeOrderId | – | yes | – |
| confirmed | boolean | yes | – |
| engagementId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
approve_scope approve scope ~50
Mark the current draft as the approved scope. Pass confirmed true only after the freelancer explicitly approves the current items, rates, and deadlines.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | – |
| engagementId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
create_engagement create engagement ~52
Create a draft engagement. Draft terms are not an approved commitment until approve_scope.
| Name | Type | Req | Description |
|---|---|---|---|
| clientName | string | yes | – |
| currency | string | yes | – |
| summary | string | – | – |
| title | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
file_change_order file change order ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amountMinor | integer | – | – |
| dueOn | string | – | – |
| engagementId | string | yes | – |
| kind | string | yes | – |
| rateCode | string | – | – |
| rateLabel | – | – | – |
| scopeItemId | – | – | – |
| summary | string | yes | – |
| unit | string | – | – |
| workDescription | string | – | – |
| workTitle | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
get_approved_record get approved record ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| engagementId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
list_engagements list engagements ~41
List the signed-in freelancer's engagements. Use a returned id with get_approved_record. Do not guess an engagement.
| Name | Type | Req | Description |
|---|---|---|---|
| offset | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
save_deadline save deadline ~54
Set or move the deadline for one scope item. The date is a calendar day in YYYY-MM-DD form.
| Name | Type | Req | Description |
|---|---|---|---|
| dueOn | string | yes | – |
| engagementId | string | yes | – |
| scopeItemId | – | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
save_rate save rate ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amountMinor | integer | yes | – |
| code | string | yes | – |
| engagementId | string | yes | – |
| label | string | yes | – |
| unit | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
save_scope_item save scope item ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | – |
| engagementId | string | yes | – |
| scopeItemId | – | – | – |
| title | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | – |
No examples provided.
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.
remote · scope-continuity2.vercel.app
claude mcp add --transport http lahutchins91-scope 'https://scope-continuity2.vercel.app/mcp'
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.