io.usefulapi/linear
REMOTE · LINEAR.USEFULAPI.IO · SCANNED AUG 3
Search, read and create Linear issues, projects, teams and cycles.
Available components
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 →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 429. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · linear.usefulapi.io
claude mcp add --transport http io-usefulapi-linear https://linear.usefulapi.io/mcp
[mcp_servers.io-usefulapi-linear] url = "https://linear.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-linear": {
"type": "remote",
"url": "https://linear.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-linear --url https://linear.usefulapi.io/mcp --transport streamable-http
mcp_servers:
io-usefulapi-linear:
url: "https://linear.usefulapi.io/mcp" {
"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.
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.
- 3 Aug 26 −54
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.20 → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- 2 Aug 26 +54
- Authorization: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.20 ▲ functional
- 1 Aug 26 −53
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.13 → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 28 Jul 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 Jul 26 +47
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 3 Aug 2026 · Probed https://linear.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 16 Jul 2026 | 14 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 4e1ad55a5aa200880e0bbd2671024590 |
| SANs: usefulapi.io, linear.usefulapi.io, *.linear.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of linear.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 429 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://linear.usefulapi.io/mcp | HTTP error | 429 | |
| http (plaintext) | http://linear.usefulapi.io/mcp | Inconclusive | 429 |
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.
linear_add_comment Add comment (WRITE — mutates Linear) ~82
⚠️ WRITE / MUTATING: posts a comment on an issue. Requires the issueId (UUID) and a markdown body. GraphQL: mutation commentCreate.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | Comment text in markdown. |
| issueId | string | yes | UUID of the issue to comment on (the `id` field, not the ENG-123 identifier). |
No output schema declared.
No examples provided.
linear_create_issue Create issue (WRITE — mutates Linear) ~165
⚠️ 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | UUID of the team to create the issue in (from linear_list_teams). |
| title | string | yes | Issue title. |
No output schema declared.
No examples provided.
linear_get_issue Get one issue ~65
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).
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Issue UUID or identifier like "ENG-123". |
No output schema declared.
No examples provided.
linear_list_cycles List cycles ~80
List cycles (sprints), optionally scoped to a team by key, with number, name and start/end dates. Read-only. GraphQL: query cycles(filter).
| Name | Type | Req | Description |
|---|---|---|---|
| first | integer | — | Max cycles to return. Default 25. |
| teamKey | string | — | Team key, e.g. "ENG", to scope cycles to one team. |
No output schema declared.
No examples provided.
linear_list_projects List projects ~50
List projects in the workspace (id, name, state, progress, target date). Read-only. GraphQL: query projects.
| Name | Type | Req | Description |
|---|---|---|---|
| first | integer | — | Max projects to return. Default 50. |
No output schema declared.
No examples provided.
linear_list_teams List teams ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| first | integer | — | Max teams to return. Default 50. |
No output schema declared.
No examples provided.
linear_my_issues My assigned issues ~61
List issues assigned to the current user (the API key's owner / OAuth actor) via viewer.assignedIssues. Read-only. GraphQL: query viewer { assignedIssues }.
| Name | Type | Req | Description |
|---|---|---|---|
| first | integer | — | Max issues to return. Default 25. |
No output schema declared.
No examples provided.
linear_search_issues Search / filter issues ~141
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.