kiriya
NPM · KIRIYA · SCANNED SEP 29
Developer tools for files, git, ports, processes and more, the same on Windows, Linux and macOS
Available components
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
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to SatPaingOo/kiriya). 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 Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 3127 tokens (~66/item across 47 items; 47 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 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
- 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 47 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 48 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the kiriya MCP server?
kiriya runs locally as an npm package, launched with npx -y kiriya. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · kiriya
claude mcp add satpaingoo-kiriya -- npx -y kiriya
{
"mcpServers": {
"satpaingoo-kiriya": {
"command": "npx",
"args": [
"-y",
"kiriya"
]
}
}
} {
"servers": {
"satpaingoo-kiriya": {
"command": "npx",
"args": [
"-y",
"kiriya"
]
}
}
} codex mcp add satpaingoo-kiriya -- npx -y kiriya
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"satpaingoo-kiriya": {
"type": "local",
"command": [
"npx",
"-y",
"kiriya"
],
"enabled": true
}
}
} openclaw mcp add satpaingoo-kiriya --command npx --arg -y --arg kiriya
mcp_servers:
satpaingoo-kiriya:
command: "npx"
args: ["-y", "kiriya"] {
"McpServers": {
"satpaingoo-kiriya": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"kiriya"
]
}
}
} assistant mcp add satpaingoo-kiriya -t stdio -c npx -a -y kiriya
{
"mcpServers": {
"satpaingoo-kiriya": {
"command": "npx",
"args": [
"-y",
"kiriya"
]
}
}
} 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.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +11
- Tool safety: pass → unverified ▼ security
- Known CVEs: unverified → pass ▲ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Dependency health: unverified → pass ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.1 → 0.1.2 functional
- 23 Sept 26 72
First indexed and scored.
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 29 Sept 2026 · Analysed npm/kiriya@0.1.2
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 | SatPaingOo/kiriya |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/SatPaingOo/kiriya/.github/workflows/release.yml@refs/tags/v0.1.2 |
| Rekor log index | 2941614713 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d6170e6f10df61a79c0b9e428720af130a74368450e5f6598ad1dd6c566be7f4ec741264130868e648af388f0279cf76213fc336a24f8e7cf4afe5a5a |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
proc.find ~35
Find processes whose name or command line contains some text
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The text to look for, in any case |
| Name | Type | Req | Description |
|---|---|---|---|
| applyFlag | string | – | – |
| command | string | – | – |
| data | – | – | – |
| error | object | – | – |
| failures | array | – | – |
| kind | string | – | – |
| ok | boolean | yes | – |
| output | string | – | What a program the command ran printed |
| truncated | array | – | Where the result was cut to fit, and how much |
| warnings | array | – | – |
No examples provided.
proc.list ~38
List processes with their memory, sorted by name
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Only processes whose name contains this text, in any case <text> |
| Name | Type | Req | Description |
|---|---|---|---|
| applyFlag | string | – | – |
| command | string | – | – |
| data | – | – | – |
| error | object | – | – |
| failures | array | – | – |
| kind | string | – | – |
| ok | boolean | yes | – |
| output | string | – | What a program the command ran printed |
| truncated | array | – | Where the result was cut to fit, and how much |
| warnings | array | – | – |
No examples provided.
proc.tree ~44
Show processes as a tree of parents and children, or the tree under one process
| Name | Type | Req | Description |
|---|---|---|---|
| pid | string | – | The process whose tree to show; every process when left out |
| Name | Type | Req | Description |
|---|---|---|---|
| applyFlag | string | – | – |
| command | string | – | – |
| data | – | – | – |
| error | object | – | – |
| failures | array | – | – |
| kind | string | – | – |
| ok | boolean | yes | – |
| output | string | – | What a program the command ran printed |
| truncated | array | – | Where the result was cut to fit, and how much |
| warnings | array | – | – |
No examples provided.
sys.info ~23
Show the operating system, processor, memory, uptime, locale and runtime
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| applyFlag | string | – | – |
| command | string | – | – |
| data | – | – | – |
| error | object | – | – |
| failures | array | – | – |
| kind | string | – | – |
| ok | boolean | yes | – |
| output | string | – | What a program the command ran printed |
| truncated | array | – | Where the result was cut to fit, and how much |
| warnings | array | – | – |
No examples provided.
sys.report ~26
Print machine facts and tool versions as Markdown for a bug report, without the host name
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| applyFlag | string | – | – |
| command | string | – | – |
| data | – | – | – |
| error | object | – | – |
| failures | array | – | – |
| kind | string | – | – |
| ok | boolean | yes | – |
| output | string | – | What a program the command ran printed |
| truncated | array | – | Where the result was cut to fit, and how much |
| warnings | array | – | – |
No examples provided.
sys.tools ~28
Find node, python, dotnet, java, go, git and docker, and their versions
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| applyFlag | string | – | – |
| command | string | – | – |
| data | – | – | – |
| error | object | – | – |
| failures | array | – | – |
| kind | string | – | – |
| ok | boolean | yes | – |
| output | string | – | What a program the command ran printed |
| truncated | array | – | Where the result was cut to fit, and how much |
| warnings | array | – | – |
No examples provided.
wait.file ~81
Wait until a file or folder exists, or until it is gone with --gone
| Name | Type | Req | Description |
|---|---|---|---|
| gone | boolean | – | Wait until it no longer exists instead |
| path | string | yes | The file or folder to wait for |
| timeout | string | – | Seconds to wait before giving up, from 1 to 3600; 60 by default <seconds> |
| Name | Type | Req | Description |
|---|---|---|---|
| applyFlag | string | – | – |
| command | string | – | – |
| data | – | – | – |
| error | object | – | – |
| failures | array | – | – |
| kind | string | – | – |
| ok | boolean | yes | – |
| output | string | – | What a program the command ran printed |
| truncated | array | – | Where the result was cut to fit, and how much |
| warnings | array | – | – |
No examples provided.
wait.port ~102
Wait until a TCP port accepts connections, or until nothing listens there with --gone
| Name | Type | Req | Description |
|---|---|---|---|
| gone | boolean | – | Wait until nothing listens there instead |
| target | string | yes | A port on this machine such as 5432, host:port, [IPv6]:port, or a URL whose scheme gives the port |
| timeout | string | – | Seconds to wait before giving up, from 1 to 3600; 60 by default <seconds> |
| Name | Type | Req | Description |
|---|---|---|---|
| applyFlag | string | – | – |
| command | string | – | – |
| data | – | – | – |
| error | object | – | – |
| failures | array | – | – |
| kind | string | – | – |
| ok | boolean | yes | – |
| output | string | – | What a program the command ran printed |
| truncated | array | – | Where the result was cut to fit, and how much |
| warnings | array | – | – |
No examples provided.
What is the kiriya MCP server?
kiriya is an MCP server listed in the public MCP registry as io.github.SatPaingOo/kiriya. Developer tools for files, git, ports, processes and more, the same on Windows, Linux and macOS. This page covers its npm package (kiriya).
Is the kiriya MCP server safe to use?
kiriya scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 29 September 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 kiriya MCP server expose?
kiriya exposes 47 tools: completion, completion.suggest, config.get, config.keys, config.list, and 42 more. Their descriptions and schemas cost roughly 3,084 tokens of context every time the server is loaded.
Is the kiriya MCP server still maintained?
kiriya is still listed as active in the MCP registry. We last reached this channel on 29 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 kiriya MCP server under?
kiriya declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.