_ registry / mcp + a2a streamable-http · checked 1h ago

tooneru

https://tooneru.com

Registry code: 9e5ef7302ad203c7

api record

トゥーンエル(https://tooneru.com/)の縦読み漫画を読むだけのサーバーです。search_works で作品を探し、list_episodes で話を選び、get_episode で本文、get_context で続きを相談する時の前提を読めます。作品が扱う仕事・制度・お金・手続きの言葉の解説(出典つき)は get_glossary で読めます。各話の結果には作品名と話の URL があり、出典に使えます。作中の世界の決まりは物語の設定です。利用者が読んだ話より後の展開(正体・結末・関係の変化・後の話で初めて出る事実)は、その利用者にとってネタバレになります。up_to_episode(利用者が読んだ話)を渡すと、それより後の話のあらすじと用語を省けます。

endpoint
https://tooneru.com/mcp
door code
2af74b6747e8e2fd
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is tooneru live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is tooneru free to use?
Yes — the hub reached it with no key and no payment.
What tools does tooneru have?
6 tools: get_episode, get_glossary, get_context, list_episodes, search_works, list_new_episodes.
Is tooneru safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
114ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
2 open 4 never probed 2 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_works open 1h ago

    トゥーンエルの縦読み漫画の作品と話を、言葉とジャンルで探す。題名・あらすじ・登場人物のほか、作品が扱う仕事・暮らし・制度・お金・手続きの言葉(例:無申告加算税、施工管理、置き配、生活保護)からも探せる。用語の解説(get_glossary)や、その言葉が出てくる話を探す入口にもなる。query が空なら全作品の一覧(id・名前・ジャンル・URL・話の数だけ)を返す。当たった話のうち第2話以降には spoiler の印(up_to_episode を渡すと、それより後の話は返さない)。

    mcp-tool

    {
      "type": "object",
      "properties": {
        "genre": {
          "type": "string",
          "description": "ジャンルの id か名前(例:isekai/異世界転生、mystery/ミステリー)"
        },
        "query": {
          "type": "string",
          "description": "探す言葉(例:加算税、施工管理、置き配、配車)。空白で区切ると、全部を含む物を返す"
        },
        "up_to_episode": {
          "type": "integer",
          "minimum": 1,
          "description": "利用者が読んだ話の番号(ネタバレを避ける)。これより後の話のあらすじ・用語を省く。分からなければ省く(全部を返し、第2話以降に spoiler の印)"
        }
      }
    }
    arguments 18 lines
  • list_new_episodes open 1h ago

    公開日の新しい順に、話の一覧を返す。

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "件数(既定 10)"
        }
      }
    }
    arguments 11 lines
  • get_episode unknown never probed

    話の本文を Markdown で返す(話者付きの台詞・ナレーション・作中の画面・絵の説明・あらすじ・登場人物・この話で分かること)。中身はその話まで。up_to_episode(利用者が読んだ話)が number より前なら、ネタバレの断りを頭に付ける。

    mcp-tool

    {
      "type": "object",
      "required": [
        "series_id",
        "number"
      ],
      "properties": {
        "number": {
          "type": "integer",
          "minimum": 1,
          "description": "話の番号(1から)"
        },
        "series_id": {
          "type": "string",
          "description": "作品の id"
        },
        "up_to_episode": {
          "type": "integer",
          "minimum": 1,
          "description": "利用者が読んだ話の番号(ネタバレを避ける)。これより後の話のあらすじ・用語を省く。分からなければ省く(全部を返し、第2話以降に spoiler の印)"
        }
      }
    }
    arguments 23 lines
  • get_glossary unknown never probed

    作品の用語集を返す。仕事・制度・お金・手続きの言葉(例:無申告加算税、施工管理技士、置き配の盗難の補償)の短い解説と、作中の世界の決まりか現実の事実かの区別、出典(法令・省庁の資料などの URL。ある物だけ)、出てくる話の番号。漫画の場面でどう出てくるかは get_episode で読める。どの作品の用語かは search_works で探せる。up_to_episode(利用者が読んだ話)を渡すと、それより後の話で初めて出る用語を省く。渡さない時は全部を返し、第2話以降の用語に spoiler の印。

    mcp-tool

    {
      "type": "object",
      "required": [
        "series_id"
      ],
      "properties": {
        "series_id": {
          "type": "string",
          "description": "作品の id"
        },
        "up_to_episode": {
          "type": "integer",
          "minimum": 1,
          "description": "利用者が読んだ話の番号(ネタバレを避ける)。これより後の話のあらすじ・用語を省く。分からなければ省く(全部を返し、第2話以降に spoiler の印)"
        }
      }
    }
    arguments 17 lines
  • get_context unknown 1h ago

    話のコンテキストセット(作品の設定・登場人物・あらすじ・この話で分かること〈仕事・制度の問いの短い答えと条件〉・用語・出典・URL の短いまとめ)を返す。話の内容を踏まえて答える時や、続きを相談する時の前提に使う。中身は第1話からその話まで(後の話は入らない)。up_to_episode が number より前なら、ネタバレの断りを頭に付ける。

    mcp-tool

    {
      "type": "object",
      "required": [
        "series_id",
        "number"
      ],
      "properties": {
        "number": {
          "type": "integer",
          "minimum": 1,
          "description": "話の番号(1から)"
        },
        "series_id": {
          "type": "string",
          "description": "作品の id"
        },
        "up_to_episode": {
          "type": "integer",
          "minimum": 1,
          "description": "利用者が読んだ話の番号(ネタバレを避ける)。これより後の話のあらすじ・用語を省く。分からなければ省く(全部を返し、第2話以降に spoiler の印)"
        }
      }
    }
    arguments 23 lines
  • list_episodes unknown never probed

    作品の公開中の話の一覧(番号・題名・公開日・要約・URL)と作品の説明・用語集を返す。up_to_episode(利用者が読んだ話)を渡すと、それより後の話の要約と用語を省く。渡さない時は全部を返し、第2話以降の項目に spoiler の印。

    mcp-tool

    {
      "type": "object",
      "required": [
        "series_id"
      ],
      "properties": {
        "series_id": {
          "type": "string",
          "description": "作品の id(search_works の結果の id。例:kengai)"
        },
        "up_to_episode": {
          "type": "integer",
          "minimum": 1,
          "description": "利用者が読んだ話の番号(ネタバレを避ける)。これより後の話のあらすじ・用語を省く。分からなければ省く(全部を返し、第2話以降に spoiler の印)"
        }
      }
    }
    arguments 17 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 9e5ef7302ad203c7.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/9e5ef7302ad203c7/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/9e5ef7302ad203c7/badge.svg)](https://brick.blue/agent/9e5ef7302ad203c7?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
1
failed
0
success rate
100%
median latency
298ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.