Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.lineai-intelligence/lineai-mcp-server

PYPI · LINEAI-MCP-SERVER

An MCP Server to utilize Lineai's rich software dependency data in your AI programming assistant.

Available components

0 this week 66 Trust /100

Last scanned (19 hours ago)

Scores higher than 58% of PyPI servers

Category Code Search and Documentation

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MPL-2.0).Pass
  • Actively maintained (last published 38 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability56
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1796 tokens (~224/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 67% of tool parameters carry a description.Partial
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 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (15)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 20 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
    • Stability: 0.97 → pass security
  • 19 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 13 Nov 26 +1
    • Stability: 0.97 → pass security
  • 11 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 6 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 21 Nov 2026 · Analysed pypi/lineai-mcp-server@1.4.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 29 packages
Packages resolved 29
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~1,611 tokens

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 →

Tool Tokens
lineai-database-impact ~259

Analyze impacts between code and database entities. Scope resolution precedence: explicit `materialized_view_id` -> `workspace` (name) -> `LINEAI_WORKSPACE_NAME` environment variable -> the server's default workspace's latest materialized view (nothing specified is never an error while a default view exists). Unresolved references found in the impact graphs are reported in a dedicated 'Unresolved References' section as dependency indicators. Recommended workflow: 1. Use this tool before implementing code or database changes 2. Search for the relevant database entity 3. Review the impact analysis to understand which code depends on this database object and vice versa Particularly crucial when AI-suggested modifications are being considered or when modifying SQL code.

NameTypeReqDescription
entity_typestringyesType of database entity to search for (column, table, or view)
materialized_view_idstring–Optional materialized view id; takes precedence over `workspace`
namestringyesName of the database entity to search for
table_or_viewstring–Name of the table or view containing the column (required for columns only)
workspacestring–Optional workspace (materialized view definition) name; overrides LINEAI_WORKSPACE_NAME

No output schema declared.

No examples provided.

lineai-graph-capabilities ~155

Fetch graph API capabilities/manifest from the Lineai server (GET). Returns label and relationship metadata when the graph tier is deployed; otherwise explains missing routes. Scope resolution precedence: explicit `materialized_view_id` -> `workspace` (name) -> `LINEAI_WORKSPACE_NAME` environment variable -> the server's default workspace's latest materialized view (nothing specified is never an error while a default view exists).

NameTypeReqDescription
materializedViewIdstring–Alias for materialized_view_id
materialized_view_idstring–Optional materialized view id; takes precedence over `workspace`
workspacestring–Optional workspace (materialized view definition) name; overrides LINEAI_WORKSPACE_NAME

No output schema declared.

No examples provided.

lineai-graph-impact ~187

Bounded graph impact from seed node ids (curated HTTP API). Optional `direction` (upstream|downstream|both), `depth`, `scan_space`, `workspace`, `materialized_view_id`. Scope resolution precedence: explicit `materialized_view_id` -> `workspace` (name) -> `LINEAI_WORKSPACE_NAME` environment variable -> the server's default workspace's latest materialized view (nothing specified is never an error while a default view exists).

NameTypeReqDescription
depthinteger––
directionstring––
materialized_view_idstring–Optional materialized view id; takes precedence over `workspace`
scan_spacestring––
seed_node_idsarrayyesGraph node ids to expand from
workspacestring–Optional workspace (materialized view definition) name; overrides LINEAI_WORKSPACE_NAME

No output schema declared.

No examples provided.

lineai-graph-owners ~158

Look up owners/reviewers for a graph node (curated HTTP API). Provide `node_id` or `identity_prefix`. Scope resolution precedence: explicit `materialized_view_id` -> `workspace` (name) -> `LINEAI_WORKSPACE_NAME` environment variable -> the server's default workspace's latest materialized view (nothing specified is never an error while a default view exists).

NameTypeReqDescription
identity_prefixstring––
materialized_view_idstring–Optional materialized view id; takes precedence over `workspace`
node_idstring––
scan_spacestring––
workspacestring–Optional workspace (materialized view definition) name; overrides LINEAI_WORKSPACE_NAME

No output schema declared.

No examples provided.

lineai-graph-path-explain ~185

Explain bounded paths between two graph nodes (curated HTTP API). Requires `from_node_id`, `to_node_id`; optional `max_depth`, `scan_space`, `workspace`, `materialized_view_id`. Scope resolution precedence: explicit `materialized_view_id` -> `workspace` (name) -> `LINEAI_WORKSPACE_NAME` environment variable -> the server's default workspace's latest materialized view (nothing specified is never an error while a default view exists).

NameTypeReqDescription
from_node_idstringyes–
materialized_view_idstring–Optional materialized view id; takes precedence over `workspace`
max_depthinteger––
scan_spacestring––
to_node_idstringyes–
workspacestring–Optional workspace (materialized view definition) name; overrides LINEAI_WORKSPACE_NAME

No output schema declared.

No examples provided.

lineai-graph-search ~267

Search the Lineai knowledge graph (curated HTTP API). Provide `query` or `identity_prefix`; optional `scan_space`, `workspace`, `materialized_view_id`, `limit`. Results may include unresolved references (primaryLabel `UnresolvedReference`): symbols that are referenced but could not be resolved in the view — treat them as dependency indicators. Requires server route POST .../ai-retrieval/graph/search. Scope resolution precedence: explicit `materialized_view_id` -> `workspace` (name) -> `LINEAI_WORKSPACE_NAME` environment variable -> the server's default workspace's latest materialized view (nothing specified is never an error while a default view exists).

NameTypeReqDescription
identity_prefixstring–Prefix of stable graph identity
limitinteger–Suggested max hits (server may cap)
materialized_view_idstring–Optional materialized view id; takes precedence over `workspace`
prefer_latest_scanboolean––
qstring–Alias for query
querystring–Symbol or text query (alias: q)
scan_spacestring–Optional scan-space / branch filter
workspacestring–Optional workspace (materialized view definition) name; overrides LINEAI_WORKSPACE_NAME

No output schema declared.

No examples provided.

lineai-graph-validate-change-scope ~155

Validate whether a proposed change scope is safe given seed graph nodes (curated HTTP API). Scope resolution precedence: explicit `materialized_view_id` -> `workspace` (name) -> `LINEAI_WORKSPACE_NAME` environment variable -> the server's default workspace's latest materialized view (nothing specified is never an error while a default view exists).

NameTypeReqDescription
materialized_view_idstring–Optional materialized view id; takes precedence over `workspace`
proposed_change_summarystringyes–
scan_spacestring––
seed_node_idsarrayyes–
workspacestring–Optional workspace (materialized view definition) name; overrides LINEAI_WORKSPACE_NAME

No output schema declared.

No examples provided.

lineai-method-impact ~245

Analyze impacts of modifying a specific method within a given class or type. Scope resolution precedence: explicit `materialized_view_id` -> `workspace` (name) -> `LINEAI_WORKSPACE_NAME` environment variable -> the server's default workspace's latest materialized view (nothing specified is never an error while a default view exists). When the impact graph contains unresolved references (calls to symbols that could not be resolved inside the analyzed view), they are reported in a dedicated 'Unresolved References' section as dependency indicators. Recommended workflow: 1. Use this tool before implementing code changes 2. Run the tool against methods or functions that are being modified 3. Carefully review the impact analysis results to understand potential downstream effects Particularly crucial when AI-suggested modifications are being considered.

NameTypeReqDescription
classstring–Optional name of the class containing the method (case-insensitive substring filter)
materialized_view_idstring–Optional materialized view id; takes precedence over `workspace`
methodstringyesName of the method being analyzed
workspacestring–Optional workspace (materialized view definition) name; overrides LINEAI_WORKSPACE_NAME

No output schema declared.

No examples provided.

Install

How do I install the io.github.lineai-intelligence/lineai-mcp-server server?

io.github.lineai-intelligence/lineai-mcp-server runs locally as a PyPI package, launched with uvx lineai-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · lineai-mcp-server

# add to Claude Code
claude mcp add lineai-intelligence-lineai-mcp-server -- uvx lineai-mcp-server
Common questions

What is the io.github.lineai-intelligence/lineai-mcp-server server?

io.github.lineai-intelligence/lineai-mcp-server is listed in the public MCP registry as io.github.lineai-intelligence/lineai-mcp-server. An MCP Server to utilize Lineai's rich software dependency data in your AI programming assistant. This page covers its PyPI package (lineai-mcp-server).

Is the io.github.lineai-intelligence/lineai-mcp-server server safe to use?

io.github.lineai-intelligence/lineai-mcp-server scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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.github.lineai-intelligence/lineai-mcp-server server expose?

io.github.lineai-intelligence/lineai-mcp-server exposes 8 tools: lineai-method-impact, lineai-database-impact, lineai-graph-capabilities, lineai-graph-search, lineai-graph-impact, and 3 more. Their descriptions and schemas cost roughly 1,611 tokens of context every time the server is loaded.

Is the io.github.lineai-intelligence/lineai-mcp-server server still maintained?

io.github.lineai-intelligence/lineai-mcp-server is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.lineai-intelligence/lineai-mcp-server server under?

io.github.lineai-intelligence/lineai-mcp-server declares the MPL-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the io.github.lineai-intelligence/lineai-mcp-server server?

VerifyMCP ran 15 checks on io.github.lineai-intelligence/lineai-mcp-server, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.lineai-intelligence/lineai-mcp-server: Malware scan. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.