# ScopeLinq (remote · mcp.scopelinq.com)

Reads what was agreed and answers whether a new request is Included, citing only confirmed lines.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `mcp.scopelinq.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-scopelinq-scopelinq/mcp.md), [page](https://verifymcp.io/servers/com-scopelinq-scopelinq/mcp)

## Channel facts

- Endpoint: `https://mcp.scopelinq.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-09-24.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 406 tokens (~203/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 ScopeLinq MCP server?

ScopeLinq is a hosted endpoint at https://mcp.scopelinq.com/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 com-scopelinq-scopelinq 'https://mcp.scopelinq.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-scopelinq-scopelinq": {
      "url": "https://mcp.scopelinq.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-scopelinq-scopelinq": {
      "type": "http",
      "url": "https://mcp.scopelinq.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-scopelinq-scopelinq]
url = "https://mcp.scopelinq.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-scopelinq-scopelinq": {
      "type": "remote",
      "url": "https://mcp.scopelinq.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-scopelinq-scopelinq --url 'https://mcp.scopelinq.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-scopelinq-scopelinq:
    url: "https://mcp.scopelinq.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-scopelinq-scopelinq": {
      "Transport": "http",
      "Url": "https://mcp.scopelinq.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-scopelinq-scopelinq -t streamable-http -u 'https://mcp.scopelinq.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-scopelinq-scopelinq": {
      "type": "http",
      "url": "https://mcp.scopelinq.com/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-09-24 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-15 (score 74)

First indexed and scored.

## MCP tools (2)

### `draft_scope_record` (~176 tokens)

Read what was agreed

Reads a proposal, quote, estimate, contract, or email thread and returns the terms it actually states, each traced to the words it came from. Works for whoever sent the document or whoever received it. Pass the text exactly as written — do not summarise it first. Remove names, email addresses and account numbers before pasting. Returns two lists: `lines` (found in the text) and `not_found_in_text` (things the text does not clearly say). Show both to the person and ask which lines they agree were agreed, then call check_scope_change with only those. The text is processed by an AI model to produce the lines and is deleted within 24 hours. Free, no account.

Input parameters:

- `agreement_text` (string, required): The proposal, quote, estimate, contract, or thread, pasted as written.

Output parameters:

- `confidence` (number|null)
- `format` (string)
- `lines` (array)
- `lines_hash` (string)
- `next_step` (string)
- `no_terms` (boolean)
- `not_found_in_text` (array)
- `parties` (null)
- `status` (string)
- `version` (string)

### `check_scope_change` (~146 tokens)

Check a request against what was agreed

Answers whether a new request is Included, Additional work, or Needs clarification, citing one of the confirmed lines. Only pass lines the person has confirmed were agreed. Never pass lines from not_found_in_text unless the person confirmed them, and never pass the original document — there is no field for it. If no lines have been confirmed yet, call draft_scope_record first and ask the person. Works for whoever sent the document or whoever received it. Free, no account.

Input parameters:

- `confirmed_lines` (array, required): Lines the person confirmed were agreed — from draft_scope_record, or in their own words.
- `request_text` (string, required): The new request, in the words it was made.

Output parameters:

- `cited_line`
- `confidence` (integer)
- `label` (string)
- `rationale` (string|null)
- `suggested_reply` (string|null)
- `verdict` (string)

## Diagnostics

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

## Score history

- 2026-09-24: 78
- 2026-09-23: 77
- 2026-09-22: 77
- 2026-09-21: 76
- 2026-09-20: 76
- 2026-09-19: 76
- 2026-09-18: 75
- 2026-09-17: 75
- 2026-09-16: 74
- 2026-09-15: 74

## Common questions

### What is the ScopeLinq MCP server?

ScopeLinq is an MCP server listed in the public MCP registry as com.scopelinq/scopelinq. Reads what was agreed and answers whether a new request is Included, citing only confirmed lines. This page covers its hosted endpoint (https://mcp.scopelinq.com/mcp).

### Is the ScopeLinq MCP server safe to use?

ScopeLinq scores 78 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 ScopeLinq MCP server expose?

ScopeLinq exposes 2 tools: draft_scope_record, check_scope_change. Their descriptions and schemas cost roughly 322 tokens of context every time the server is loaded.

### Does the ScopeLinq MCP server require authentication?

No. We connected to ScopeLinq without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ScopeLinq MCP server still maintained?

ScopeLinq is still listed as active in the MCP registry. We last reached this channel on 24 September 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://mcp.scopelinq.com/mcp
- Website: https://scopelinq.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-scopelinq-scopelinq/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-scopelinq-scopelinq/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-scopelinq-scopelinq/mcp