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.

KIP MCP Server

NPM · KIP-MCP-SERVER

Reads a boat's Signal K data and helps an AI assistant design and install KIP dashboards.

Available components

0 this week 96 Trust /100

Last scanned (16 hours ago)

Scores higher than 99% of npm servers

Category IoT and Hardware

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
  • 30 of 95 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 dillan/kip-mcp-server). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 132 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability86
  • 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
  • Tool/resource definitions use about 2437 tokens (~39/item across 61 items; 21 tools + 40 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 64% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • 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
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.

  • 3 Nov 26 0
    • Stability: 0.97 → pass security
  • 2 Nov 26 0
    • Stability: pass → 0.97 functional
  • 27 Oct 26 0
    • Stability: 0.97 → pass security
  • 26 Oct 26 0
    • Stability: pass → 0.97 functional
  • 20 Oct 26 0
    • Stability: 0.97 → pass security
  • 19 Oct 26 0
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +2
    • Stability: 0.87 → pass security
  • 15 Oct 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.

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 4 Nov 2026 · Analysed npm/kip-mcp-server@1.12.0

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 dillan/kip-mcp-server
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/dillan/kip-mcp-server/.github/workflows/release.yml@refs/heads/main
Rekor log index 1937788464
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:9684c2f1541ae5f72f7a19f3256e14a1d257a8b3bce390d811123b1a202abb321d60db86047076698c6c70bf709b749515ac02cfa4aa70385dc763158

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 21 exposed · ~1,257 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
analyze_signalk_data ~83

Analyse the boat's Signal K data: the available paths with units, the vessel capabilities, and installed plugins. Use this before recommending dashboards.

NameTypeReqDescription
cursorstring–Opaque token from a previous response, to fetch the next page.
limitinteger–Maximum paths to return. Omit to return all; with it, page using nextCursor.
NameTypeReqDescription
capabilitiesobjectyes–
nextCursorstring––
pathCountnumberyes–
pathsarrayyes–
pluginsarrayyes–
serverobjectyes–

No examples provided.

apply_kip_config ~108

Write dashboards to the KIP config on the Signal K server. Dry run by default — it shows what it would do; pass dryRun:false and confirm:true to actually write. Falls back to a file export on old servers.

NameTypeReqDescription
configNamestring––
confirmboolean––
dashboardsarrayyes–
dryRunboolean––
fileVersionnumber––
modestring––
scopestring––
NameTypeReqDescription
appliedboolean––
dryRunboolean––
errorsarray––
notestring––
okboolean––
reasonstring––
refusedboolean––
suggestionstring––
warningsarray––
wouldWritearray––
wrotearray––

No examples provided.

backup_kip_config ~51

Return the current stored KIP config so it can be kept as a backup before changes.

NameTypeReqDescription
configNamestring––
fileVersionnumber––
scopestring––
NameTypeReqDescription
backup–––
existsbooleanyes–

No examples provided.

check_connection ~70

Run connection diagnostics against the live Signal K server and KIP install: server reachable, version supports the applicationData write store (>= 1.27), the KIP schema asset is served live, and authentication works when credentials are set. Reports each check as pass, warn or fail with plain-language guidance.

Input schema present but exposes no named parameters.

NameTypeReqDescription
checksarrayyes–
okbooleanyes–
summarystringyes–

No examples provided.

compose_dashboard ~123

Design one KIP dashboard for an intent by binding widgets to the boat's data. Returns the dashboard, an ASCII preview, and what was left out. Does not write anything.

NameTypeReqDescription
iconstring–Override the dashboard icon.
intentstringyesWhich dashboard to design.
namestring–Override the dashboard name.
sourcesobject–Pick a non-default Signal K source per path: map a path (e.g. "navigation.speedOverGround") to a source id from get_path_sources. Paths not listed use the server default.
NameTypeReqDescription
dashboardobjectyes–
droppedarrayyes–
notesarrayyes–
previewstringyes–

No examples provided.

export_kip_config ~91

Build a complete KipConfig.json from dashboards that a user can import via KIP Settings. Works on any Signal K server (no write to the server). Returns the file contents.

NameTypeReqDescription
dashboardsarrayyesDashboards to include.
themestring–Theme name (default '').
unitsobject–Unit-default overrides, e.g. { Speed: "kph" }.
NameTypeReqDescription
filenamestringyes–
jsonstringyes–

No examples provided.

get_design_system ~30

Get KIP's design system: grid, colour tokens, theme names, dashboard icons and unit groups.

Input schema present but exposes no named parameters.

NameTypeReqDescription
colorsarrayyes–
gridobjectyes–
iconsarrayyes–
themeNamesarrayyes–
unitGroupsarrayyes–

No examples provided.

get_kip_initial_context ~32

Start here. Explains how to design KIP dashboards and summarises the available widgets and design system.

Input schema present but exposes no named parameters.

NameTypeReqDescription
categoriesarrayyes–
colorTokensarrayyes–
gridobjectyes–
kipVersionstringyes–
overviewstringyes–
widgetCountnumberyes–

No examples provided.

get_path_meta ~37

Get metadata (units, description, value type, zones) for specific Signal K paths.

NameTypeReqDescription
pathsarrayyesPaths to describe.
NameTypeReqDescription
metaarrayyes–

No examples provided.

get_path_sources ~44

List the data sources reporting each Signal K path, and which source the server currently serves as the active one.

NameTypeReqDescription
pathsarrayyesPaths to list the sources for.
NameTypeReqDescription
sourcesarrayyes–

No examples provided.

get_server_info ~18

Get the Signal K server version and id.

Input schema present but exposes no named parameters.

NameTypeReqDescription
serverIdstring––
versionstringyes–

No examples provided.

get_unit_options ~55

For a Signal K base unit (e.g. rad, m/s, K, Pa), list the KIP unit group and convertible measures.

NameTypeReqDescription
skUnitstringyesSignal K base unit, e.g. rad.
NameTypeReqDescription
foundbooleanyes–
groupstring––
measuresarray––
notestring––
skUnitstringyes–

No examples provided.

get_widget_schema ~39

Get one widget's default config, binding kind and data path slots.

NameTypeReqDescription
selectorstringyesWidget selector, e.g. widget-numeric.
NameTypeReqDescription
widgetobjectyes–

No examples provided.

list_available_paths ~84

List the Signal K data paths available on the boat, optionally filtered by prefix.

NameTypeReqDescription
cursorstring–Opaque token from a previous response, to fetch the next page.
limitinteger–Maximum paths to return. Omit to return all; with it, page using nextCursor.
prefixstring–Only list paths starting with this prefix.
NameTypeReqDescription
nextCursorstring––
pathsarrayyes–

No examples provided.

list_installed_plugins ~22

List the Signal K server plugins and whether each is enabled.

Input schema present but exposes no named parameters.

NameTypeReqDescription
pluginsarrayyes–

No examples provided.

list_kip_widgets ~61

List KIP's widget catalog, optionally filtered by category or to widgets that need no plugins.

NameTypeReqDescription
categorystring–Only list widgets in this category.
requiresNoPluginsboolean–Only list widgets that work with no Signal K plugins.
NameTypeReqDescription
widgetsarrayyes–

No examples provided.

preview_dashboard ~69

Render a preview of a dashboard object (as returned by compose_dashboard): a text grid (ascii, the default) or an SVG picture (svg).

NameTypeReqDescription
dashboardobjectyesA KIP dashboard object.
formatstring–Preview format: "ascii" (default) or "svg".
NameTypeReqDescription
asciistring––
svgstring––

No examples provided.

read_kip_config ~52

Read the KIP config stored on the Signal K server, and list the available config names.

NameTypeReqDescription
configNamestring––
fileVersionnumber––
scopestring––
NameTypeReqDescription
config–––
existsbooleanyes–
listingarray––

No examples provided.

recommend_dashboard_set ~57

Recommend a set of KIP dashboards for this boat: the use-case dashboards its data supports, each with a preview. Does not write anything.

NameTypeReqDescription
intentsarray–Limit to these intents (default: all that the boat supports).
NameTypeReqDescription
dashboardsarrayyes–
unsupportedarrayyes–

No examples provided.

validate_against_signalk ~69

Check a KIP dashboard against the live boat: that every bound data path exists, the widgets' required plugins are installed and enabled, and the units match. The live counterpart of validate_kip_config (which only checks structure).

NameTypeReqDescription
dashboardobjectyesA KIP dashboard object.
NameTypeReqDescription
checkedPathsnumberyes–
missingPathsarrayyes–
okbooleanyes–
pluginIssuesarrayyes–
unitMismatchesarrayyes–
warningsarrayyes–

No examples provided.

validate_kip_config ~62

Validate a KIP dashboard object: structure, the widget-host2 invariants (id===uuid, known widget types), grid bounds, overlaps, and colour/icon/unit sanity. Returns errors and warnings.

NameTypeReqDescription
dashboardobjectyesA KIP dashboard object.
NameTypeReqDescription
errorsarrayyes–
okbooleanyes–
warningsarrayyes–

No examples provided.

Install

How do I install the KIP MCP Server server?

KIP MCP Server runs locally as an npm package, launched with npx -y kip-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 · kip-mcp-server

# add to Claude Code
claude mcp add dillan-kip-mcp-server -- npx -y kip-mcp-server
Common questions

What is the KIP MCP Server server?

KIP MCP Server is listed in the public MCP registry as io.github.dillan/kip-mcp-server. Reads a boat's Signal K data and helps an AI assistant design and install KIP dashboards. This page covers its npm package (kip-mcp-server).

Is the KIP MCP Server server safe to use?

KIP MCP Server scores 96 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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 KIP MCP Server server expose?

KIP MCP Server exposes 21 tools: get_kip_initial_context, list_kip_widgets, get_widget_schema, get_design_system, get_unit_options, and 16 more. Their descriptions and schemas cost roughly 1,257 tokens of context every time the server is loaded.

Is the KIP MCP Server server still maintained?

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

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