io.usefulapi/linear
REMOTE · LINEAR.USEFULAPI.IO · SCANNED SEP 20
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 → Why this is hard to score →
Endpoint Security78
- 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 enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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
- 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 Usability84
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 708 tokens (~88/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/linear MCP server?
io.usefulapi/linear is a hosted endpoint at https://linear.usefulapi.io/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 · linear.usefulapi.io
claude mcp add --transport http io-usefulapi-linear 'https://linear.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-linear": {
"url": "https://linear.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-linear": {
"type": "http",
"url": "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": {
"Transport": "http",
"Url": "https://linear.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-linear -t streamable-http -u '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.
- 20 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 19 Sept 26 +55
- Transport: unverified → pass ▲ security
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Destructive annotations: pass functional
- Schema quality: good → excellent functional
- 16 Sept 26 0
- Transport: fail → unverified ▼ security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: pass → unverified ▼ security
- Stability: 0.20 → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 2 Aug 26 0
- 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 0
- 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
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 20 Sept 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 | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | e611de27a4474faa13fc5e4a36098ed0 |
| 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 |
Background: What to check on a remote MCP endpoint →
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 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 realm="OAuth", resource_metadata="https://linear.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://linear.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://linear.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://linear.usefulapi.io/mcp |
| Authorisation server | https://linear.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://linear.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://linear.usefulapi.io/mcp | Inconclusive | 401 |
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 →
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.
What is the io.usefulapi/linear MCP server?
io.usefulapi/linear is an MCP server listed in the public MCP registry as io.usefulapi/linear. Search, read and create Linear issues, projects, teams and cycles. This page covers its hosted endpoint (https://linear.usefulapi.io/mcp).
Is the io.usefulapi/linear MCP server safe to use?
io.usefulapi/linear scores 73 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 io.usefulapi/linear MCP server expose?
io.usefulapi/linear exposes 8 tools: linear_search_issues, linear_get_issue, linear_list_teams, linear_list_projects, linear_my_issues, and 3 more. Their descriptions and schemas cost roughly 708 tokens of context every time the server is loaded.
Does the io.usefulapi/linear MCP server require authentication?
Yes. io.usefulapi/linear 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 io.usefulapi/linear MCP server still maintained?
io.usefulapi/linear is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.