io.github.spranab/saga-mcp
NPM · SAGA-MCP · SCANNED SEP 20
Jira-like project tracker for AI agents with SQLite, full task hierarchy, and dashboard
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 52 of 130 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to spranab/saga-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 11 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 2087 tokens (~67/item across 31 items; 31 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 57% 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
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 31 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
How do I install the io.github.spranab/saga-mcp server?
io.github.spranab/saga-mcp runs locally as an npm package, launched with npx -y saga-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · saga-mcp
claude mcp add spranab-saga-mcp -- npx -y saga-mcp
{
"mcpServers": {
"spranab-saga-mcp": {
"command": "npx",
"args": [
"-y",
"saga-mcp"
]
}
}
} {
"servers": {
"spranab-saga-mcp": {
"command": "npx",
"args": [
"-y",
"saga-mcp"
]
}
}
} codex mcp add spranab-saga-mcp -- npx -y saga-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"spranab-saga-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"saga-mcp"
],
"enabled": true
}
}
} openclaw mcp add spranab-saga-mcp --command npx --arg -y --arg saga-mcp
mcp_servers:
spranab-saga-mcp:
command: "npx"
args: ["-y", "saga-mcp"] {
"McpServers": {
"spranab-saga-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"saga-mcp"
]
}
}
} assistant mcp add spranab-saga-mcp -t stdio -c npx -a -y saga-mcp
{
"mcpServers": {
"spranab-saga-mcp": {
"command": "npx",
"args": [
"-y",
"saga-mcp"
]
}
}
} 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.77 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Stability: pass → 0.83 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
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 · Analysed npm/saga-mcp@1.5.5
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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | spranab/saga-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/spranab/saga-mcp/.github/workflows/publish.yml@refs/tags/v1.5.5 |
| Rekor log index | 1187964197 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b03211c67bc2bbc4a6c4af281d6dc9e4a7fed76eb39e37802d0cb84b3e2e8a0de1324c13b5fb0354bb2324c73184703ce48ba17584b4540679d3bba80 |
Background: How many MCP packages publish verified provenance →
Dependencies 130 packages
| Packages resolved | 130 |
|---|---|
| Deprecated | 1 |
| Stale | 51 |
| 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 →
activity_log ~93
View the activity log showing what changed and when. Useful for understanding recent progress or reviewing what happened since the last session.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Filter by action type |
| entity_id | integer | – | Filter by specific entity |
| entity_type | string | – | Filter by entity type |
| limit | integer | – | – |
| since | string | – | ISO 8601 datetime - show only activity after this time |
No output schema declared.
No examples provided.
comment_add ~62
Add a comment to a task. Comments create a chronological discussion thread — useful for leaving breadcrumbs across sessions.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | Author name (optional) |
| content | string | yes | Comment text |
| task_id | integer | yes | Task ID to comment on |
No output schema declared.
No examples provided.
comment_list ~28
List all comments on a task in chronological order.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | integer | yes | Task ID |
No output schema declared.
No examples provided.
epic_create ~77
Create an epic within a project. Epics group related tasks into a feature or workstream.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Epic description |
| name | string | yes | Epic name |
| priority | string | – | – |
| project_id | integer | yes | Parent project ID |
| status | string | – | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
epic_list ~53
List epics for a project with task counts and completion stats. Optionally filter by status or priority.
| Name | Type | Req | Description |
|---|---|---|---|
| priority | string | – | – |
| project_id | integer | yes | Project ID |
| status | string | – | – |
No output schema declared.
No examples provided.
epic_update ~84
Update an epic. Pass only the fields you want to change. Set status to "cancelled" to soft-delete.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| id | integer | yes | Epic ID |
| name | string | – | – |
| priority | string | – | – |
| sort_order | integer | – | – |
| status | string | – | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
note_delete ~23
Delete a note by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Note ID |
No output schema declared.
No examples provided.
note_list ~67
List notes with optional filters. Returns notes sorted by most recent first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| note_type | string | – | – |
| related_entity_id | integer | – | – |
| related_entity_type | string | – | – |
| tag | string | – | Filter by a single tag |
No output schema declared.
No examples provided.
note_save ~131
Create or update a note. Notes capture decisions, context, progress, meeting notes, blockers, technical details, or release info. If "id" is provided, updates the existing note; otherwise creates a new one.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Full note content (markdown supported) |
| id | integer | – | Note ID (omit to create new) |
| note_type | string | – | – |
| related_entity_id | integer | – | ID of the related entity |
| related_entity_type | string | – | Link note to an entity |
| tags | array | – | – |
| title | string | yes | Note title |
No output schema declared.
No examples provided.
note_search ~41
Search across note titles and content by keyword.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| note_type | string | – | – |
| query | string | yes | Search keywords |
No output schema declared.
No examples provided.
project_create ~61
Create a new project. Projects are the top-level container for all work.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Project description |
| name | string | yes | Project name |
| status | string | – | Project status |
| tags | array | – | Tags for categorization |
No output schema declared.
No examples provided.
project_list ~35
List all projects with epic/task counts and completion percentages. Optionally filter by status.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Filter by status |
No output schema declared.
No examples provided.
project_update ~69
Update a project. Pass only the fields you want to change. Set status to "archived" to soft-delete.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | – |
| id | integer | yes | Project ID |
| name | string | – | – |
| status | string | – | – |
| tags | array | – | – |
No output schema declared.
No examples provided.
subtask_create ~56
Create one or more subtasks (checklist items) for a task. Accepts a single title string or an array of title strings for batch creation.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | integer | yes | Parent task ID |
| titles | – | yes | – |
No output schema declared.
No examples provided.
subtask_delete ~31
Delete one or more subtasks. Accepts a single ID or array of IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | – | yes | – |
No output schema declared.
No examples provided.
subtask_update ~53
Update a subtask title, status, or sort order.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Subtask ID |
| sort_order | integer | – | – |
| status | string | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
task_batch_update ~72
Update multiple tasks at once. Useful for changing status of several tasks (e.g., mark 3 tasks as done) or reassigning tasks.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_to | string | – | – |
| ids | array | yes | Task IDs to update |
| priority | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
task_create ~135
Create a task within an epic. Tasks are the primary unit of work.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_to | string | – | Assignee name |
| depends_on | array | – | Task IDs this task depends on |
| description | string | – | Task description |
| due_date | string | – | Due date (YYYY-MM-DD) |
| epic_id | integer | yes | Parent epic ID |
| estimated_hours | number | – | Estimated hours |
| priority | string | – | – |
| source_ref | object | – | Link to source code location |
| status | string | – | – |
| tags | array | – | – |
| title | string | yes | Task title |
No output schema declared.
No examples provided.
task_get ~37
Get a single task with full details including all subtasks, related notes, comments, and dependencies.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Task ID |
No output schema declared.
No examples provided.
task_list ~129
List tasks with optional filters. If no epic_id given, lists across ALL epics. Includes subtask counts and dependency info.
| Name | Type | Req | Description |
|---|---|---|---|
| assigned_to | string | – | Filter by assignee |
| epic_id | integer | – | Filter by epic (omit for all tasks) |
| limit | integer | – | Max results |
| priority | string | – | – |
| sort_by | string | – | Sort order: priority (critical first), created (newest first), due_date (earliest first), status (actionable first) |
| status | string | – | – |
| tag | string | – | Filter by tag |
No output schema declared.
No examples provided.
task_update ~143
Update a task. Pass only fields to change. Status transitions are automatically logged in the activity log.
| Name | Type | Req | Description |
|---|---|---|---|
| actual_hours | number | – | – |
| assigned_to | string | – | – |
| depends_on | array | – | Task IDs this task depends on (replaces existing) |
| description | string | – | – |
| due_date | string | – | – |
| estimated_hours | number | – | – |
| id | integer | yes | Task ID |
| priority | string | – | – |
| sort_order | integer | – | – |
| source_ref | object | – | Link to source code location |
| status | string | – | – |
| tags | array | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
template_apply ~77
Apply a template to create tasks in an epic. Replaces {variable} placeholders with provided values.
| Name | Type | Req | Description |
|---|---|---|---|
| epic_id | integer | yes | Epic to create tasks in |
| template_id | integer | yes | Template ID to apply |
| variables | object | – | Key-value pairs for {variable} substitution (e.g., {"feature": "auth"}) |
No output schema declared.
No examples provided.
template_create ~75
Create a reusable task template. Templates define a set of tasks that can be instantiated into any epic. Use {variable} placeholders for dynamic values.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Template description |
| name | string | yes | Template name (must be unique) |
| tasks | array | yes | Task definitions. Use {variable} for placeholders. |
No output schema declared.
No examples provided.
template_delete ~22
Delete a task template.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | Template ID |
No output schema declared.
No examples provided.
template_list ~14
List all available task templates.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tracker_dashboard ~80
Get a comprehensive project overview in a single call. Returns: project info, all epics with task counts, overall stats (total/done/blocked/in_progress), recent activity, and recent notes. This is the best first tool to call when starting work on a project.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | integer | – | Project ID (omit if only one project exists) |
No output schema declared.
No examples provided.
tracker_export ~62
Export a full project as nested JSON. Includes all epics, tasks, subtasks, comments, dependencies, and related notes. Useful for backup, migration, or sharing.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | integer | – | Project ID to export (omit if only one project exists) |
No output schema declared.
No examples provided.
tracker_import ~51
Import a project from JSON (matching tracker_export format). Creates all entities with new IDs and remaps references. Uses a transaction for atomicity.
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | Full export JSON object from tracker_export |
No output schema declared.
No examples provided.
tracker_init ~72
Initialize the tracker for a project. If the database is empty, creates a project with the given name. If a project already exists, returns its info.
| Name | Type | Req | Description |
|---|---|---|---|
| project_description | string | – | Description for the new project |
| project_name | string | – | Name for a new project (only used if DB is empty) |
No output schema declared.
No examples provided.
tracker_search ~68
Search across ALL entities (projects, epics, tasks, notes) by keyword. Returns categorized results.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_types | array | – | Limit search to specific entity types (omit for all) |
| limit | integer | – | Max results per entity type |
| query | string | yes | Search keywords |
No output schema declared.
No examples provided.
tracker_session_diff ~86
Show what changed since a given timestamp. Returns aggregated summary with counts by action and entity type, plus highlights of key changes. Call this at the start of a session to understand what happened since the last one.
| Name | Type | Req | Description |
|---|---|---|---|
| since | string | yes | ISO 8601 datetime — show changes after this time (e.g. "2026-02-21T15:00:00") |
No output schema declared.
No examples provided.
What is the io.github.spranab/saga-mcp server?
io.github.spranab/saga-mcp is listed in the public MCP registry as io.github.spranab/saga-mcp. Jira-like project tracker for AI agents with SQLite, full task hierarchy, and dashboard. This page covers its npm package (saga-mcp).
Is the io.github.spranab/saga-mcp server safe to use?
io.github.spranab/saga-mcp scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.spranab/saga-mcp server expose?
io.github.spranab/saga-mcp exposes 31 tools: project_create, project_list, project_update, epic_create, epic_list, and 26 more. Their descriptions and schemas cost roughly 2,087 tokens of context every time the server is loaded.
Is the io.github.spranab/saga-mcp server still maintained?
io.github.spranab/saga-mcp 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.
What licence is the io.github.spranab/saga-mcp server under?
io.github.spranab/saga-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.