# io.usefulapi/linear (remote · linear.usefulapi.io)

Search, read and create Linear issues, projects, teams and cycles.

- Trust score: 18/100 (low)
- Change this week: −51
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `linear.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-linear/linear.md), [page](https://verifymcp.io/servers/io-usefulapi-linear/linear)

## Channel facts

- Endpoint: `https://linear.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 429.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 4 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add --transport http io-usefulapi-linear https://linear.usefulapi.io/mcp
```

### Codex

```toml
[mcp_servers.io-usefulapi-linear]
url = "https://linear.usefulapi.io/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add io-usefulapi-linear --url https://linear.usefulapi.io/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-linear:
    url: "https://linear.usefulapi.io/mcp"
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-linear": {
      "type": "http",
      "url": "https://linear.usefulapi.io/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-08-03 (score 18, −54)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Authorization: pass → unverified
- [security regression] Stability: 0.20 → unverified
- [security regression] Transport: pass → fail
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: fail → unverified

### 2026-08-02 (score 72, +54)

- [security improvement] Authorization: unverified → pass
- [security improvement] Transport: fail → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.20

### 2026-08-01 (score 18, −53)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.13 → unverified
- [security regression] Authorization: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-07-31 (score 71, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 68, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 70, +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-07-28 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-27 (score 69, +47)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (8)

### `linear_search_issues` (~141 tokens)

Search / filter issues

Find issues, optionally filtered by a text query (matches title), team key, workflow-state name, or assignee email. Read-only. GraphQL: query issues(filter, first).

Input parameters:

- `assigneeEmail` (string): Filter to issues assigned to this user email.
- `first` (integer): Max issues to return. Default 25.
- `query` (string): Free text to match against issue titles (containsIgnoreCase).
- `state` (string): Workflow-state name, e.g. "In Progress", "Todo", "Done".
- `teamKey` (string): Team key, e.g. "ENG". Filters to that team.

### `linear_get_issue` (~65 tokens)

Get one issue

Fetch a single issue by its UUID or human identifier (e.g. "ENG-123"), including description, state, assignee and recent comments. Read-only. GraphQL: query issue(id).

Input parameters:

- `id` (string, required): Issue UUID or identifier like "ENG-123".

### `linear_list_teams` (~64 tokens)

List teams

List the teams in the workspace (id, key, name). Use a team's id for linear_create_issue or its key for linear_search_issues. Read-only. GraphQL: query teams.

Input parameters:

- `first` (integer): Max teams to return. Default 50.

### `linear_list_projects` (~50 tokens)

List projects

List projects in the workspace (id, name, state, progress, target date). Read-only. GraphQL: query projects.

Input parameters:

- `first` (integer): Max projects to return. Default 50.

### `linear_my_issues` (~61 tokens)

My assigned issues

List issues assigned to the current user (the API key's owner / OAuth actor) via viewer.assignedIssues. Read-only. GraphQL: query viewer { assignedIssues }.

Input parameters:

- `first` (integer): Max issues to return. Default 25.

### `linear_list_cycles` (~80 tokens)

List cycles

List cycles (sprints), optionally scoped to a team by key, with number, name and start/end dates. Read-only. GraphQL: query cycles(filter).

Input parameters:

- `first` (integer): Max cycles to return. Default 25.
- `teamKey` (string): Team key, e.g. "ENG", to scope cycles to one team.

### `linear_create_issue` (~165 tokens)

Create issue (WRITE — mutates Linear)

⚠️ WRITE / MUTATING: creates a new issue in Linear. Requires a teamId (from linear_list_teams) and a title. Optional description (markdown), priority (0=none,1=urgent,2=high,3=medium,4=low), and assigneeId. GraphQL: mutation issueCreate.

Input parameters:

- `assigneeId` (string): UUID of the user to assign the issue to.
- `description` (string): Issue body in markdown.
- `priority` (integer): 0 none, 1 urgent, 2 high, 3 medium, 4 low.
- `teamId` (string, required): UUID of the team to create the issue in (from linear_list_teams).
- `title` (string, required): Issue title.

### `linear_add_comment` (~82 tokens)

Add comment (WRITE — mutates Linear)

⚠️ WRITE / MUTATING: posts a comment on an issue. Requires the issueId (UUID) and a markdown body. GraphQL: mutation commentCreate.

Input parameters:

- `body` (string, required): Comment text in markdown.
- `issueId` (string, required): UUID of the issue to comment on (the `id` field, not the ENG-123 identifier).

## Diagnostics

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

## Score history

- 2026-08-03: 18
- 2026-08-02: 72
- 2026-08-01: 18
- 2026-07-31: 71
- 2026-07-30: 68
- 2026-07-29: 70
- 2026-07-28: 69
- 2026-07-27: 69
- 2026-07-26: 22

## Links

- Remote endpoint: https://linear.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-linear/linear/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-linear/linear/changelog.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-linear/linear