@mrfentmen/linear-mcp

MCPcommunity
v1.1.2UnknownMITUpdated 3d agonpmGitHub

Query the Linear GraphQL API (key; set LINEAR_API_KEY, raw Authorization): viewer, teams, issue search.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
716Downloads/wk
3d agoLast update
Package
AuthorUnknown
LicenseMIT
Version1.1.2
Sourcenpm+mcp-registry
npm@mrfentmen/linear-mcp
GitHubmrfentmen/premium-mcps
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface12 tools · none privileged
Security scan✓ Cleanv1.1.2 · 2d agoHow well does this scan work?
EvalsNone
IndexedOct 3, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

12 tools · none privileged
Statically extracted from the published packagev1.1.2 · 2d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

meThe Linear user the API key belongs to.

The Linear user the API key belongs to.

No input schema was published for this tool.

list_teamsTeams in the workspace, with key and id.

Teams in the workspace, with key and id.

No input schema was published for this tool.

search_issuesSearch issues by text, e.g. login bug.

Search issues by text, e.g. login bug.

No input schema was published for this tool.

get_issueIssue details.

Issue details.

No input schema was published for this tool.

team_issuesIssues in a team.

Issues in a team.

No input schema was published for this tool.

list_projectsLinear projects.

Linear projects.

No input schema was published for this tool.

my_issuesAssigned to me.

Assigned to me.

No input schema was published for this tool.

list_labelsTeam labels.

Team labels.

No input schema was published for this tool.

create_issueCreate a REAL issue.

Create a REAL issue.

No input schema was published for this tool.

update_issue_titleRename a REAL issue.

Rename a REAL issue.

No input schema was published for this tool.

package_adoptionHow much an npm package is actually used and how recently it shipped: monthly download count, dist-tags, release cadence, deprecation count and maintainers. No Linear key needed.

How much an npm package is actually used and how recently it shipped: monthly download count, dist-tags, release cadence, deprecation count and maintainers. No Linear key needed.

No input schema was published for this tool.

project_scorecardThe OpenSSF scorecard for a repository: the aggregate supply-chain score and the individual checks behind it, worst first, with the reason each one gives.

The OpenSSF scorecard for a repository: the aggregate supply-chain score and the individual checks behind it, worst first, with the reason each one gives.

No input schema was published for this tool.

12 of 12 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Query the Linear GraphQL API (key; set LINEAR_API_KEY, raw Authorization): viewer, teams, issue search.

Keywords
mcplinearissuesprojectdev
Alternatives
Comparing tool surfaces…

Tools exposed

12 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-10-03 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in project management