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.

Granoflow

NPM · @GRANOFLOW/MCP-SERVER · SCANNED SEP 24

Connect MCP-capable AI agents to local Granoflow tasks, reviews, cards, imports, and work memory.

0 this week 77 Trust /100
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 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
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 9272 tokens (~71/item across 129 items; 129 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 22% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 11 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "granoflow_evidence_delete" implies "delete" 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 129 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
Install

How do I install the Granoflow MCP server?

Granoflow runs locally as an npm package, launched with npx -y @granoflow/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.

npm · @granoflow/mcp-server

# add to Claude Code
claude mcp add com-granoflow-mcp-server -- npx -y @granoflow/mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "com-granoflow-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@granoflow/mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-granoflow-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@granoflow/mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-granoflow-mcp-server -- npx -y @granoflow/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-granoflow-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@granoflow/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-granoflow-mcp-server --command npx --arg -y --arg @granoflow/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  com-granoflow-mcp-server:
    command: "npx"
    args: ["-y", "@granoflow/mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-granoflow-mcp-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@granoflow/mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-granoflow-mcp-server -t stdio -c npx -a -y @granoflow/mcp-server
// mcp.json
{
  "mcpServers": {
    "com-granoflow-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@granoflow/mcp-server"
      ]
    }
  }
}
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.

  • 24 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 23 Sept 26 0
    • Stability: 0.97 → pass security
  • 22 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.

  • 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.

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 0
    • Stability: 0.97 → pass security
  • 15 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.

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 24 Sept 2026 · Analysed npm/@granoflow/mcp-server@0.1.16

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 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 129 exposed · ~9,272 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
granoflow_logical_attachment_replace ~115

Replace the current typed project, milestone, or task artifact and require App-owned SHA-256 readback before it becomes current.

NameTypeReqDescription
dryRunboolean––
entityIdstringyes–
entityTypestringyes–
expectedUpdatedAtstringyes–
filePathstringyes–
idempotencyKeystringyes–
logicalSlotstringyes–
visualConfirmedboolean–Must be true when logicalSlot is ui_prototype.

No output schema declared.

No examples provided.

granoflow_memory_batch_preview ~92

Ask the running Granoflow app to preview an AI-agent memory batch before any write. Granoflow owns project/milestone matching and duplicate signals; this MCP tool only forwards after capability checks.

NameTypeReqDescription
dryRunboolean–When true, previews the HTTP request without calling the app.
itemsarrayyes–
sourceobject––
targetobject––

No output schema declared.

No examples provided.

granoflow_milestone_context_archive ~114

Preview a milestone archive context closure: final milestone state plus parent project description update. Real writes fail closed until the app exposes a safe archive API.

NameTypeReqDescription
closureobjectyes–
confirmArchiveboolean–Reserved for future safe archive writes; dry-run remains the normal mode.
dryRunboolean–When true, previews the closure without writing.
milestoneIdstringyesGranoflow milestone id.
projectIdstringyesParent Granoflow project id.

No output schema declared.

No examples provided.

granoflow_milestone_context_update ~100

Update only an active Granoflow milestone description as living context. Fails closed for archived milestones and defaults to dry-run.

NameTypeReqDescription
descriptionstringyes–
dryRunboolean–When true, previews the request without writing.
evidenceSummarystringyesShort evidence summary for why this context description changed.
milestoneIdstringyesGranoflow milestone id.
projectIdstring––

No output schema declared.

No examples provided.

granoflow_milestone_create ~135

Create a Granoflow milestone with common structured fields. When dueAt is omitted, defaults to the next available Saturday for the project. Defaults to dry-run.

NameTypeReqDescription
descriptionstring––
dryRunboolean–When true, previews the request without writing.
dueAtstring–Explicit deadline. When omitted, uses the next local Saturday at 23:59:59.000 and advances by whole weeks past existing deadlines in the same project.
projectIdstringyesGranoflow project id.
statusstring––
titlestringyes–

No output schema declared.

No examples provided.

granoflow_milestone_delete ~71

Safely delete a Granoflow milestone. Defaults to dry-run and requires confirmTitle for writes.

NameTypeReqDescription
allowLinkedTasksboolean––
confirmTitlestring––
dryRunboolean––
milestoneIdstringyesGranoflow milestone id.

No output schema declared.

No examples provided.

granoflow_milestone_experiences ~34

List independent Experience records derived from tasks in one milestone.

NameTypeReqDescription
milestoneIdstringyes–

No output schema declared.

No examples provided.

granoflow_milestone_knowledge_usages ~42

