Skip to content

MCP servers › io.github.Kernel-Hunter › kandle

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.Kernel-Hunter/kandle

Read and draw on a live crypto, stock or forex chart, run scripts and backtests. — the publisher's description

5 of 5 record checks metRead-only · tools listed 2026-10-23Topic: finance-and-payments · AI-classifiedversion 0.10.1TypeScriptstandard input/output26 tools

Summary

io.github.Kernel-Hunter/kandle is a local MCP server listed in the official MCP registry at version 0.10.1. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 26 tools, 0 resources and 0 prompts.

Record checks

5 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: not an npm or PyPI package
  • Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
local package
Transport
standard input/output
Package
MCP bundle
Repository
public
Tools
26
Described as changing data
16 of 26 toolsAI-classified
Topic
finance-and-paymentsAI-classified
Last tested
2026-10-23

Add to your client

Worth knowing before you connect it

  • 16 tools are described as changing something (set_symbol, set_timeframe, add_indicator, …): our AI model's reading of the descriptions, not something we tested. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
0.10.1, published 2026-10-21 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-19 (earliest version still in the registry; older removed versions would be earlier)
Version history
10 versions listed, 2026-10-19 to 2026-10-21; 10 in the 90 days before the 2026-10-23 snapshot.
Most recent 10 versions
  • 0.10.1 · 2026-10-21
  • 0.10.0 · 2026-10-21
  • 0.9.0 · 2026-10-21
  • 0.8.0 · 2026-10-21
  • 0.7.0 · 2026-10-20
  • 0.6.0 · 2026-10-20
  • 0.5.0 · 2026-10-20
  • 0.4.0 · 2026-10-20
  • 0.3.0 · 2026-10-19
  • 0.2.2 · 2026-10-19
(versions still listed in the registry only)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-23
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.10.1 (published 2026-10-21).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
26tools
0resources
0prompts

