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.

gently

NPM · @GENTLY/MCP-SERVER · 2 COMPONENTS · SCANNED SEP 20

Ask a codebase what calls what: search, blast radius, paths between symbols, and diffs.

Available components

remote · api.stage.gently.is 36 npm · @gently/mcp-server 76
0 this week 76 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
  • 32 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • 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
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1065 tokens (~177/item across 6 items; 6 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 Management90
  • Stability observed for 27 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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 gently MCP server?

gently runs locally as an npm package, launched with npx -y @gently/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 · @gently/mcp-server

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

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 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 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 −3
    • Stability: pass → 0.83 functional
  • 10 Sept 26 +1
    • Stability: 0.97 → pass security
  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 20 Sept 2026 · Analysed npm/@gently/mcp-server@0.1.22

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 98 packages
Packages resolved 98
Stale 31
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~1,065 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
gently_diff ~128

Compare graph between two refs (and optional generation numbers). Prefer this to understand what a branch changes vs its base.

NameTypeReqDescription
baseAtinteger–Optional generation number on the base ref
baseRefstringyesBase ref (branch) to compare from
headAtinteger–Optional generation number on the head ref
headRefstringyesHead ref (branch) to compare to
limitinteger–Max diff entries to return (default 500)
sourcestring–Optional source filter (e.g. github:owner/repo)

No output schema declared.

No examples provided.

gently_impact ~189

List callers/callees/endpoints affected by changing a symbol, file, or HTTP endpoint (name or URN). Defaults to foreign impact around this checkout.

NameTypeReqDescription
depthinteger–How many hops to open inside the foreign repo after the first cross-source edge (not hops inside this checkout)
detailstring–compact (default) returns denser citations; full adds path/line/via endpoints
includeLocalboolean–When false (default), omit local-only nodes from the payload; keep foreign nodes plus local bridge call sites
scopestring–Anchor: repo = foreign graph around this checkout; tenant = whole workspace without requiring a local anchor
targetstringyesSymbol name, file path, HTTP endpoint (e.g. POST /todos), or URN
viewstring–View identifier; defaults to tenant default view

No output schema declared.

No examples provided.

gently_path ~183

Show how two symbols, files, or endpoints are connected across repos (names or URNs)

NameTypeReqDescription
depthinteger–How many hops to open inside the foreign repo after the first cross-source edge (not hops inside this checkout)
detailstring–compact (default) returns denser citations; full adds path/line/via endpoints
fromstringyesSource symbol, file, endpoint, or URN
includeLocalboolean–When false (default), omit local-only nodes from the payload; keep foreign nodes plus local bridge call sites
scopestring–Anchor: repo = foreign graph around this checkout; tenant = whole workspace without requiring a local anchor
tostringyesDestination symbol, file, endpoint, or URN
viewstring–View identifier; defaults to tenant default view

No output schema declared.

No examples provided.

gently_query ~200

Foreign-first graph context anchored on this checkout: ranked matches, neighbors across repos, and explicit cross-repo bridges. Prefer this before gently_impact / gently_path. Local intra-repo structure is read from files, not this tool.

NameTypeReqDescription
depthinteger–How many hops to open inside the foreign repo after the first cross-source edge (not hops inside this checkout)
detailstring–compact (default) returns denser citations; full adds path/line/via endpoints
includeLocalboolean–When false (default), omit local-only nodes from the payload; keep foreign nodes plus local bridge call sites
questionstringyesNatural-language question or keywords (e.g. POST /todos, TODO_API_URL)
scopestring–Anchor: repo = foreign graph around this checkout; tenant = whole workspace without requiring a local anchor
viewstring–View identifier; defaults to tenant default view

No output schema declared.

No examples provided.

gently_scip_sync ~177

Check the caller's per-identity SCIP head and upload only when the local index hash differs. Prefer this over gently_upload_scip for routine enrichment. Uses GENTLY_SCIP_PATH or .gently/index.scip.json. Auto-runs once on MCP boot when GENTLY_SCIP_AUTO is unset/1 (set 0 to disable). Requires graph:read + graph:write when an upload is needed.

NameTypeReqDescription
forceboolean–Upload even when local hash matches the server head
pathstring–Optional SCIP JSON path (default GENTLY_SCIP_PATH or .gently/index.scip.json)
refstring–Graph ref / branch (defaults to GENTLY_REF or main)
sourcestring–Source tag github:org/repo (defaults to ambient checkout)

No output schema declared.

No examples provided.

gently_upload_scip ~188

Opt-in only: upload a simplified SCIP JSON index (ADR-0010) to enrich CALLS/IMPORTS with provenance=scip. Call ONLY when the operator explicitly asks to upload/enrich SCIP — never on ordinary query/impact/path turns. Prefer CI (gently-mcp-scip-upload). Provide path or inline index. Requires graph:write. Bodies over 1 MiB are rejected.

NameTypeReqDescription
connectorIdstring–Optional connector id recorded on the generation
indexobject–Inline simplified SCIP JSON (documents[]) when not using path
pathstring–Path to simplified SCIP JSON on disk (relative to the workspace cwd or absolute)
refstring–Graph ref / branch (defaults to GENTLY_REF or main)
sourcestring–Source tag github:org/repo (defaults to this checkout's ambient source)

No output schema declared.

No examples provided.

Common questions

What is the gently MCP server?

gently is an MCP server listed in the public MCP registry as is.gently/knowledge-graph. Ask a codebase what calls what: search, blast radius, paths between symbols, and diffs. This page covers its npm package (@gently/mcp-server).

Is the gently MCP server safe to use?

gently scores 76 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 gently MCP server expose?

gently exposes 6 tools: gently_query, gently_impact, gently_path, gently_diff, gently_upload_scip, gently_scip_sync. Their descriptions and schemas cost roughly 1,065 tokens of context every time the server is loaded.

Is the gently MCP server still maintained?

gently 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 gently MCP server under?

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