List Knowledge actually adopted by tasks in one milestone. The result is read-only and derived.

NameTypeReqDescription
milestoneIdstringyes–

No output schema declared.

No examples provided.

granoflow_milestone_list ~19

List Granoflow milestones.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

granoflow_milestone_resolve ~59

Resolve Granoflow milestone candidates by title without creating or updating data.

NameTypeReqDescription
includeDoneboolean––
matchModestring––
projectIdstring––
querystringyes–

No output schema declared.

No examples provided.

granoflow_milestone_update ~116

Update a Granoflow milestone with common structured fields. Defaults to dry-run. Use granoflow_milestone_context_update for description upkeep; description updates fail closed for archived milestones.

NameTypeReqDescription
descriptionstring––
dryRunboolean–When true, previews the request without writing.
dueAtstring––
milestoneIdstringyesGranoflow milestone id.
projectIdstring––
statusstring––
titlestring––

No output schema declared.

No examples provided.

granoflow_milestone_workflow_skill ~79

Read the bundled Granoflow Milestone Workflow skill. Use it when one delegated outcome spans multiple child tasks and needs a stable milestone charter, evolving task portfolio, dependency and handoff coordination, bounded authorization, replanning, cross-task integration evidence, and milestone-level acceptance before closure. Child implementation remains owned by Task Work.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

granoflow_persistent_milestone_runner_skill ~78

Read the bundled provider-neutral Granoflow Persistent Milestone Runner skill. Use it for restart-safe milestone execution with leases, heartbeat, bounded attempt history, no-progress replanning, resumable interaction nodes, explicit authorization manifests, and evidence-gated completion. A separate user Skill may choose the worker command or model.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

granoflow_project_context_attachment_read ~113

Read a bounded section of project_snapshot.yaml or project_rules.yaml. Defaults to header, summary, and the smallest matching section; full read requires explicit intent.

NameTypeReqDescription
allowFullReadboolean––
attachmentstring––
dryRunboolean–When true, previews the HTTP request without calling the app.
intentstring––
projectIdstringyesGranoflow project id.
querystring––
sectionstring––

No output schema declared.

No examples provided.

granoflow_project_context_attachment_reconcile ~74

Check or reconcile project context YAML freshness. Low-risk factual snapshot deltas can reconcile; rules and wording conflicts return a proposal.

NameTypeReqDescription
attachmentstring––
dryRunboolean–When true, previews reconcile without writing.
projectIdstringyesGranoflow project id.

No output schema declared.

No examples provided.

granoflow_project_context_attachment_write ~110

Write a project context YAML attachment through app-owned safety gates. project_rules.yaml requires confirmation; secret/privacy risks fail closed.

NameTypeReqDescription
attachmentstring––
confirmedboolean–Required for project_rules.yaml rule, wording, or decision-note changes.
contentstringyes–
dryRunboolean–When true, previews the HTTP request without calling the app.
projectIdstringyesGranoflow project id.
sectionstring––

No output schema declared.

No examples provided.

granoflow_project_context_attachments_ensure ~68

Ensure Granoflow canonical project context YAML attachments exist: project_snapshot.yaml and project_rules.yaml. Defaults to dry-run.

NameTypeReqDescription
dryRunboolean–When true, previews missing attachments without writing.
projectIdstringyesGranoflow project id.

No output schema declared.

No examples provided.

granoflow_project_context_update ~87

Update only a Granoflow project description as living context. Defaults to dry-run and requires an evidence summary.

NameTypeReqDescription
descriptionstringyes–
dryRunboolean–When true, previews the request without writing.
evidenceSummarystringyesShort evidence summary for why this context description changed.
projectIdstringyesGranoflow project id.

No output schema declared.

No examples provided.

granoflow_project_create ~72

Create a Granoflow project with common structured fields. Defaults to dry-run.

NameTypeReqDescription
descriptionstring––
domainTagstring––
dryRunboolean–When true, previews the request without writing.
statusstring––
titlestringyes–

No output schema declared.

No examples provided.

granoflow_project_definition_skill ~57

Read the bundled Granoflow Project Definition skill. Use it to build or refine one Project Work YAML step by step or from a vague request, then gate manual and automatic project actions through App-owned readiness and artifact readback.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

granoflow_project_delete ~69

Safely delete a Granoflow project. Defaults to dry-run and requires confirmTitle for writes.

NameTypeReqDescription
allowLinkedTasksboolean––
confirmTitlestring––
dryRunboolean––
projectIdstringyesGranoflow project id.

