io.github.umitkavala/mindpm
NPM · MINDPM · SCANNED SEP 20
Persistent project memory for LLMs via SQLite. Never re-explain your project again.
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 & Transparency45
- 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 (MIT).Pass
- Actively maintained (last published 40 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1708 tokens (~77/item across 22 items; 22 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "query" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 22 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.umitkavala/mindpm MCP server?
io.github.umitkavala/mindpm runs locally as an npm package, launched with npx -y mindpm. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mindpm
claude mcp add umitkavala-mindpm -- npx -y mindpm
{
"mcpServers": {
"umitkavala-mindpm": {
"command": "npx",
"args": [
"-y",
"mindpm"
]
}
}
} {
"servers": {
"umitkavala-mindpm": {
"command": "npx",
"args": [
"-y",
"mindpm"
]
}
}
} codex mcp add umitkavala-mindpm -- npx -y mindpm
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"umitkavala-mindpm": {
"type": "local",
"command": [
"npx",
"-y",
"mindpm"
],
"enabled": true
}
}
} openclaw mcp add umitkavala-mindpm --command npx --arg -y --arg mindpm
mcp_servers:
umitkavala-mindpm:
command: "npx"
args: ["-y", "mindpm"] {
"McpServers": {
"umitkavala-mindpm": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mindpm"
]
}
}
} assistant mcp add umitkavala-mindpm -t stdio -c npx -a -y mindpm
{
"mcpServers": {
"umitkavala-mindpm": {
"command": "npx",
"args": [
"-y",
"mindpm"
]
}
}
} 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.
- 19 Sept 26 −2
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 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.
- 15 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.
- 13 Sept 26 −2
- Stability: pass → 0.83 functional
- 12 Sept 26 0
- Stability: 0.97 → pass security
- 11 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.
- 9 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.
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/mindpm@1.2.41
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
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 →
add_note Add Note ~143
Add a note to a project or task. Proactively use this when the user shares context about architecture, bugs, ideas, research findings, or any important information worth remembering. Always specify the project parameter when you know which project is active.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Note category (default: general) |
| content | string | yes | The note content |
| project | string | – | Project name or ID (always pass this when known — omitting may target the wrong project) |
| tags | array | – | Tags for categorization |
| task_id | string | – | Link this note to a specific task (hex ID or short ID like "zrdt-180") |
No output schema declared.
No examples provided.
create_project Create Project ~95
Create a new project to track. Use this when starting a new project or when a user mentions a project that doesn't exist yet.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | What this project is about |
| name | string | yes | Project name (unique) |
| repo_path | string | – | Path to the project repository |
| tech_stack | array | – | Technologies used, e.g. ["FastAPI", "React", "PostgreSQL"] |
No output schema declared.
No examples provided.
create_task Create Task ~128
Create a new task in a project. Proactively use this when the user mentions something that needs to be done, a bug to fix, or a feature to build.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Detailed description of the task |
| parent_task_id | string | – | Parent task ID for sub-tasks |
| priority | string | – | Task priority (default: medium) |
| project | string | – | Project name or ID (defaults to most recent active project) |
| tags | array | – | Tags like "backend", "auth", "bug" |
| title | string | yes | Short task title |
No output schema declared.
No examples provided.
end_session End Session ~102
End a work session with a summary of what was accomplished and what to do next. Call this when the user is done working.
| Name | Type | Req | Description |
|---|---|---|---|
| decisions_made | array | – | Decision IDs that were made |
| next_steps | string | – | What to do next time |
| project | string | – | Project name or ID |
| summary | string | yes | Summary of what was accomplished this session |
| tasks_worked_on | array | – | Task IDs that were worked on |
No output schema declared.
No examples provided.
get_agent_instructions Get Agent Instructions ~47
Returns the recommended instructions for using mindpm effectively. Call this once if you are unsure how to use mindpm, or share it with the user to paste into other LLM clients.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_blockers Get Blockers ~29
List all blocked tasks with what's blocking them.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | – | Project name or ID |
No output schema declared.
No examples provided.
get_context Get Context ~50
Get context by key or list all context for a project.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | – | Specific context key to retrieve. If omitted, returns all context. |
| project | string | – | Project name or ID |
No output schema declared.
No examples provided.
get_delivery_metrics Get Delivery Metrics ~72
DORA-inspired delivery metrics for a project: throughput, lead time, flow efficiency, and performance tier. Use to understand delivery health and trends.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Time window in days (default: 30) |
| project | string | – | Project name or ID (defaults to most recent active project) |
No output schema declared.
No examples provided.
get_next_tasks Get Next Tasks ~59
Smart query: what should be worked on next? Returns highest priority non-blocked tasks for a project.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max number of tasks to return (default: 5) |
| project | string | – | Project name or ID |
No output schema declared.
No examples provided.
get_project_status Get Project Status ~48
Get a full overview of a project: active tasks, recent decisions, blockers, and last session summary. Great for getting up to speed.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project name or ID |
No output schema declared.
No examples provided.
get_project_summary Get Project Summary ~42
High-level summary of a project: total tasks by status, recent activity, open blockers, and upcoming priorities.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | – | Project name or ID |
No output schema declared.
No examples provided.
get_task Get Task ~46
Get full detail for a specific task including sub-tasks and related notes.
| Name | Type | Req | Description |
|---|---|---|---|
| task_id | string | yes | Task ID (hex ID or short ID like "zrdt-180") |
No output schema declared.
No examples provided.
list_decisions List Decisions ~62
List decisions for a project. Filter by tags to find specific decisions.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max number of decisions to return (default: 20) |
| project | string | – | Project name or ID |
| tag | string | – | Filter by tag |
No output schema declared.
No examples provided.
list_projects List Projects ~39
List all tracked projects. Filter by status to see active, paused, completed, or archived projects.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Filter by project status |
No output schema declared.
No examples provided.
list_tasks List Tasks ~118
List tasks with filters. Defaults to showing non-completed tasks for the most recent active project.
| Name | Type | Req | Description |
|---|---|---|---|
| include_done | boolean | – | Include completed tasks (default: false) |
| limit | integer | – | Max tasks to return (default: 50) |
| offset | integer | – | Number of tasks to skip for pagination (default: 0) |
| priority | string | – | Filter by priority |
| project | string | – | Project name or ID |
| status | string | – | Filter by status |
| tag | string | – | Filter by tag |
No output schema declared.
No examples provided.
log_decision Log Decision ~130
Record a decision with reasoning and alternatives considered. Proactively use this when the user makes a technical decision, chooses between options, or settles a debate.
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | array | – | Rejected alternatives |
| decision | string | yes | What was decided |
| project | string | – | Project name or ID |
| reasoning | string | – | Why this was decided |
| tags | array | – | Tags like "architecture", "database", "api" |
| task_id | string | – | Task ID to associate this decision with (omit for project-level) |
| title | string | yes | Short title for the decision |
No output schema declared.
No examples provided.
query Query Database ~46
Execute a read-only SQL query against the database. Only SELECT statements are allowed. Use this for custom queries not covered by other tools.
| Name | Type | Req | Description |
|---|---|---|---|
| sql | string | yes | SQL SELECT query to execute |
No output schema declared.
No examples provided.
search Search Everything ~41
Full-text search across tasks, notes, and decisions for a project.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | – | Project name or ID |
| query | string | yes | Search query |
No output schema declared.
No examples provided.
search_notes Search Notes ~47
Full-text search across notes for a project.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category |
| project | string | – | Project name or ID |
| query | string | yes | Search query |
No output schema declared.
No examples provided.
set_context Set Context ~112
Set a key-value context pair for a project (upsert). Proactively use this when the user shares important project context like architecture decisions, config values, conventions, or constraints.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category like "architecture", "config", "convention", "constraint" |
| key | string | yes | Context key, e.g. "auth_approach", "deployment_target", "api_base_url" |
| project | string | – | Project name or ID |
| value | string | yes | Context value |
No output schema declared.
No examples provided.
start_session Start Session ~104
Begin a work session for a project. Returns the full project overview including last session's next_steps, active tasks, blockers, and recent decisions. Call this at the start of every conversation. For multi-project conversations, call once per project — after that, pass `project` explicitly on every tool call. IMPORTANT: Always show the kanban_url to the user as a clickable link so they can open the Kanban board.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | – | Project name or ID |
No output schema declared.
No examples provided.
update_task Update Task ~148
Update any field of a task. Proactively use this when a task status changes, priorities shift, or new information comes in.
| Name | Type | Req | Description |
|---|---|---|---|
| addBlockedBy | array | – | Task IDs that block this task (appended to existing list) |
| blocked_by | array | – | Task IDs that block this task (replaces existing list) |
| description | string | – | New description |
| priority | string | – | New priority |
| status | string | – | New status |
| tags | array | – | New tags (replaces existing) |
| task_id | string | yes | Task ID to update (hex ID or short ID like "zrdt-180") |
| title | string | – | New title |
No output schema declared.
No examples provided.
What is the io.github.umitkavala/mindpm MCP server?
io.github.umitkavala/mindpm is an MCP server listed in the public MCP registry as io.github.umitkavala/mindpm. Persistent project memory for LLMs via SQLite. Never re-explain your project again. This page covers its npm package (mindpm).
Is the io.github.umitkavala/mindpm MCP server safe to use?
io.github.umitkavala/mindpm scores 81 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. 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.umitkavala/mindpm MCP server expose?
io.github.umitkavala/mindpm exposes 22 tools: create_project, list_projects, get_project_status, create_task, update_task, and 17 more. Their descriptions and schemas cost roughly 1,708 tokens of context every time the server is loaded.
Is the io.github.umitkavala/mindpm MCP server still maintained?
io.github.umitkavala/mindpm 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.umitkavala/mindpm MCP server under?
io.github.umitkavala/mindpm declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.