MCP server for Atlassian Confluence Data Center - access and manage content
Manga is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
This server allows you to read the full text of works, stories, and glossary (with sources) from "ToonL," a vertical-scrolling manga media that depicts the realities of work and daily life through comics. All chapters are free to read, and no login is required. Operated by H Corporation.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http manga-mcp https://tooneru.com/mcp
# 2 — ask your agent for something these tools do
# search_works, list_episodes, get_episode and 3 more
Manga costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http manga-mcp https://tooneru.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
トゥーンエルの縦読み漫画の作品と話を、言葉とジャンルで探す。題名・あらすじ・登場人物のほか、作品が扱う仕事・暮らし・制度・お金・手続きの言葉(例:無申告加算税、施工管理、置き配、生活保護)からも探せる。用語の解説(get_glossary)や、その言葉が出てくる話を探す入口にもなる。query が空なら全作品の一覧(id・名前・ジャンル・URL・話の数だけ)を返す。当たった話のうち第2話以降には spoiler の印(up_to_episode を渡すと、それより後の話は返さない)。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | 探す言葉(例:加算税、施工管理、置き配、配車)。空白で区切ると、全部を含む物を返す |
| genre | string | no | ジャンルの id か名前(例:isekai/異世界転生、mystery/ミステリー) |
| up_to_episode | integer | no | 利用者が読んだ話の番号(ネタバレを避ける)。これより後の話のあらすじ・用語を省く。分からなければ省く(全部を返し、第2話以降に spoiler の印) |
作品の公開中の話の一覧(番号・題名・公開日・要約・URL)と作品の説明・用語集を返す。up_to_episode(利用者が読んだ話)を渡すと、それより後の話の要約と用語を省く。渡さない時は全部を返し、第2話以降の項目に spoiler の印。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| series_id | string | yes | 作品の id(search_works の結果の id。例:kengai) |
| up_to_episode | integer | no | 利用者が読んだ話の番号(ネタバレを避ける)。これより後の話のあらすじ・用語を省く。分からなければ省く(全部を返し、第2話以降に spoiler の印) |
話の本文を Markdown で返す(話者付きの台詞・ナレーション・作中の画面・絵の説明・あらすじ・登場人物・この話で分かること)。中身はその話まで。up_to_episode(利用者が読んだ話)が number より前なら、ネタバレの断りを頭に付ける。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| series_id | string | yes | 作品の id |
| number | integer | yes | 話の番号(1から) |
| up_to_episode | integer | no | 利用者が読んだ話の番号(ネタバレを避ける)。これより後の話のあらすじ・用語を省く。分からなければ省く(全部を返し、第2話以降に spoiler の印) |
話のコンテキストセット(作品の設定・登場人物・あらすじ・この話で分かること〈仕事・制度の問いの短い答えと条件〉・用語・出典・URL の短いまとめ)を返す。話の内容を踏まえて答える時や、続きを相談する時の前提に使う。中身は第1話からその話まで(後の話は入らない)。up_to_episode が number より前なら、ネタバレの断りを頭に付ける。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| series_id | string | yes | 作品の id |
| number | integer | yes | 話の番号(1から) |
| up_to_episode | integer | no | 利用者が読んだ話の番号(ネタバレを避ける)。これより後の話のあらすじ・用語を省く。分からなければ省く(全部を返し、第2話以降に spoiler の印) |
公開日の新しい順に、話の一覧を返す。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | 件数(既定 10) |
作品の用語集を返す。仕事・制度・お金・手続きの言葉(例:無申告加算税、施工管理技士、置き配の盗難の補償)の短い解説と、作中の世界の決まりか現実の事実かの区別、出典(法令・省庁の資料などの URL。ある物だけ)、出てくる話の番号。漫画の場面でどう出てくるかは get_episode で読める。どの作品の用語かは search_works で探せる。up_to_episode(利用者が読んだ話)を渡すと、それより後の話で初めて出る用語を省く。渡さない時は全部を返し、第2話以降の用語に spoiler の印。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| series_id | string | yes | 作品の id |
| up_to_episode | integer | no | 利用者が読んだ話の番号(ネタバレを避ける)。これより後の話のあらすじ・用語を省く。分からなければ省く(全部を返し、第2話以降に spoiler の印) |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Manga or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_works | no tags | |
| list_episodes | no tags | |
| get_episode | no tags | |
| get_context | no tags | |
| list_new_episodes | no tags | |
| get_glossary | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Manga can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.