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.CoralLips/gft-mcp

NPM · GFT-MCP · SCANNED SEP 30

Bring your GFT (Git for Thought) white-box thinking map to any AI agent. 把你的思维脉络接给任何 agent。

Available components

0 this week 83 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 101 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 728 tokens (~242/item across 3 items; 3 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 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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 io.github.CoralLips/gft-mcp server?

io.github.CoralLips/gft-mcp runs locally as an npm package, launched with npx -y gft-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 · gft-mcp

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

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

  • 28 Sept 26 −3
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 0
    • Stability: 0.97 → pass security
  • 26 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.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 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.

  • 22 Sept 26 −2
    • Stability: pass → 0.83 functional
  • 21 Sept 26 0
    • Stability: 0.97 → pass security
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 30 Sept 2026 · Analysed npm/gft-mcp@0.1.4

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

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~728 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
list_thinking_maps ~98

列出用户在 GFT 的全部思维脉络:图名、判断条数、各线新鲜度(哪条线最后什么时候喂过图)。 什么时候调用:本场还没链接任何脉络、需要帮用户选图时;或用户问"我有哪些脉络"。 轻查询,不含节点内容——选定后用 read_thinking_map 读取。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

read_thinking_map ~326

读取用户在 GFT(gitforthought.com)里逐条确认过的思考资产——他的「思维脉络」:已经想通的判断、还悬着的问题、已经否决的方向。 什么时候调用:用户提到他之前的判断/想法/正在纠结的问题时;或你要给出建议、而这个建议应该建立在他已有的思考之上时;或他直接说「读一下我的脉络」时。 一场会话拉一次即可——内容不会在对话中途改变,反复调用只是浪费用户的 token。 选图:本场聊过哪张就继续用哪张;语境不明且用户没指名时,把返回里列出的可选项目报给用户挑,**不要赌"最近更新的那张"**——那可能是用户在别的 session 里喂的图。 若用户要把这场对话的新判断存进脉络,用 for_update=true 再调一次:会额外返回抽取规则和旧图别名,按那份规则抽完再调 submit_map_update。

NameTypeReqDescription
for_updateboolean–要往脉络里补新判断时传 true,会附带抽取规则与旧图别名。默认 false。
projectstring–按项目名模糊匹配指定读哪张脉络。不传 = 最近更新的那张(多数情况不用传)。

No output schema declared.

No examples provided.

submit_map_update ~304

把这场对话里长出来的新判断增量并入用户的思维脉络。 **必须先调 read_thinking_map(for_update=true)**,拿到抽取规则和旧图别名,按那份规则抽出 <node/> / <edge/> 标签后,原样传进 tags。 规则由 GFT 定,你只出算力:只抽用户真说了的判断,你自己的分析除非他明确接住否则不上图;旧节点一律不重输出;没有新东西就传 <noop/>。

NameTypeReqDescription
agent_idstring–你这条对话线的稳定标识(如工作目录名或话题名)。同一张图可能被多个 session 喂,水位按此分开记,别省略。
cursorstring–本次抽到哪的标记,下次接着走。例:"2026-08-05 关于 MCP 外接的讨论,至第 40 轮"。
projectstring–写进哪张脉络,同 read_thinking_map。不传 = 最近更新的那张。
tagsstringyes按规则抽出的标签原文,一行一个,如:<node id="m1" title="..." body="..."/> 与 <edge from="n2" to="m1"/>。没有新东西时传 <noop/>。

No output schema declared.

No examples provided.

Common questions

What is the io.github.CoralLips/gft-mcp server?

io.github.CoralLips/gft-mcp is listed in the public MCP registry as io.github.CoralLips/gft-mcp. Bring your GFT (Git for Thought) white-box thinking map to any AI agent. 把你的思维脉络接给任何 agent。 This page covers its npm package (gft-mcp).

Is the io.github.CoralLips/gft-mcp server safe to use?

io.github.CoralLips/gft-mcp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 30 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.CoralLips/gft-mcp server expose?

io.github.CoralLips/gft-mcp exposes 3 tools: list_thinking_maps, read_thinking_map, submit_map_update. Their descriptions and schemas cost roughly 728 tokens of context every time the server is loaded.

Is the io.github.CoralLips/gft-mcp server still maintained?

io.github.CoralLips/gft-mcp is still listed as active in the MCP registry. We last reached this channel on 30 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.CoralLips/gft-mcp server under?

io.github.CoralLips/gft-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.