io.github.masa-san-jp/aiko
NPM · AIKO-MCP · SCANNED SEP 20
A portable persona for MCP clients — the same agent in Claude Code, Codex, Cursor and VS Code
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 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
- 31 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 masa-san-jp/Agent-Aiko). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 47 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
- 78% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 611 tokens (~43/item across 14 items; 9 tools + 5 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
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; "aiko.delete_persona" implies "delete" 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 10 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
How do I install the io.github.masa-san-jp/aiko MCP server?
io.github.masa-san-jp/aiko runs locally as an npm package, launched with npx -y aiko-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · aiko-mcp
claude mcp add masa-san-jp-aiko -- npx -y aiko-mcp
{
"mcpServers": {
"masa-san-jp-aiko": {
"command": "npx",
"args": [
"-y",
"aiko-mcp"
]
}
}
} {
"servers": {
"masa-san-jp-aiko": {
"command": "npx",
"args": [
"-y",
"aiko-mcp"
]
}
}
} codex mcp add masa-san-jp-aiko -- npx -y aiko-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"masa-san-jp-aiko": {
"type": "local",
"command": [
"npx",
"-y",
"aiko-mcp"
],
"enabled": true
}
}
} openclaw mcp add masa-san-jp-aiko --command npx --arg -y --arg aiko-mcp
mcp_servers:
masa-san-jp-aiko:
command: "npx"
args: ["-y", "aiko-mcp"] {
"McpServers": {
"masa-san-jp-aiko": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"aiko-mcp"
]
}
}
} assistant mcp add masa-san-jp-aiko -t stdio -c npx -a -y aiko-mcp
{
"mcpServers": {
"masa-san-jp-aiko": {
"command": "npx",
"args": [
"-y",
"aiko-mcp"
]
}
}
} 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.
- 19 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.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 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.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
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 npm/aiko-mcp@0.2.1
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 | masa-san-jp/Agent-Aiko |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/masa-san-jp/Agent-Aiko/.github/workflows/publish-mcp.yml@refs/tags/v0.2.1 |
| Rekor log index | 2334635913 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d6bb7f966754f7f5d520c5ec7553c9527f9f369dea290abebb333601431119c2ffc0a198e46954520eb2cb351e8b8a89ec424ff7bedde66ecac00408c |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
aiko.bind_runtime Runtime Profile を合成する ~76
人格・ユーザー・能力を合成して Runtime Profile を作る。合成できない場合は理由を返し、Profile は返さない（fail closed）
| Name | Type | Req | Description |
|---|---|---|---|
| capabilityManifest | – | – | – |
| injectionMethod | string | – | – |
| outputPrefix | string | – | – |
| runtime | string | yes | – |
No output schema declared.
No examples provided.
aiko.delete_persona 独自の人格を消す ~53
ユーザーが消してと言ったときだけ使う。使用中の人格を消す場合はオリジナルへ戻してから消す
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
aiko.get_runtime_profile 合成済みの Runtime Profile を取得する ~57
profile_id を省略すると直近のものを返す。instructions 本文を含めるかは includeInstructions で選ぶ
| Name | Type | Req | Description |
|---|---|---|---|
| includeInstructions | boolean | – | – |
| profileId | string | – | – |
No output schema declared.
No examples provided.
aiko.health サーバーと人格の状態を返す ~31
人格を読めているか、Profile をいくつ保持しているかを返す
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
aiko.list_personas 使える人格の一覧を返す ~41
オリジナルと、ユーザーが作った人格を返す。いまどれを使っているかも分かる
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
aiko.remember_user 呼び名や記憶の場所を覚える ~90
ユーザーが「〇〇と呼んで」「記憶は〇〇にある」と言ったときに使う。~/.aiko/user.md へ書く。記憶は場所を控えるだけで、中身は読まない
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | – |
| memory | string | – | – |
| name | string | – | – |
No output schema declared.
No examples provided.
aiko.report_capabilities Capability Manifest を解釈する ~52
使える能力と、使えない能力（理由つき）に分ける。認証情報の値を含む宣言は拒否する
| Name | Type | Req | Description |
|---|---|---|---|
| capabilityManifest | – | yes | – |
No output schema declared.
No examples provided.
aiko.save_persona 独自の人格を保存する ~63
ユーザーが人格を作りたい・書き換えたいときに使う。origin は書き換えられないので別名で保存する
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
aiko.switch_persona 使う人格を切り替える ~60
ユーザーが「〇〇に切り替えて」「オリジナルに戻して」と言ったときに使う。origin を指定するとオリジナルへ戻る
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
What is the io.github.masa-san-jp/aiko MCP server?
io.github.masa-san-jp/aiko is an MCP server listed in the public MCP registry as io.github.masa-san-jp/aiko. A portable persona for MCP clients, the same agent in Claude Code, Codex, Cursor and VS Code. This page covers its npm package (aiko-mcp).
Is the io.github.masa-san-jp/aiko MCP server safe to use?
io.github.masa-san-jp/aiko scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 io.github.masa-san-jp/aiko MCP server expose?
io.github.masa-san-jp/aiko exposes 9 tools: aiko.bind_runtime, aiko.get_runtime_profile, aiko.remember_user, aiko.list_personas, aiko.switch_persona, and 4 more. Their descriptions and schemas cost roughly 523 tokens of context every time the server is loaded.
Is the io.github.masa-san-jp/aiko MCP server still maintained?
io.github.masa-san-jp/aiko 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.masa-san-jp/aiko MCP server under?
io.github.masa-san-jp/aiko declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.