warmnight-fishing
Registry code: 126b96a5d78efdfd
Free blind-play night-fishing game over MCP. Deterministic engine, zero LLM calls, save codes.
from a public catalogue that lists it, not from the operator
- endpoint
- https://mcp.aevia.cloud/mcp/v1
- protocol
- http-sse ·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 warmnight-fishing live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
- Is warmnight-fishing free to use?
- Not measured yet.
- What tools does warmnight-fishing have?
- 5 tools: fishing_save_info, fishing_play, fishing_manual, fishing_new_game, fishing_share_card.
- Is warmnight-fishing 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.
90 days 99%· all time 99%
last good check
of 5 tools
- down → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- topic
- games & entertainment games
- used for
- play a text night-fishing game
- start a new fishing game
- generate a shareable catch card
- takes → gives
- text → text, images
- tools
- 3 reads2 changes data
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.
through this hub
successful
what callers paid
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.
fishing_save_info reads unknown never probed
存档元信息(路径 / schema 版本 / 身份模式 / 进度摘要,不含游戏机密)。 / Save metadata (path, schema version, identity mode, progress); no game secrets.
{ "type": "object", "properties": { "player_code": { "type": "string", "description": "你的存档码(形如 WNF-XXXX-XXXX-XXXX),用来查这个存档的信息。不填就先 fishing_play 玩一竿拿到码,再来查。 / Your save code (e.g. WNF-XXXX-XXXX-XXXX) to inspect this save; play once first if you don't have one." } }, "additionalProperties": false }arguments 10 linesfishing_play changes data unknown never probed
执行钓鱼指令,一切游戏操作走这里(如 cast 5、status、buy basic_worm 3;支持用 ; 叠加最多 8 条)。 / Run a fishing command; the main gameplay channel.
{ "type": "object", "required": [ "command" ], "properties": { "command": { "type": "string", "description": "引擎指令,如 cast 5 / status / buy basic_worm 3;支持用 ; 叠加最多 8 条。 / A fishing command, e.g. 'cast 5'; up to 8 chained with ';'." }, "player_code": { "type": "string", "description": "可选:你的存档码(形如 WNF-XXXX-XXXX-XXXX)。首次玩不填,服务器会发一个并在结果里告诉你,记下它下次续玩报回来即可;不填则每次都是新的临时局。 / Optional save code (e.g. WNF-XXXX-XXXX-XXXX). Omit on first play; the server issues one and returns it—keep it and pass it back next time to resume." } }, "additionalProperties": false }arguments 17 linesfishing_manual reads unknown never probed
玩法说明与全部指令列表(中文)。 / Game manual and full command list (Chinese).
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesfishing_new_game changes data unknown never probed
重开一局(会覆盖当前进度,必须传 confirm:true 确认)。 / Start over (overwrites progress; requires confirm:true).
{ "type": "object", "required": [ "confirm" ], "properties": { "seed": { "type": "integer", "description": "可选:32 位整数种子(便于复现)。不填则随机取种。 / Optional 32-bit integer seed for reproducibility; random if omitted." }, "confirm": { "type": "boolean", "description": "必须显式为 true 才会重开(防误重开覆盖进度)。 / Must be explicitly true to start over (guards against accidental reset)." }, "player_code": { "type": "string", "description": "可选:要在哪个存档码上重开(形如 WNF-XXXX-XXXX-XXXX)。不填则发一个新码开新局。 / Optional save code to start over on; omit to get a fresh code and a new game." } }, "additionalProperties": false }arguments 21 linesfishing_share_card reads unknown never probed
生成可分享的图鉴 / 稀有时刻分享卡(kind: encyclopedia | moment);也可填 fish:<中文鱼名> 给某条已钓到、收录进图鉴的鱼单独出一张卡。 / Generate a shareable card (encyclopedia | moment); optionally name a caught fish to card it.
{ "type": "object", "required": [ "kind" ], "properties": { "fish": { "type": "string", "description": "可选:给某条你已经钓到、收录进图鉴的鱼单独出一张卡,填它的中文名(如 鲫鱼);没钓到过或名字对不上就不出卡。 / Optional: name a fish you've already caught (Chinese name, e.g. 鲫鱼) to card that one fish; no card if it's uncaught or the name doesn't match." }, "kind": { "enum": [ "encyclopedia", "moment" ], "type": "string", "description": "卡片类型:encyclopedia(图鉴进度)或 moment(近期稀有时刻)。 / Card kind: 'encyclopedia' (dex progress) or 'moment' (recent rare moment)." }, "player_code": { "type": "string", "description": "你的存档码(形如 WNF-XXXX-XXXX-XXXX),用来给这个存档出分享卡。不填就先 fishing_play 玩一竿拿到码,再来出卡。 / Your save code (e.g. WNF-XXXX-XXXX-XXXX) to card this save; play once first if you don't have one." } }, "additionalProperties": false }arguments 25 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id126b96a5d78efdfd.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/126b96a5d78efdfd/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/126b96a5d78efdfd?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.