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.masa-san-jp/aiko

NPM · AIKO-MCP

A portable persona for MCP clients — the same agent in Claude Code, Codex, Cursor and VS Code

Available components

0 this week 90 Trust /100

Last scanned (9 hours ago)

Scores higher than 93% of npm servers

Category Memory and Knowledge

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 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
  • 30 of 92 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 4 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
  • 78% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 832 tokens (~52/item across 16 items; 11 tools + 5 resources), lean.Pass
  • 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 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 12 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
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.

  • 5 Nov 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → pass ▲ functional
  • 4 Nov 26 0
    • Security disclosure: pass → unverified ▼ functional
  • 3 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 1 Nov 26 +26
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.85 ▲ functional
  • 31 Oct 26 −26
    • Known CVEs: pass → unverified ▼ security
    • Malware scan: pass → unverified ▼ security
    • Dependency health: 0.85 → unverified ▼ functional
    • Package version: 0.3.2 → 0.3.6 functional
    • Package version: 0.3.2 → 0.3.5 functional
  • 28 Oct 26 +1
    • Stability: 0.97 → pass security
  • 27 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 24 Oct 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 5 Nov 2026 · Analysed npm/aiko-mcp@0.3.6

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.3.6
Rekor log index 3614222202
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:bf7a17d88945e0c7d746b59ddd24b509d4338e84b3c99f867ca94516d20109ba8a241157563e40e8371ac96900ee682a0fc400fb858a2ba9df9164053

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~744 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
aiko.bind_runtime ~76

人格・ユーザー・能力を合成して Runtime Profile を作る。合成できない場合は理由を返し、Profile は返さない(fail closed)

NameTypeReqDescription
capabilityManifest–––
injectionMethodstring––
outputPrefixstring––
runtimestringyes–

No output schema declared.

No examples provided.

aiko.delete_persona ~53

ユーザーが消してと言ったときだけ使う。使用中の人格を消す場合はオリジナルへ戻してから消す

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

aiko.get_runtime_profile ~57

profile_id を省略すると直近のものを返す。instructions 本文を含めるかは includeInstructions で選ぶ

NameTypeReqDescription
includeInstructionsboolean––
profileIdstring––

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.list_speech_styles ~61

original(人格本来の話し方)/ friend(くだけた友だち口調)/ servant(仕える丁寧な口調)と、いまどれを使っているかを返す

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

aiko.remember_user ~119

ユーザーが「〇〇と呼んで」「記憶は〇〇にある」と言ったときに使う。すぐには反映しない。~/.aiko/user-proposal.md に提案として残し、利用者が aiko accept したときだけ user.md に入る。記憶は場所を控えるだけで、中身は読まない

NameTypeReqDescription
addressstring––
memorystring––
namestring––

No output schema declared.

No examples provided.

aiko.report_capabilities ~52

使える能力と、使えない能力(理由つき)に分ける。認証情報の値を含む宣言は拒否する

NameTypeReqDescription
capabilityManifest–yes–

No output schema declared.

No examples provided.

aiko.save_persona ~84

ユーザーが人格を作りたい・書き換えたいときに使う。すぐには有効にならない。提案として残り、利用者が aiko accept したときに保存される。origin は提案できない

NameTypeReqDescription
contentstringyes–
namestringyes–

No output schema declared.

No examples provided.

aiko.switch_persona ~80

ユーザーが「〇〇に切り替えて」「オリジナルに戻して」と言ったときに使う。すぐには切り替わらない。提案として残り、利用者が aiko accept したときに反映される

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

aiko.switch_speech_style ~90

ユーザーが「friend モードにして」「servant で話して」「オリジナルの話し方に戻して」と言ったときに使う。提案として残り、利用者が aiko accept した後、次に人格を読み込んだときに反映される

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add masa-san-jp-aiko -- npx -y aiko-mcp
Common questions

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 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 11 tools: aiko.bind_runtime, aiko.get_runtime_profile, aiko.remember_user, aiko.list_personas, aiko.switch_persona, and 6 more. Their descriptions and schemas cost roughly 744 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 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.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.