Wakidokoro — Chiikawa episode guide
REMOTE · WAKIDOKORO.PARTY
Unofficial Chiikawa episode guide: search episodes, characters and story arcs in 5 languages.
Available components
Last scanned (16 hours ago)
Scores higher than 43% of remote servers
Reachable. Last reached 5 Nov 2026.
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 Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1120 tokens (~140/item across 8 items; 8 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 48% of tool parameters carry a description.Partial
- Structured output schemas are declared (13% of tools); any adoption earns full credit.Pass
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; "send_confirmed_error_report" implies "send" 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 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (10)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (3)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
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 58
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 5 Nov 2026 · Probed https://wakidokoro.party/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=wakidokoro.party | CN=WE1,O=Google Trust Services,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 45c6b19433c449b81379009325f7dc3e |
| SANs: wakidokoro.party, *.wakidokoro.party | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of wakidokoro.party. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| party. | DS published | 55099 | 8 | Verified |
| wakidokoro.party. | 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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'nonce-9QhmifmLzlQuhNPG2V3rbA==' https://platform.twitter.com https://www.googletagmanager.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://platform.twitter.com; font-src 'self' data: https://fonts.gstatic.com; img-src 'self' data: blob: https://pbs.twimg.com https://abs.twimg.com https://platform.twitter.com https://syndication.twitter.com https://*.twimg.com https://www.googletagmanager.com https://*.google-analytics.com https://*.analytics.google.com; frame-src https://platform.twitter.com https://syndication.twitter.com https://*.twitter.com https://*.x.com; connect-src 'self' https://platform.twitter.com https://syndication.twitter.com https://www.googletagmanager.com https://*.google-analytics.com https://*.analytics.google.com; worker-src 'self'; manifest-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'self' |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://wakidokoro.party/mcp | Verified | 200 | |
| http (plaintext) | http://wakidokoro.party/mcp | Inconclusive | 405 |
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 →
draft_error_report ~342
Step 1 of 2 for privately telling the site operator about a factual error in one episode's page (one point per report). Fill only the fields for the part you choose: title / summary / translation → the exact wrong text copied from get_episode in that language (checked against the page) and the corrected text; characters → the add/remove lists; arc → an arc id from list_arcs; number → the correct episode number; other → one neutral sentence. This only makes a draft. It returns the draft, the terms and a token; show both to the user and call send_confirmed_error_report only if they say yes.
| Name | Type | Req | Description |
|---|---|---|---|
| characters_to_add_from_this_list | array | – | – |
| characters_to_remove_from_this_list | array | – | – |
| correct_arc_id_from_list_arcs | string | – | – |
| correct_episode_number | integer | – | – |
| corrected_text_only_no_insults_no_personal_data_no_urls_no_ads | string | – | – |
| episode_id_or_number | string | yes | Post id (X status id) or manga episode number. |
| i_rewrote_it_factual_polite_without_insults_pii_urls_or_ads | boolean | yes | – |
| language_of_the_page | string | – | Language version of the page the wrong text is on. Default ja. translation needs a language other than ja. |
| other_issue_in_one_neutral_sentence_no_insults_pii_urls_or_ads | string | – | – |
| panel_number_only_if_the_user_said_it | integer | – | – |
| which_part_is_wrong | string | yes | – |
| wrong_text_copied_exactly_from_the_page | string | – | – |
No output schema declared.
No examples provided.
get_arc ~61
One story arc: its chapters and episodes in order.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Arc id from list_arcs. |
| locale | string | – | Language of titles, summaries and names. ja is the original; other languages only include translated episodes. Default ja. |
No output schema declared.
No examples provided.
get_character ~96
A character's profile in the catalog: number of posts, first and latest appearance, who they appear with most, and their most typical episodes. The name may be in any language (e.g. ハチワレ, Hachiware, 小八).
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language of titles, summaries and names. ja is the original; other languages only include translated episodes. Default ja. |
| name | string | yes | – |
No output schema declared.
No examples provided.
get_episode ~86
Get one episode by its post id or its manga episode number: title, date, summary, characters, arc and links.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Post id (the X status id). |
| locale | string | – | Language of titles, summaries and names. ja is the original; other languages only include translated episodes. Default ja. |
| number | integer | – | Manga episode number. |
No output schema declared.
No examples provided.
latest_episodes ~64
The newest episodes, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many to return (default 10, max 20). |
| locale | string | – | Language of titles, summaries and names. ja is the original; other languages only include translated episodes. Default ja. |
No output schema declared.
No examples provided.
list_arcs ~49
All multi-part story arcs with their number of episodes.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language of titles, summaries and names. ja is the original; other languages only include translated episodes. Default ja. |
No output schema declared.
No examples provided.
search_episodes ~117
Search Chiikawa episodes by words, scenes or feelings in any language (e.g. 'Hachiware cries', '草むしり検定'). Episodes whose title or summary contains the words come first, then ones close in meaning.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many to return (default 10, max 20). |
| locale | string | – | Language of titles, summaries and names. ja is the original; other languages only include translated episodes. Default ja. |
| query | string | yes | What to look for. |
No output schema declared.
No examples provided.
send_confirmed_error_report ~129
Step 2 of 2: send a draft from draft_error_report after the user has seen that exact draft and the terms, said to send it, and agreed to the terms. Never call it on your own.
| Name | Type | Req | Description |
|---|---|---|---|
| draft_token_from_draft_error_report | string | yes | – |
| user_agreed_to_terms_version_shown_with_the_draft | string | yes | – |
| user_assigns_copyright_to_wakidokoro_and_waives_moral_rights | boolean | yes | – |
| user_saw_this_exact_draft_and_said_send_it | boolean | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
| report_id | integer | yes | – |
| status | string | yes | – |
No examples provided.
How do I install the Wakidokoro — Chiikawa episode guide MCP server?
Wakidokoro — Chiikawa episode guide is a hosted endpoint at https://wakidokoro.party/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 · wakidokoro.party
claude mcp add --transport http party-wakidokoro-chiikawa 'https://wakidokoro.party/mcp'
What is the Wakidokoro — Chiikawa episode guide MCP server?
Wakidokoro — Chiikawa episode guide is an MCP server listed in the public MCP registry as party.wakidokoro/chiikawa. Unofficial Chiikawa episode guide: search episodes, characters and story arcs in 5 languages. This page covers its hosted endpoint (https://wakidokoro.party/mcp).
Is the Wakidokoro — Chiikawa episode guide MCP server safe to use?
Wakidokoro — Chiikawa episode guide scores 58 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 Wakidokoro — Chiikawa episode guide MCP server expose?
Wakidokoro — Chiikawa episode guide exposes 8 tools: search_episodes, get_episode, latest_episodes, get_character, list_arcs, and 3 more. Their descriptions and schemas cost roughly 944 tokens of context every time the server is loaded.
Does the Wakidokoro — Chiikawa episode guide MCP server require authentication?
No. We connected to Wakidokoro — Chiikawa episode guide without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Wakidokoro — Chiikawa episode guide MCP server still maintained?
Wakidokoro — Chiikawa episode guide 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 Wakidokoro — Chiikawa episode guide MCP server?
VerifyMCP ran 10 checks on Wakidokoro — Chiikawa episode guide, covering TLS certificate, HSTS header, DNSSEC, Transport and 6 more. 3 items could not be completed, a gap on our side rather than a finding about Wakidokoro — Chiikawa episode guide: Authorization, HTTPS and Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.