No output schema declared.

No examples provided.

granoflow_project_design_baseline_import ~115

Import one validated high-fidelity prototype package as the App-owned project design baseline. The App owns package validation, immutable versions, project linking, deduplication, and exact SHA-256 readback.

NameTypeReqDescription
dryRunboolean––
filePathstringyesAbsolute path to a local .zip package.
idempotencyKeystringyes–
projectIdstringyes–
prototypeIdstring–Existing App-owned prototype id when adding a new baseline version.

No output schema declared.

No examples provided.

granoflow_project_design_baseline_read ~65

Read back one exact App-owned project design baseline reference. Never guesses the latest version.

NameTypeReqDescription
expectedPackageSha256stringyes–
projectIdstringyes–
prototypeIdstringyes–
versionIdstringyes–

No output schema declared.

No examples provided.

granoflow_project_experiences ~32

List independent Experience records derived from tasks in one project.

NameTypeReqDescription
projectIdstringyes–

No output schema declared.

No examples provided.

granoflow_project_interaction_style ~62

Resolve the current project's explanation style. Missing or incomplete settings default to newcomer-friendly, detailed explanations; this tool never asks the user to choose.

NameTypeReqDescription
dryRunboolean––
projectIdstringyesGranoflow project id.

No output schema declared.

No examples provided.

granoflow_project_knowledge_usages ~40

List Knowledge actually adopted by tasks in one project. The result is read-only and derived.

NameTypeReqDescription
projectIdstringyes–

No output schema declared.

No examples provided.

granoflow_project_list ~17

List Granoflow projects.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

granoflow_project_resolve ~49

Resolve Granoflow project candidates by title without creating or updating data.

NameTypeReqDescription
includeDoneboolean––
matchModestring––
querystringyes–

No output schema declared.

No examples provided.

granoflow_project_update ~85

Update a Granoflow project with common structured fields. Defaults to dry-run.

NameTypeReqDescription
descriptionstring––
domainTagstring––
dryRunboolean–When true, previews the request without writing.
projectIdstringyesGranoflow project id.
statusstring––
titlestring––

No output schema declared.

No examples provided.

granoflow_project_work_confirm ~78

Confirm the exact current Project Work content hash in the App. Confirmation does not authorize execution, commit, push, publish, deploy, deletion, payment, or messaging.

NameTypeReqDescription
confirmedbooleanyes–
dryRunboolean––
expectedContentSha256stringyes–
projectIdstringyes–

No output schema declared.

No examples provided.

granoflow_project_work_evaluate ~71

Evaluate the current Project Work YAML for a manual or automatic action. Partial attachment is allowed; gated actions fail with all relevant missing paths.

NameTypeReqDescription
actionstringyes–
dryRunboolean––
projectIdstringyes–
requiredPathsarray––

No output schema declared.

No examples provided.

granoflow_review_card_authoring_apply ~80

Apply only user-approved operations from a current review-card authoring preview. Returns app-owned readback; never call without explicit approval of the previewed operations.

NameTypeReqDescription
approvedFieldsByOperationobject––
approvedOperationIdsarrayyes–
previewHashstringyes–
previewTokenstringyes–

No output schema declared.

No examples provided.

granoflow_review_card_authoring_preview ~66

Preview controlled review-card creation, existing-card linking, or field-level updates for an existing project or inbox task. This endpoint performs no writes and returns a confirmation token plus shared-note impact.

NameTypeReqDescription
operationsarrayyes–
taskIdstringyes–

No output schema declared.

No examples provided.

granoflow_review_card_draft_schema ~55

Fetch the Granoflow review card draft template and field schema from the running app. Call before creating reviewCardDrafts so card types, note fields, layouts, and fallbacks match app import rules.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

granoflow_review_card_draft_skill ~70

Read the bundled core Granoflow review-card authoring skill. Call it for every lifecycle Card Checkpoint and every card search, link, create, or modification so similarity fallback, AI filtering, note quality, preview, approval, controlled writes, and readback use one workflow.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

granoflow_review_card_record ~101

Record a reusable review-card lesson through Granoflow's controlled work-memory API. The app may fail closed until controlled review-card import/create paths are available.

NameTypeReqDescription
clientstring––
dryRunboolean–When true, previews the request without writing.
problemstringyes–
solutionstringyes–
sourceobject––
tagsarray––
titlestringyes–

No output schema declared.

No examples provided.

granoflow_review_card_similar ~71

Find potentially similar Granoflow review cards. The app prefers vector search and falls back to agent-supplied keywords; the agent must prefilter results before showing them to the user.

