WIA360: AI session probe and match
REMOTE · WIA360-MCP.WIAACADEMY.COM
Probe an AI session with WIA360 missions and match it to a human WIA360 KYEOL profile.
Available components
Last scanned (11 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 5 Nov 2026.
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 773 tokens (~257/item across 3 items; 3 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 Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 71% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 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.
- 21 Oct 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.
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 · Probed https://wia360-mcp.wiaacademy.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=wiaacademy.com | CN=YE1,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 657a5e6cd20ae4a67af5ab6d49ed68546b8 |
| SANs: *.wiaacademy.com, wiaacademy.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of wia360-mcp.wiaacademy.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| wiaacademy.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://wia360-mcp.wiaacademy.com/mcp | Verified | 200 | |
| http (plaintext) | http://wia360-mcp.wiaacademy.com/mcp | HTTPS enforced | 301 | https://wia360-mcp.wiaacademy.com/mcp |
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 →
get_match ~246
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.
| Name | Type | Req | Description |
|---|---|---|---|
| h_adventure | number | yes | Human adventure axis raw score (1-5 average). |
| h_initiative | number | yes | Human initiative axis raw score (1-5 average, from WIA360 result). |
| h_pivot | number | yes | Human pivot axis raw score (adaptability-persistence difference, roughly -4..4). |
| h_verification | number | yes | Human verification axis raw score (1-5 average). |
| paid | boolean | – | Set true only for an active paid WIA360 profile — reveals full grade/heatmap/priming prompts instead of the free teaser. |
| session_ref | string | yes | – |
No output schema declared.
No examples provided.
run_probe ~291
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Mission delivery language — must match the language the target AI session converses in, and must be passed identically to score_session for the same probe/variant. Defaults to ko. Only ko/en mission… |
| session_ref | string | yes | Caller-generated opaque session id, stable across one probing run. |
No output schema declared.
No examples provided.
score_session ~236
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Must match the lang used in the run_probe call for this probe/variant. Defaults to ko. |
| probe | string | yes | – |
| response_text | string | yes | The target AI session's raw reply text (for P4, the TURN2 reply only). |
| retry_of | integer | – | attempt_id from a prior invalid/omitted_pending result for this same probe, if this is a retry. |
| session_ref | string | yes | – |
| variant | integer | yes | – |
No output schema declared.
No examples provided.
How do I install the WIA360: AI session probe and match MCP server?
WIA360: AI session probe and match is a hosted endpoint at https://wia360-mcp.wiaacademy.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · wia360-mcp.wiaacademy.com
claude mcp add --transport http com-wiaacademy-wia360 'https://wia360-mcp.wiaacademy.com/mcp'
What is the WIA360: AI session probe and match MCP server?
WIA360: AI session probe and match is an MCP server listed in the public MCP registry as com.wiaacademy/wia360. Probe an AI session with WIA360 missions and match it to a human WIA360 KYEOL profile. This page covers its hosted endpoint (https://wia360-mcp.wiaacademy.com/mcp).
Is the WIA360: AI session probe and match MCP server safe to use?
WIA360: AI session probe and match scores 77 out of 100 on VerifyMCP. 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 WIA360: AI session probe and match MCP server expose?
WIA360: AI session probe and match exposes 3 tools: run_probe, score_session, get_match. Their descriptions and schemas cost roughly 773 tokens of context every time the server is loaded.
Does the WIA360: AI session probe and match MCP server require authentication?
No. We connected to WIA360: AI session probe and match without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the WIA360: AI session probe and match MCP server still maintained?
WIA360: AI session probe and match 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 did VerifyMCP test on the WIA360: AI session probe and match MCP server?
VerifyMCP ran 13 checks on WIA360: AI session probe and match, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.