io.github.kaiser-data/kitsune-mcp
PYPI · KITSUNE-MCP · 2 COMPONENTS
Hot-reload for MCP servers + mount any community server mid-session, Docker optional. No restarts.
Available components
Last scanned (4 hours ago)
Scores higher than 75% of PyPI servers
Category Developer Tools
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 30 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to kaiser-data/kitsune-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
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.
- 5 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 31 Oct 26 0
- Package version: 0.22.5 → 0.22.7 functional
- Package version: 0.22.5 → 0.22.6 functional
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Package version: 0.22.4 → 0.22.5 functional
- 29 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.93 functional
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
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 5 Nov 2026 · Analysed pypi/kitsune-mcp@0.22.7
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 | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | kaiser-data/kitsune-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/kaiser-data/kitsune-mcp/.github/workflows/publish.yml@refs/tags/v0.22.7 |
| Rekor log index | 3614542139 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:8dbca4b371fbd7104c7b08145c2931c58e0ed9ad453f7e6c6f0fc5865f86e71a |
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 30 packages
| Packages resolved | 30 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
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
| Name | Type | Req | Description |
|---|---|---|---|
| server_id_or_var | string | yes | – |
| value | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
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')
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | – | – | – |
| keys | – | – | – |
| server_hint | string | – | – |
| task | string | yes | – |
| tool_name | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
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
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | – | – | Tool arguments matching its inputSchema (default {}) |
| config | – | – | – |
| server_id | – | – | Defaults to the currently shapeshifted form when omitted |
| tool_name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
connect ~65
Start a persistent server. command: server_id or shell cmd (e.g. 'uvx voice-mode'). name: alias for release().
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | – |
| inherit_stderr | boolean | – | – |
| name | string | – | – |
| timeout | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
release ~21
Kill a persistent connection by name.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
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().
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
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
| Name | Type | Req | Description |
|---|---|---|---|
| compare | boolean | – | Return a side-by-side token-cost comparison table |
| limit | integer | – | – |
| query | string | yes | Keywords, capability description, or natural-language phrase |
| registry | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | boolean | – | – |
| keep | boolean | – | – |
| sandbox | – | – | – |
| server_args | – | – | – |
| server_id | string | – | – |
| source | string | – | – |
| tools | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
status ~23
Show Kitsune runtime state: providers, current form, connections, token stats.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
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
claude mcp add kaiser-data-kitsune-mcp -- uvx kitsune-mcp
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. Hot-reload for MCP servers + mount any community server mid-session, Docker optional. No restarts. 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 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 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 5 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 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.