tw-travel-2027
https://tw-travel-2027.panda198271.workers.dev
Registry code: 6d26592777ddb6b7
台灣 2027 連假請假攻略、各國假日人潮、機票購票時機、劇場密室訂票須知。
- endpoint
- https://tw-travel-2027.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 tw-travel-2027 live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is tw-travel-2027 free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does tw-travel-2027 have?
- 5 tools: flight_booking_timing, plan_leave_2027, ticket_booking_guide, check_destination_crowd, get_2027_long_weekends.
- Is tw-travel-2027 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.3%· all time 99.3%
last good check
of 5 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- unknown → degraded· timeout after 20000ms
- used for
- plan leave days for 2027 long weekends in taiwan
- check destination crowd levels
- get flight booking timing advice
- takes → gives
- data → data
- tools
- 5 reads
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.
check_destination_crowd reads open 5h ago
查某個目的地在一段日期的人潮等級:是否撞到當地國定假日或旺季。country 國碼:JP,KR,HK,CN,VN,TH,SG,PH,ID,US,GB,FR,AU
{ "type": "object", "required": [ "country", "start", "end" ], "properties": { "end": { "type": "string", "description": "YYYY-MM-DD" }, "start": { "type": "string", "description": "YYYY-MM-DD" }, "country": { "type": "string" } } }arguments 21 linesget_2027_long_weekends reads open 5h ago
台灣 2027 年(民國 116 年)9 個 3 天以上連假,以及每個連假請 1~5 天假的最佳組合(例:春節請 5 休 16)。
{ "type": "object", "properties": {} }arguments 4 linesflight_booking_timing reads unknown never probed
評估從台灣出發的機票現在該買還是該等:依出發日、目的地、台灣連假與旺季,給建議購票期。不是即時票價。
{ "type": "object", "required": [ "depart" ], "properties": { "dest": { "type": "string", "description": "國碼" }, "depart": { "type": "string", "description": "YYYY-MM-DD" } } }arguments 16 linesplan_leave_2027 reads unknown never probed
輸入可請的假日天數,算出 2027 年最長的連休組合與要請哪幾天。
{ "type": "object", "required": [ "leave" ], "properties": { "leave": { "type": "number", "description": "可請天數 1~10" } } }arguments 12 linesticket_booking_guide reads unknown never probed
沉浸式劇場、密室逃脫訂票須知:台灣售票平台、退票規定、黃牛罰則、預約前確認清單。
{ "type": "object", "properties": {} }arguments 4 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 id6d26592777ddb6b7.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/6d26592777ddb6b7/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/6d26592777ddb6b7?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.