NameTypeReqDescription
keywordsarray––
limitinteger––
summarystringyes–

No output schema declared.

No examples provided.

granoflow_review_day_show ~35

Show a Granoflow daily review by date.

NameTypeReqDescription
datestringyesDate in YYYY-MM-DD format.

No output schema declared.

No examples provided.

granoflow_setup_detect_local_api ~49

Probe a bounded localhost port list for Granoflow identity. This never scans all ports or writes config.

NameTypeReqDescription
portsarray––
timeoutMsinteger––

No output schema declared.

No examples provided.

granoflow_setup_open_app ~103

Preview or open the installed Granoflow app after user approval. Uses a cross-process launch lease for real opens, and refuses if another MCP launch is in progress, any Granoflow process is already running, or process state cannot be verified, even when the configured Local HTTP API URL or port is unreachable. Defaults to dry-run.

NameTypeReqDescription
appNamestring––
appPathstring––
dryRunboolean––

No output schema declared.

No examples provided.

granoflow_setup_open_config ~43

Create and optionally open the MCP-owned non-secret Granoflow config file.

NameTypeReqDescription
createIfMissingboolean––
openboolean––

No output schema declared.

No examples provided.

granoflow_setup_status ~26

Inspect Granoflow MCP config and Local HTTP API health without printing secrets.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

granoflow_setup_write_config ~70

Preview or write one user-confirmed MCP-owned non-secret Granoflow API URL or local port. Defaults to dry-run; writes are reread and verified immediately.

NameTypeReqDescription
apiBaseUrlstring––
apiPortinteger––
dryRunboolean––

No output schema declared.

No examples provided.

granoflow_source_tags_ensure ~63

Ensure the AI and 人工 completion source tags exist in Granoflow. Idempotent: reuses existing tags matched by slug or label.

NameTypeReqDescription
dryRunboolean–When true, only inspects the current catalog without creating missing tags.

No output schema declared.

No examples provided.

granoflow_tag_create ~62

Create a custom Granoflow tag. Defaults to dry-run.

NameTypeReqDescription
dryRunboolean–When true, previews the request without writing.
iconKeystring––
labelstringyes–
slugstring––

No output schema declared.

No examples provided.

granoflow_tag_list ~38

List tags from the Granoflow local catalog.

NameTypeReqDescription
kindstring–Optional tag kind filter forwarded to the Local HTTP API.

No output schema declared.

No examples provided.

granoflow_task_attachment_add_markdown ~88

Conditionally attach a versioned Task Work Document, legacy Task Analysis/Plan, or Task Delivery Markdown file and verify App-owned content/hash readback.

NameTypeReqDescription
dryRunboolean––
expectedTaskUpdatedAtstringyes–
filePathstringyes–
idempotencyKeystringyes–
taskIdstringyes–

No output schema declared.

No examples provided.

granoflow_task_attachment_delete ~51

Delete a task attachment after explicit confirmation.

NameTypeReqDescription
attachmentIdstringyes–
confirmedbooleanyes–
dryRunboolean––
taskIdstringyes–

No output schema declared.

No examples provided.

granoflow_task_attachment_list ~29

List attachments for a Granoflow task.

NameTypeReqDescription
taskIdstringyes–

No output schema declared.

No examples provided.

granoflow_task_attachment_read_markdown ~58

Read a bounded Task Work Document, legacy Task Analysis/Plan, or Task Delivery Markdown attachment with its App-owned SHA-256 for verification.

NameTypeReqDescription
attachmentIdstringyes–
taskIdstringyes–

No output schema declared.

No examples provided.

Common questions

What is the Granoflow MCP server?

Granoflow is an MCP server listed in the public MCP registry as com.granoflow/mcp-server. Connect MCP-capable AI agents to local Granoflow tasks, reviews, cards, imports, and work memory. This page covers its npm package (@granoflow/mcp-server).

Is the Granoflow MCP server safe to use?

Granoflow scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 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 Granoflow MCP server expose?

Granoflow exposes 129 tools: granoflow_agent_workflow_skill, granoflow_daily_review_skill, granoflow_first_run_import_skill, granoflow_review_card_draft_skill, granoflow_gfmcp_runner_skill, and 124 more. Their descriptions and schemas cost roughly 9,272 tokens of context every time the server is loaded.

Is the Granoflow MCP server still maintained?

Granoflow is still listed as active in the MCP registry. We last reached this channel on 24 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 Granoflow MCP server under?

Granoflow declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.