_ registry / mcp streamable-http · checked 29m ago

tw-screen-release

https://tw-screen-release.panda198271.workers.dev

Registry code: 1dd0fb831027399f

api record

電影、影集、動畫上映日資料庫（繁體中文）：首次公開日、預定與確定上映日、改期紀錄、官方預告片與新聞，每筆附來源；另可用 Wikidata 查任何作品。

endpoint
https://tw-screen-release.panda198271.workers.dev/mcp
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 tw-screen-release live?
Yes — it answered the hub's last check (checked 29m ago). It answered 100% of checks over the last 30 days.
Is tw-screen-release free to use?
Yes — the hub reached it with no key and no payment.
What tools does tw-screen-release have?
6 tools: get_title, lookup_any_title, release_calendar, schedule_changes, release_countdown, list_titles.
Is tw-screen-release 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 99.3%· all time 99.3%

latency
93ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 289 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
games & entertainment entertainment & media
used for
  • look up movie or series release date
  • list upcoming film and anime releases
  • get monthly release calendar
  • track release schedule changes
takes → gives
text → data
tools
6 reads
_ 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
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
1 open 5 never probed 1 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.

  • list_titles reads open 7h ago

    列出 2026–2027 重點電影、影集、動畫、劇場版，含首次公開日、上映日、平台、狀態；可依類型、平台、狀態、日期篩選。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "to": {
      "type": "string"
    },
    "from": {
      "type": "string"
    },
    "type": {
      "enum": [
        "film",
        "series",
        "anime-series",
        "anime-film"
      ],
      "type": "string"
    },
    "status": {
      "enum": [
        "confirmed",
        "window",
        "tba",
        "released"
      ],
      "type": "string"
    },
    "platform": {
      "type": "string"
    },
    "upcoming": {
      "type": "boolean"
    }
  }
}
    arguments 35 lines
  • get_title reads unknown 7h ago

    查單一作品：製作、發行平台、導演、首次公開日、上映時程與改期紀錄、初公開與最新官方預告、官方新聞；中文、英文、日文片名皆可（如 沙丘3、Avengers Doomsday、薬屋のひとりごと）。

    mcp-tool

    {
  "type": "object",
  "required": [
    "q"
  ],
  "properties": {
    "q": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • lookup_any_title reads unknown 7h ago

    用 Wikidata 公開資料查任何電影、影集、動畫的上映日、導演、製作公司、播出平台、官方網站與 YouTube 影片。

    mcp-tool

    {
  "type": "object",
  "required": [
    "q"
  ],
  "properties": {
    "q": {
      "type": "string"
    }
  }
}
    arguments 11 lines
  • release_calendar reads unknown never probed

    依月份的上映與開播行事曆，以及只公布時期、未定的作品。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "month": {
      "type": "string",
      "description": "YYYY-MM"
    }
  }
}
    arguments 9 lines
  • schedule_changes reads unknown never probed

    有時程變更的作品（延期、提前、換發行商），每次變更附來源。

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • release_countdown reads unknown never probed

    距離作品上映或開播還有幾天（預設復仇者聯盟：末日崛起）。

    mcp-tool

    {
  "type": "object",
  "properties": {
    "q": {
      "type": "string"
    }
  }
}
    arguments 8 lines
_ try it 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 1dd0fb831027399f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1dd0fb831027399f/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/1dd0fb831027399f/badge.svg)](https://brick.blue/agent/1dd0fb831027399f?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 know
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
0
ok
0
failed
0
success rate
—
median latency
—
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
—

0 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.