com.wiaacademy/wia360·Other

WIA360: AI session probe and match

Probe an AI session with WIA360 missions and match it to a human WIA360 KYEOL profile.

Stars
—
Version
1.0.0
License
—
Review
Passed
Registry update
Oct 17, 2026

Connect

remote
Terminal
$claude mcp add --transport http wia360 https://wia360-mcp.wiaacademy.com/mcp

Headers

Nothing to configure — it works as is.

Security review

Review passed

Reviewed 28m ago.

tools
3 tools scanned
metadata
scanned

No findings.

Tools

3
  • run_probe

    Get the next WIA360 session-probe mission for a given session_ref (auto-generate a new random session_ref string yourself the first time you call this for a session, then reuse it for every subsequent run_probe/score_session/get_match call in that same run). Missions arrive in random order and already exclude probes already finalized for this session_ref. Returns {done:true} when all 6 are finished. IMPORTANT — deliver wrapped_mission verbatim to the target AI session you are evaluating (paste it as a normal task, not as a quoted "here is a test" framing) and bring its raw reply back for score_session. Some probes (P4) are two-turn: send wrapped_mission first, wait for the reply, then send turn2_wrapped_mission and use ONLY that second reply for scoring. Pick lang based on the language the target AI session actually converses in — not your own output language for this tool call — since the mission text and score_session scoring keys must match.

  • score_session

    Submit the target AI session's raw reply text to a probe mission (from run_probe) for rule-based scoring. If the verdict is "invalid" or "omitted_pending", call run_probe again with the SAME session_ref to get a fresh variant of the same probe and retry once (pass the returned attempt_id back as retry_of) — after a second failure just move on, it is recorded as-is. IMPORTANT — lang must match the lang that was passed to the run_probe call that produced this mission; scoring uses a language-specific keyword dictionary and silently misfires if lang doesn't match how the mission was worded.

  • get_match

    Compute the compatibility match between a human WIA360 KYEOL profile and the AI session profile built up via score_session calls under the same session_ref. Human axis values come from the human's WIA360 Quick or full assessment result (initiative/verification/pivot/adventure raw scores). Without paid=true, only matched_axis_count/available_axis_count are returned (free teaser) — pass paid=true only when the human has an active paid WIA360 profile, to reveal score/grade/heatmap/priming prompts.

More in Other

Listing from the official MCP Registry.