Skip to content

Linear MCP by usefulapi

io.usefulapi/linearusefulapi.iostreamable-httpv1.40.5Scanned

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

8 tools: 2 change things and 6 only read.

Tools: 0 delete, 0 irreversible, 2 write, 6 read.
  • Reads private data · 1
  • Reads text others write · 8
  • Can send data out · 2
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Linear MCP by usefulapi can do

The Linear MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 8 tools. It can create or change data (2 tools: linear_create_issue and linear_add_comment), but cannot delete data. 6 tools only read.

1 tool reads private data (linear_search_issues); 8 tools bring in text other people can write (linear_search_issues, linear_get_issue, linear_list_teams and 5 more); 2 tools can send data out of your system (linear_create_issue and linear_add_comment). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.40.5.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 2Claude Code: ask
  • linear_add_comment⚠[U+FE0F] WRITE / MUTATING: posts a comment on an issue.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "linear_add_comment" says "add": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "linear_add_comment" says "add" and "comment": it writes something other people read.
    Description, as the server wrote itContains invisible characters, shown as [U+…]
    ⚠[U+FE0F] WRITE / MUTATING: posts a comment on an issue. Requires the issueId (UUID) and a markdown body. GraphQL: mutation commentCreate.

    Annotations the server declares

    • title: Add comment (WRITE — mutates Linear)
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
  • linear_create_issue⚠[U+FE0F] WRITE / MUTATING: creates a new issue in Linear.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "linear_create_issue" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "linear_create_issue" says "create" and "issue": it writes something other people read.
    Description, as the server wrote itContains invisible characters, shown as [U+…]
    ⚠[U+FE0F] 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.

    Annotations the server declares

    • title: Create issue (WRITE — mutates Linear)
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
Only reads 6Show 6 read-only tools
  • linear_get_issueFetch a single issue by its UUID or human identifier (e.g.Reads text others writeNo findings

    Why it is in this group

    • The name "linear_get_issue" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "linear_get_issue" says "get" and "issue": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "fetch" and "issue": it reads issues, which other people can write.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Get one issue
    • readOnlyHint: true
    • openWorldHint: true
  • linear_list_cyclesList cycles (sprints), optionally scoped to a team by key, with number, name and start/end dates.Reads text others writeNo findings

    Why it is in this group

    • The name "linear_list_cycles" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List cycles (sprints), optionally scoped to a team by key, with number, name and start/end dates. Read-only. GraphQL: query cycles(filter).

    Annotations the server declares

    • title: List cycles
    • readOnlyHint: true
    • openWorldHint: true
  • linear_list_projectsList projects in the workspace (id, name, state, progress, target date).Reads text others writeNo findings

    Why it is in this group

    • The name "linear_list_projects" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    List projects in the workspace (id, name, state, progress, target date). Read-only. GraphQL: query projects.

    Annotations the server declares

    • title: List projects
    • readOnlyHint: true
    • openWorldHint: true
  • linear_list_teamsList the teams in the workspace (id, key, name).Reads text others writeNo findings

    Why it is in this group

    • The name "linear_list_teams" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List teams
    • readOnlyHint: true
    • openWorldHint: true
  • linear_my_issuesList issues assigned to the current user (the API key's owner / OAuth actor) via viewer.assignedIssues.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "linear_my_issues" says "issue": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "list" and "issue": it reads issues, which other people can write.
    Description, as the server wrote it
    List issues assigned to the current user (the API key's owner / OAuth actor) via viewer.assignedIssues. Read-only. GraphQL: query viewer { assignedIssues }.

    Annotations the server declares

    • title: My assigned issues
    • readOnlyHint: true
    • openWorldHint: true
  • linear_search_issuesFind issues, optionally filtered by a text query (matches title), team key, workflow-state name, or assignee email.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "linear_search_issues" says "search": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "find" and "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "linear_search_issues" says "search" and "issue": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "find" and "issue": it reads issues, which other people can write.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Search / filter issues
    • readOnlyHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

16 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write8
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__linear__linear_search_issues"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:36 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://linear.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://linear.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://linear.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://linear.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.5. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__linear__linear_search_issues",
      "mcp__linear__linear_get_issue",
      "mcp__linear__linear_list_teams",
      "mcp__linear__linear_list_projects",
      "mcp__linear__linear_my_issues",
      "mcp__linear__linear_list_cycles"
    ],
    "ask": [
      "mcp__linear__linear_create_issue",
      "mcp__linear__linear_add_comment"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as linear. Review it before you use it.

Capability tags behind 8 rules
  • mcp__linear__linear_search_issues private-data, untrusted-input
  • mcp__linear__linear_get_issue untrusted-input
  • mcp__linear__linear_list_teams untrusted-input
  • mcp__linear__linear_list_projects untrusted-input
  • mcp__linear__linear_my_issues untrusted-input
  • mcp__linear__linear_list_cycles untrusted-input
  • mcp__linear__linear_create_issue untrusted-input, outbound
  • mcp__linear__linear_add_comment untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/linear/verify?hash=bc577262175d7f54998f2aa2e6327b10e0bfb8b1fcb9999912a2cb71b57b203b" | jq -e '.changed == false'

Pinned hash bc577262175d, from Oct 25, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/linear/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/linear
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/linear.svg)](https://radar.anlyon.com/servers/io.usefulapi/linear)

Source: MCP Registry · repository. Synced Nov 20, 2026, 20:18 UTC.

Linear MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Linear MCP by usefulapi safe?

No scan can promise that. What its definitions show: 8 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Linear MCP by usefulapi delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Linear MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Linear MCP by usefulapi have?

8 tools: 2 write, 6 read. linear_create_issue, linear_add_comment, linear_search_issues, linear_get_issue, linear_list_teams, linear_list_projects, linear_my_issues and linear_list_cycles.

Does the Linear MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Linear MCP by usefulapi send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): linear_create_issue and linear_add_comment.

Has the Linear MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.