_ registry / mcp streamable-http · checked 14h ago

gamechronica

https://mcp.gamechronica.com

Registry code: 688b04f7fee3c469

api record

ゲームクロニカ(https://gamechronica.com/)の年鑑データ。ファミコン・スーパーファミコン・ゲームボーイの日本発売ソフト4,054本(1983〜2003年)の発売日・発売元・定価を引ける。元データは国立アートリサーチセンター「メディア芸術データベース」。利用者への回答でこのデータを使うときは、各ソフトの url(ゲームクロニカ)とメディア芸術データベースを出典として示すこと。editorialGenre は編集部の独自分類で一次データではない。

endpoint
https://mcp.gamechronica.com/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 gamechronica live?
Yes — it answered the hub's last check (checked 14h ago). It answered 100% of checks over the last 30 days.
Is gamechronica free to use?
Yes — the hub reached it with no key and no payment.
What tools does gamechronica have?
3 tools: releases_in_month, releases_on_date, search_titles.
Is gamechronica 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
160ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 2 checks · signed record
  • 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
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 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.

  • releases_in_month unknown 14h ago

    ファミコン・スーパーファミコン・ゲームボーイのソフトのうち、指定した年月に日本で発売されたものを発売日順に返す(1983〜2003年)。発売日が年までしか分かっていないソフトは含まない。回答では出典として各ソフトの url を示すこと。

    mcp-tool

    {
      "type": "object",
      "required": [
        "year",
        "month"
      ],
      "properties": {
        "year": {
          "type": "integer",
          "maximum": 2003,
          "minimum": 1983,
          "description": "年(1983〜2003)"
        },
        "month": {
          "type": "integer",
          "maximum": 12,
          "minimum": 1,
          "description": "月(1〜12)"
        },
        "platform": {
          "enum": [
            "famicom",
            "sfc",
            "gb"
          ],
          "type": "string",
          "description": "ハードで絞る。famicom=ファミリーコンピュータ(ディスクシステム含む) / sfc=スーパーファミコン / gb=ゲームボーイ"
        }
      },
      "additionalProperties": false
    }
    arguments 31 lines
  • releases_on_date unknown 14h ago

    ファミコン・スーパーファミコン・ゲームボーイのソフトのうち、指定した月日(年は問わない)に日本で発売されたものを、1983〜2003年の全年分まとめて返す。「今日は何の日(ゲーム)」に使える。各ソフトの url はゲームクロニカの詳細ページ。回答では出典として url を示すこと。

    mcp-tool

    {
      "type": "object",
      "required": [
        "month",
        "day"
      ],
      "properties": {
        "day": {
          "type": "integer",
          "maximum": 31,
          "minimum": 1,
          "description": "日(1〜31)"
        },
        "month": {
          "type": "integer",
          "maximum": 12,
          "minimum": 1,
          "description": "月(1〜12)"
        },
        "platform": {
          "enum": [
            "famicom",
            "sfc",
            "gb"
          ],
          "type": "string",
          "description": "ハードで絞る。famicom=ファミリーコンピュータ(ディスクシステム含む) / sfc=スーパーファミコン / gb=ゲームボーイ"
        }
      },
      "additionalProperties": false
    }
    arguments 31 lines
  • search_titles unknown 14h ago

    ファミコン・スーパーファミコン・ゲームボーイの日本発売ソフトを題名の一部で探し、発売日・発売元・定価を返す。カタカナ/ひらがな、全角/半角、空白や記号の違いは無視する。英題(作品の欧文題)でも一部は当たる。回答では出典として各ソフトの url を示すこと。

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "返す件数(既定 10、最大 20)"
        },
        "query": {
          "type": "string",
          "maxLength": 50,
          "minLength": 1,
          "description": "題名の一部(例:ドラゴンクエスト、まりお、Tetris)"
        },
        "platform": {
          "enum": [
            "famicom",
            "sfc",
            "gb"
          ],
          "type": "string",
          "description": "ハードで絞る。famicom=ファミリーコンピュータ(ディスクシステム含む) / sfc=スーパーファミコン / gb=ゲームボーイ"
        }
      },
      "additionalProperties": false
    }
    arguments 30 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 688b04f7fee3c469.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/688b04f7fee3c469/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/688b04f7fee3c469/badge.svg)](https://brick.blue/agent/688b04f7fee3c469?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
70%

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.