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.

Maple

NPM · @MAPLE-KIT/MCP

Review comments pinned to a running frontend, read and resolved by your coding agent.

Available components

+1 this week 83 Trust /100

Last scanned (22 hours ago)

Scores higher than 79% of npm servers

Category Version Control

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.30.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 99 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to maple-kit/maple). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 428 tokens (~85/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
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.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +5
    • Stability: unverified → 0.37 ▲ functional
  • 12 Oct 26 +1
    • Security disclosure: unverified → pass ▲ functional
  • 11 Oct 26 −6
    • CVE-2026-104850 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
    • Security disclosure: pass → unverified ▼ functional
  • 4 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Oct 26 67

    First indexed and scored.

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 16 Oct 2026 · Analysed npm/@maple-kit/mcp@0.17.1

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 maple-kit/maple
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/maple-kit/maple/.github/workflows/release.yml@refs/heads/main
Rekor log index 3070727821
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:09b613e161962c46be2ee2616d3e1c1ecc240cc4cc00adf59ea31a3c77f98b18413bb0c3c4f269c177ec54fda39310781792ece6fc640b488dd67b5b9

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-6qxp-vccf-f47h CVE-2026-104850 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 99 packages
Packages resolved 99
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~428 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
get_comment_context ~96

Return everything needed to act on one comment: anchor, viewport, surrounding markup and any replay link. A comment written under a Maple Mock carries `mock.recipe` and `mock.replay`, a link to the page in that state.

NameTypeReqDescription
branchstringyesHead branch of the pull request the comments are on, such as `feat/login`. Not a pull request number.
idstringyesThe comment's id.

No output schema declared.

No examples provided.

list_comments ~65

Return the review comments on a branch, newest first.

NameTypeReqDescription
branchstringyesHead branch of the pull request the comments are on, such as `feat/login`. Not a pull request number.
statusesarray–Only these states. Omit for all of them.

No output schema declared.

No examples provided.

resolve_comment ~57

Mark a comment resolved, recording the commit that addressed it.

NameTypeReqDescription
idstringyesThe comment's id.
notestring–What you changed, for the reviewer.
shastringyesCommit you believe addresses it.

No output schema declared.

No examples provided.

start_solo ~96

Start a bridge on localhost and return the link that pairs a deployed preview with it. The reviewer opens the link in their browser and the comments they write there land in .maple/ for list_comments and wait_for_comments to read. They never count toward the merge gate.

NameTypeReqDescription
previewUrlstringyesThe deployed preview's URL, such as `https://feat-login.preview.example`. Only that origin is paired with the bridge.

No output schema declared.

No examples provided.

wait_for_comments ~114

Block until a new comment arrives or the wait elapses. Returns status "timeout" rather than failing when nothing arrives.

NameTypeReqDescription
branchstringyesHead branch of the pull request the comments are on, such as `feat/login`. Not a pull request number.
cursorstring–Timestamp from a previous call. Only comments newer than this are returned; omit it to drain everything already there.
timeoutMsnumber–How long to wait. Clamped to 55 seconds, under every client's ceiling.

No output schema declared.

No examples provided.

Install

How do I install the Maple MCP server?

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

# add to Claude Code
claude mcp add maple-kit-maple -- npx -y @maple-kit/mcp
Common questions

What is the Maple MCP server?

Maple is an MCP server listed in the public MCP registry as io.github.maple-kit/maple. Review comments pinned to a running frontend, read and resolved by your coding agent. This page covers its npm package (@maple-kit/mcp).

Is the Maple MCP server safe to use?

Maple scores 83 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 16 October 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 Maple MCP server expose?

Maple exposes 5 tools: list_comments, wait_for_comments, resolve_comment, get_comment_context, start_solo. Their descriptions and schemas cost roughly 428 tokens of context every time the server is loaded.

Is the Maple MCP server still maintained?

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

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