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.kaiser-data/kitsune-mcp

PYPI · KITSUNE-MCP · 2 COMPONENTS · SCANNED SEP 20

Shape-shifting MCP hub — shapeshift() into 130,000+ servers at runtime. No restarts. 7 registries.

0 this week 80 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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 0 of 29 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • 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 12 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1024 tokens (~113/item across 9 items; 9 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 Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage76
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 14% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "release" implies "kill" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 9 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.kaiser-data/kitsune-mcp server?

io.github.kaiser-data/kitsune-mcp runs locally as a PyPI package, launched with uvx kitsune-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · kitsune-mcp

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

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

  • 18 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 17 Sept 26 0
    • Stability: 0.97 → pass security
  • 16 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.

  • 15 Sept 26 +15
    • Malware scan: unverified → pass security
  • 14 Sept 26 −15
    • Malware scan: pass → unverified security
  • 13 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.

  • 12 Sept 26 +15
    • Malware scan: unverified → 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 20 Sept 2026 · Analysed pypi/kitsune-mcp@0.21.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 29 packages
Packages resolved 29
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~1,024 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
auth ~102

Check or set credentials. ALL_CAPS = env var; server-id = creds check or OAuth. auth('GITHUB_TOKEN', 'ghp_...') # save env var auth('GITHUB_TOKEN') # check if set auth('server-id') # show creds needed / run OAuth auth('server-id', 'logout') # revoke OAuth tokens

NameTypeReqDescription
server_id_or_varstringyes
valuestring
NameTypeReqDescription
resultstringyes

No examples provided.

auto ~81

search → pick server → infer args → call. Use when you don't know which server to use. auto('what time in Tokyo') auto('list issues on acme/api', server_hint='github')

NameTypeReqDescription
arguments
keys
server_hintstring
taskstringyes
tool_namestring
NameTypeReqDescription
resultstringyes

No examples provided.

call ~196

Invoke a tool on an MCP server. Returns the tool's response as text. Routes through the warm pooled transport when a server is shapeshifted; otherwise spins up a transient transport for the given server_id. Records the call in session stats. Long responses (HTML, large outputs) are truncated with a continuation note. Use when: the tool name and target server are known. Avoid when: discovery is needed — auto() does search → pick → call in one step. call('get_current_time', arguments={'timezone': 'UTC'}) # after shapeshift call('list_directory', '@mcp/server-fs', {'path': '/tmp'}) # ad-hoc one-shot

NameTypeReqDescription
argumentsTool arguments matching its inputSchema (default {})
config
server_idDefaults to the currently shapeshifted form when omitted
tool_namestringyes
NameTypeReqDescription
resultstringyes

No examples provided.

connect ~65

Start a persistent server. command: server_id or shell cmd (e.g. 'uvx voice-mode'). name: alias for release().

NameTypeReqDescription
commandstringyes
inherit_stderrboolean
namestring
timeoutinteger
NameTypeReqDescription
resultstringyes

No examples provided.

release ~21

Kill a persistent connection by name.

NameTypeReqDescription
namestringyes
NameTypeReqDescription
resultstringyes

No examples provided.

reload ~97

Reload a persistent connection after editing its code — the MCP REPL in one call. reload('dev') # release the stale process, start fresh code, remount live Replaces the manual release() + connect() + shapeshift() cycle and removes the "connect() handed back the old process" footgun (it always releases first). `name` is the alias you gave connect().

NameTypeReqDescription
namestringyes
NameTypeReqDescription
resultstringyes

No examples provided.

search ~208

Discover MCP servers across registries — the entry point to mounting. Returns a ranked list of server_ids with name, description, source, and credential-readiness status. Records discovered servers in session so status() can summarize them. Reports per-registry failures inline rather than failing the whole call. Use when: you need to find a server matching a capability before mounting. Avoid when: the server_id is already known — go straight to shapeshift() or inspect(). search('web search') # find candidates search('postgres', compare=True) # side-by-side token-cost table search('vector db', registry='smithery') registry: all|official|mcpregistry|glama|npm|smithery|pypi

NameTypeReqDescription
comparebooleanReturn a side-by-side token-cost comparison table
limitinteger
querystringyesKeywords, capability description, or natural-language phrase
registrystring
NameTypeReqDescription
resultstringyes

No examples provided.

shapeshift ~231

Mount an MCP server's tools at runtime. Empty server_id unmounts. shapeshift('mcp-server-time') # mount (community sources cage by default) shapeshift('id', tools=['only_this']) # lean — mount only listed tools shapeshift('id', sandbox=False) # opt out of the default Docker cage shapeshift('id', sandbox=True) # force the cage (hard-fail if no Docker) shapeshift() # unmount + kill process sandbox: None (default) cages low-trust npm/PyPI/github sources in Docker when it's available (best-effort — runs uncaged with a nudge if not); True forces the cage; False opts out. source: auto|local|smithery|official. confirm=True for community sources.

NameTypeReqDescription
confirmboolean
keepboolean
sandbox
server_args
server_idstring
sourcestring
tools
NameTypeReqDescription
resultstringyes

No examples provided.

status ~23

Show Kitsune runtime state: providers, current form, connections, token stats.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes

No examples provided.

Common questions

What is the io.github.kaiser-data/kitsune-mcp server?

io.github.kaiser-data/kitsune-mcp is listed in the public MCP registry as io.github.kaiser-data/kitsune-mcp. Shape-shifting MCP hub, shapeshift() into 130,000+ servers at runtime. No restarts. 7 registries. This page covers its PyPI package (kitsune-mcp).

Is the io.github.kaiser-data/kitsune-mcp server safe to use?

io.github.kaiser-data/kitsune-mcp scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.kaiser-data/kitsune-mcp server expose?

io.github.kaiser-data/kitsune-mcp exposes 9 tools: search, status, call, auto, auth, and 4 more. Their descriptions and schemas cost roughly 1,024 tokens of context every time the server is loaded.

Is the io.github.kaiser-data/kitsune-mcp server still maintained?

io.github.kaiser-data/kitsune-mcp 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 io.github.kaiser-data/kitsune-mcp server under?

io.github.kaiser-data/kitsune-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.