16 of 26 tools are described as changing something (creating, editing, deleting, sending or running). For 1 the reading was uncertain, so no mark is shown.

  • get_bridge_statuson 1 other serverreads or searches

    “Shows whether the Kandle app is connected and, if not, the pairing code the user must enter in Kandle (Agent button, then Agent bridge).”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • get_chart_statereads or searches

    “Symbol, exchange, timeframe, last price, visible range, indicators with their latest values, drawings with ids, alerts, replay and layout state.”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input
    • paneinteger“Chart pane, 1 to 4 in reading order.”
  • set_symbolcreates or changes datadescribed as changing data

    “Switches the chart to another market, e.g.”

    Publisher declares: read-only no · destructive no · open-world no

    3 inputs, 1 required
    • symbolstringrequired“Market symbol such as BTCUSDT, ETH/USDT or BTC-USD”
    • exchangestring“Data source.”
    • paneinteger“Chart pane, 1 to 4 in reading order.”
  • set_timeframecreates or changes datadescribed as changing data

    “Changes the bar size of the chart.”

    Publisher declares: read-only no · destructive no · open-world no

    2 inputs, 1 required
    • timeframestringrequired“Bar size: 1m, 5m, 15m, 1h, 4h, 1D or 1W”
    • paneinteger“Chart pane, 1 to 4 in reading order.”
  • get_candleson 14 other serversreads or searches

    “OHLCV bars from the chart, newest last.”

    Publisher declares: read-only yes · destructive no · open-world no

    5 inputs
    • limitinteger“Most recent bars to return (default 200, max 5000)”
    • fromnumber or string“Only bars at or after this time”
    • tonumber or string“Only bars at or before this time”
    • include_indicatorsboolean“Add the values of indicators on the chart for each bar”
    • paneinteger“Chart pane, 1 to 4 in reading order.”
  • add_indicatorcreates or changes datadescribed as changing data

    “Adds an indicator such as RSI, MACD, EMA, BOLL, ICHIMOKU or VP (volume profile).”

    Publisher declares: read-only no · destructive no · open-world no

    3 inputs, 1 required
    • namestringrequired“Indicator name from list_indicators, e.g.”
    • paramsarray“Calculation parameters, e.g.”
    • paneinteger“Chart pane, 1 to 4 in reading order.”
  • remove_indicatordeletesdescribed as changing data

    “Removes an indicator by id, or every indicator with a name.”

    Publisher declares: read-only no · destructive yes · open-world no

    3 inputs
    • idstring“Indicator id from list_indicators”
    • namestring“Remove every indicator with this name instead”
    • paneinteger“Chart pane, 1 to 4 in reading order.”
  • list_indicatorson 8 other serversreads or searches

    “Indicators on the chart (with ids, parameters and latest values) and every indicator that can be added.”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input
    • paneinteger“Chart pane, 1 to 4 in reading order.”
  • drawon 5 other serverscreates or changes datadescribed as changing data

    “Draws on the main chart by price and time: trend_line, horizontal_line, horizontal_ray, vertical_line, ray, extended_line, rectangle, fib (retracement from the first point to the second), text (a not…”

    Publisher declares: read-only no · destructive no · open-world no

    3 inputs, 2 required
    • typestringrequired“What to draw”
    • pointsarrayrequired“Anchor points.”
    • textstring“Label for text notes”
  • remove_drawingdeletesdescribed as changing data

    “Removes one drawing by id.”

    Publisher declares: read-only no · destructive yes · open-world no

    1 input, 1 required
    • idstringrequired“Drawing id from get_chart_state or draw”
  • clear_drawingsdeletesdescribed as changing data

    “Removes every drawing on the current symbol of the main chart.”

    Publisher declares: read-only no · destructive yes · open-world no

    Takes no inputs.

  • run_scripton 13 other serversruns code or commandsdescribed as changing data

    “Runs a Kandle script on the main chart and returns its id and latest plot values, or the error with line and column.”

    Publisher declares: read-only no · destructive no · open-world no

    5 inputs, 1 required
    • codestringrequired“Script source code”
    • namestring
    • idstring“Id of a script from an earlier run_script, to replace it instead of adding another”
    • inputsobject“Input values by input title, e.g.”
    • strategyobject“Backtest settings that replace the ones in the strategy() call, e.g.”
Show 14 more tools
  • get_backteston 5 other serversreads or searches

    “Backtest results of a strategy script on the main chart: settings in use (and changedSettings, those that differ from the strategy() call; settings.risk lists the strategy.risk.* rules the script set…”

    Publisher declares: read-only yes · destructive no · open-world no

    2 inputs
    • idstring“Script id from run_script.”
    • tradesinteger“How many of the latest closed trades to include (default 50, max 500)”
  • screenshoton 82 other serversreads or searches

    “PNG image of a chart pane, including indicators and drawings.”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input
    • paneinteger“Chart pane, 1 to 4 in reading order.”
  • set_alerton 4 other serverscreates or changes datadescribed as changing data

    “Creates an alert on the main chart's symbol: price crossing or touching a level, price crossing a drawn horizontal or trend line, or an indicator line crossing a level.”

    Publisher declares: read-only no · destructive no · open-world no

    8 inputs, 1 required
    • typestringrequired“price: a price level.”
    • conditionstring“Default crosses.”
    • levelnumber“Price level for price alerts, or value level for indicator alerts”
    • drawing_idstring“Drawing id for drawing alerts”
    • indicator_idstring“Indicator id for indicator alerts”
    • indicator_linestring“Which line of the indicator, e.g.”
    • frequencystring“once (default) disables the alert after it fires; every_time fires at most once per bar”
    • messagestring
  • list_alertson 26 other serversreads or searches

    “Every alert with its status.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • remove_alertdeletesdescribed as changing data

    “Deletes an alert by id, or all alerts with "all".”

    Publisher declares: read-only no · destructive yes · open-world no

    1 input, 1 required
    • idstringrequired“Alert id, or "all"”
  • get_watchliston 13 other serversreads or searches

    “Symbols in the watchlist panel with their exchange, last price, change and change percent.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • add_to_watchliston 9 other serverscreates or changes datadescribed as changing data

    “Adds a symbol to the watchlist, on the main chart's exchange unless exchange is given.”

    Publisher declares: read-only no · destructive no · open-world no

    2 inputs, 1 required
    • symbolstringrequired“Market symbol such as SOLUSDT, ETH-USD or AAPL”
    • exchangestring“Data source of the row.”
  • remove_from_watchliston 9 other serversdeletesdescribed as changing data

    “Removes a symbol from the watchlist, or every symbol with "all".”

    Publisher declares: read-only no · destructive yes · open-world no

    2 inputs, 1 required
    • symbolstringrequired“Symbol to remove, or "all" to empty the watchlist”
    • exchangestring“Only needed when the symbol is listed on more than one exchange”
  • start_replaycreates or changes datadescribed as changing data

    “Hides bars after a start point so the chart can be replayed bar by bar.”

    Publisher declares: read-only no · destructive no · open-world no

    4 inputs
    • start_timenumber or string“Replay starts with this bar as the last visible one”
    • bars_backinteger“Or start this many bars before the latest bar (default 100)”
    • speedinteger“Bars per second when playing, 1 to 10”
    • autoplayboolean“Start playing right away instead of waiting for step_replay”
  • step_replayreads or searches

    “Reveals the next bars in replay and returns them.”

    Publisher declares: read-only no · destructive no · open-world no

    1 input
    • barsinteger“Bars to reveal (default 1)”
  • stop_replaycreates or changes datadescribed as changing data

    “Leaves replay and returns the chart to live data.”

    Publisher declares: read-only no · destructive no · open-world no

    Takes no inputs.

  • set_layouton 2 other serverscreates or changes datadescribed as changing data

    “Shows 1, 2 (side by side) or 4 (grid) charts.”

    Publisher declares: read-only no · destructive no · open-world no

    3 inputs, 1 required
    • chartsnumberrequired“Number of charts: 1, 2 side by side, or 4 in a grid”
    • syncobject“Keep these in step across charts”
    • panesarray“Optional symbol and timeframe per pane, in reading order”
  • set_chart_stylecreates or changes datadescribed as changing data

    “Changes how a chart draws its bars (candles, hollow_candles, bars, line, area or heikin_ashi) and its price scale (normal, log or percent).”

    Publisher declares: read-only no · destructive no · open-world no

    3 inputs
    • typestring“How bars are drawn.”
    • scalestring“Price axis: normal, log (logarithmic) or percent (change from the first bar on screen)”
    • paneinteger“Chart pane, 1 to 4 in reading order.”
  • get_share_linkon 1 other serverreads or searches

    “A link that opens the main chart in Kandle for anyone: exchange, symbol, timeframe, chart type, scale, visible range, indicators and drawings, and optionally scripts and the multi-chart layout.”

    Publisher declares: read-only yes · destructive no · open-world no

    2 inputs
    • includeobject“What the link carries besides the exchange, symbol and timeframe of the main chart”
    • embedboolean“Also return embed_url and iframe, HTML that shows the chart on another web page with a link back to Kandle (default false).”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 26 tools
Says what it returns
54% of 26 tools
States limits, defaults or errors
12% of 26 tools
Says when to use it
0% of 24 tools
Items covered per tool
1.7 of 4 on average

Counted from the listing

Parameters with a description
96% of 56
Tools with a description
100% of 26
Typical description length
176 characters

The tool set

Counted from the listing

Tools
26
Size of the list
about 5,913 tokens for an agent to load (characters ÷ 4)
Naming
24 of 26 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 26 of 26 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry
  • No config: the MCP bundle is a file to install in a client that supports bundles, not a command.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Published package can be startedStarted and answeredmatchesour test · 2026-10-23
Repository github.com/Kernel-Hunter/kandleOpens publiclymatchesapi.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.Kernel-Hunter
GitHub owner
a personal account (Kernel-Hunter)
Repository
github.com/Kernel-Hunter/kandle
Stars
0
Repository age
0–30 days
Last push
0–30 days ago
Archived
no
Security policy
SECURITY.md

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

5 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: not an npm or PyPI package
  • Not ranked by stars: 0 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
  • Does not applyPackage names its licence with a standard (SPDX) identifierNot an npm or PyPI package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnNot an npm or PyPI package.
  • Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
  • Does not applyNo known critical or high advisory in the package or its dependenciesNot an npm or PyPI package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.Kernel-Hunter/kandle

Answered from the data above

Is io.github.Kernel-Hunter/kandle safe to install?

We do not rate servers as safe or unsafe. 5 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. 16 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.Kernel-Hunter/kandle been security tested?

Partly. 2 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.Kernel-Hunter/kandle do?

It lists 26 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete and run code or commands. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.Kernel-Hunter/kandle change or delete data?

16 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.Kernel-Hunter/kandle publish a security policy?

Yes: its repository has a public security policy (github.com/kernel-hunter/kandle/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Where is the source code of io.github.Kernel-Hunter/kandle?

In github.com/Kernel-Hunter/kandle, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “finance-and-payments” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not applicable
  17. Consent handling: not applicable
  18. Sign-in metadata: not applicable

2 exercised10 not run (reason given)6 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 12 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 10
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
Does not apply to this server · 6
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted the published package in an isolated sandbox (read-only mode)
  2. 194 msConnected after 0 redirects.
  3. Read the inventory: 26 tools, 0 resources, 0 prompts.
  4. 1,360 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
AI-classified · 2026-10-23
Pricing modelAI-classified
not known (our limit)
The website shows almost no text without JavaScript, and we did not re-read it in a browser. This is our limit.
Programming language
api.github.com · 2026-10-23
Hosting type
registry · 2026-10-23
MCP capability
tools
our test · 2026-10-23
Transport
standard input/output
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
registry · 2026-10-23
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Integrity hash
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Signature / provenance
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Dependency advisories
not checked
only npm and PyPI packages are audited
Popularity
does not apply
package ecosystem not queried by this layer (mcpb); only npm and PyPI are supported here
Publisher signals
owner: a personal account · repository age: 0–30 days · stars: 0–9
api.github.com · 2026-10-23
Maintenance
api.github.com · 2026-10-23
Environment
your machine
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.Kernel-Hunter/kandle: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.Kernel-Hunter/kandle

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 5 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.Kernel-Hunter/kandle)](https://protocolprobe.com/mcp/servers/io.github.Kernel-Hunter/kandle)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology