Abscissa
PYPI · ABSCISSA
Safety-aware MCP server for Linear issues, projects, cycles, and dependencies.
Available components
Last scanned (17 hours ago)
Scores higher than 87% of PyPI servers
Category Project Management
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 Security100
- No malware found by supply-chain analysis.Pass
- 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 28 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to KazKozDev/abscissa). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 115 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2005 tokens (~47/item across 42 items; 42 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety80
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 1 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_issue_from_project" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
- An AI judge read all 42 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
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.
- 4 Nov 26 −5
- Stability: pass → 0.63 functional
- 2 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 1 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 0
- Stability: pass → 0.97 functional
- 22 Oct 26 0
- Stability: 0.97 → pass security
- 21 Oct 26 0
- Stability: pass → 0.97 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 4 Nov 2026 · Analysed pypi/abscissa@0.1.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | KazKozDev/abscissa |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/KazKozDev/abscissa/.github/workflows/release.yml@refs/tags/v0.1.3 |
| Rekor log index | 2143851392 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:26916b4a3825ba9cd817c1f18c771f993f80228f1de38ae9b29e63105c9bed8b |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
add_comment ~32
Add a markdown comment to a Linear issue.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| issue_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
add_issue_dependency ~39
Record that blocker_issue_id blocks blocked_issue_id in Linear.
| Name | Type | Req | Description |
|---|---|---|---|
| blocked_issue_id | string | yes | – |
| blocker_issue_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
add_issue_label ~32
Add a label to an issue.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_id | string | yes | – |
| label_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
add_project_label ~34
Attach an existing project label to a project.
| Name | Type | Req | Description |
|---|---|---|---|
| label_id | string | yes | – |
| project_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
archive_cycle ~36
Archive a cycle. Set confirm=true only after explicit user confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| cycle_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
archive_issue ~36
Archive an issue. Set confirm=true only after explicit user confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| issue_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
archive_project ~36
Archive a project. Set confirm=true only after explicit user confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| project_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
assign_issue ~31
Assign a user to an issue.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_id | string | yes | – |
| user_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_cycle ~93
Create a Linear cycle for a team. starts_at and ends_at must be ISO 8601 timestamps, for example 2026-07-13T09:00:00Z. team_id accepts a team UUID or key.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| ends_at | string | yes | – |
| name | string | yes | – |
| starts_at | string | yes | – |
| team_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_issue ~91
Create a new Linear issue. team_id accepts a team UUID or key (for example, ART). Priority is 0=none, 1=urgent, 2=high, 3=normal, or 4=low.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| priority | integer | – | – |
| state | string | – | – |
| team_id | string | yes | – |
| title | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_label ~37
Create a label for a team.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | – |
| name | string | yes | – |
| team_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_project ~46
Create a project; team_ids may be comma-separated team keys or UUIDs.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| name | string | yes | – |
| team_ids | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_project_label ~47
Create a reusable project label. Use add_project_label to attach it to a project.
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | – |
| description | string | – | – |
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
create_project_update ~49
Post a project update. Health may be onTrack, atRisk, or offTrack.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| health | string | – | – |
| project_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
delete_issue ~37
Delete an issue permanently. Set confirm=true only after explicit user confirmation.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| issue_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_current_user ~20
Return the authenticated Linear user behind the configured API key.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_issue ~32
Get full issue details, including comments, labels, assignee, and dates.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_project ~22
Get a project by UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_team ~29
Get a team by key (for example, ART) or UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_user_issues ~48
Get a user's assigned issues; omit user_id to retrieve the authenticated user's issues.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
| user_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_cycle_issues ~48
List issues in a cycle. Pass next_cursor as cursor for the next page.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| cycle_id | string | yes | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_cycles ~43
List workspace cycles, optionally filtered by a team key or UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
| team_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_issue_dependencies ~81
List issues this issue blocks and issues that block it. The returned relation IDs can be passed to remove_issue_dependency. Use the matching cursor from next_cursors to retrieve another page for either side.
| Name | Type | Req | Description |
|---|---|---|---|
| blocked_by_cursor | string | – | – |
| blocks_cursor | string | – | – |
| issue_id | string | yes | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_issue_labels ~47
List labels for a team. Pass next_cursor as cursor for the next page.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
| team_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_project_issues ~47
List a project's issues. Pass next_cursor as cursor for the next page.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
| project_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_project_labels ~38
List reusable project labels. Pass next_cursor as cursor for the next page.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_project_updates ~46
List a project's updates. Pass next_cursor as cursor for the next page.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
| project_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_projects ~35
List projects. Pass next_cursor as cursor for the next page.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_teams ~36
List teams. Pass next_cursor as cursor for the next page.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_users ~36
List organization users. Pass next_cursor as cursor for the next page.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_workflow_states ~49
List workflow states for a team. Pass next_cursor as cursor for the next page.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | – |
| limit | integer | – | – |
| team_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
remove_issue_dependency ~26
Remove an issue dependency by its relation ID.
| Name | Type | Req | Description |
|---|---|---|---|
| relation_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
remove_issue_from_project ~27
Remove an issue from its current Linear project.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
remove_issue_label ~32
Remove a label from an issue.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_id | string | yes | – |
| label_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
remove_project_label ~38
Remove a project label from a project without deleting the reusable label.
| Name | Type | Req | Description |
|---|---|---|---|
| label_id | string | yes | – |
| project_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
search_issues ~77
Search Linear issues with filters. Pass next_cursor as cursor for the next page.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee_id | string | – | – |
| cursor | string | – | – |
| limit | integer | – | – |
| priority | integer | – | – |
| query | string | – | – |
| state | string | – | – |
| team_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_issue_estimate ~36
Set story points or an hour estimate on an issue.
| Name | Type | Req | Description |
|---|---|---|---|
| estimate | number | yes | – |
| issue_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
set_issue_project ~56
Add an issue to a Linear project. Args: issue_id: Issue UUID or identifier such as ABS-1. project_id: Project UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_id | string | yes | – |
| project_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_cycle ~64
Update a cycle's name, description, or ISO 8601 start and end timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| cycle_id | string | yes | – |
| description | string | – | – |
| ends_at | string | – | – |
| name | string | – | – |
| starts_at | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_issue ~70
Update an existing Linear issue. Use a UUID or identifier such as ART-5.
| Name | Type | Req | Description |
|---|---|---|---|
| assignee_id | string | – | – |
| description | string | – | – |
| issue_id | string | yes | – |
| priority | integer | – | – |
| state | string | – | – |
| title | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_project ~73
Update a project's name, summary, or status. State accepts a Linear status type such as planned, started, paused, completed, or canceled, or the status's display name.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| name | string | – | – |
| project_id | string | yes | – |
| state | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
update_project_details ~173
Update a project's detailed fields. member_ids and team_ids are comma-separated user/team UUIDs; team keys also work. Dates use YYYY-MM-DD. Member and team lists replace their current values. Use the clear_* flags to remove an optional field deliberately.
| Name | Type | Req | Description |
|---|---|---|---|
| clear_lead | boolean | – | – |
| clear_members | boolean | – | – |
| clear_start_date | boolean | – | – |
| clear_target_date | boolean | – | – |
| color | string | – | – |
| content | string | – | – |
| icon | string | – | – |
| lead_id | string | – | – |
| member_ids | string | – | – |
| priority | integer | – | – |
| project_id | string | yes | – |
| start_date | string | – | – |
| target_date | string | – | – |
| team_ids | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Abscissa MCP server?
Abscissa runs locally as a PyPI package, launched with uvx abscissa. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · abscissa
claude mcp add kazkozdev-abscissa -- uvx abscissa
What is the Abscissa MCP server?
Abscissa is an MCP server listed in the public MCP registry as io.github.KazKozDev/abscissa. Safety-aware MCP server for Linear issues, projects, cycles, and dependencies. This page covers its PyPI package (abscissa).
Is the Abscissa MCP server safe to use?
Abscissa scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 Abscissa MCP server expose?
Abscissa exposes 42 tools: get_current_user, create_issue, update_issue, set_issue_project, remove_issue_from_project, and 37 more. Their descriptions and schemas cost roughly 2,005 tokens of context every time the server is loaded.
Is the Abscissa MCP server still maintained?
Abscissa is still listed as active in the MCP registry. We last reached this channel on 4 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 Abscissa MCP server under?
Abscissa declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.