funfriday
Registry code: 4d2ed9deb6764c4c
Fun Friday runs online team-building games. Use funfriday_list_games to see what is available, funfriday_create_session to open a room and get a code to share (no account needed — without one, whoever opens the join link first becomes the host), funfriday_schedule_session to plan one for a later date with an invite link for the calendar, funfriday_create_pack to add the team's own trivia questions, Imposter words or Emoji Story phrases, and the read tools to check on a session or report standings. There is no tool for playing a game — the games are played by people in the browser, and…
- endpoint
- https://www.funfriday.work/mcp
- door code
- fea233ada90c30b3
- 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 funfriday live?
- Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
- Is funfriday free to use?
- Partly — some of its tools are open, others need a key or payment.
- What tools does funfriday have?
- 10 tools: funfriday_schedule_session, funfriday_create_pack, funfriday_create_session, funfriday_list_games, funfriday_get_session, funfriday_list_sessions, funfriday_get_team, funfriday_get_leaderboard, ….
- Is funfriday 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 10 tools
- degraded → live
- unknown → live
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- topic
- games & entertainment games
- used for
- create a team-building game session
- list team games
- get team leaderboard
- check a session's status
- takes → gives
- text → data
- tools
- 5 reads1 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.
funfriday_list_games reads open 5h ago
List the team-building games available to play on Fun Friday (funfriday.work), with each game's name, description, ideal group size and whether it needs a paid plan. Use this to answer "what could we play?" or to pick a game_type before calling funfriday_create_session.
{ "type": "object", "properties": { "include_premium": { "type": "boolean", "default": true, "description": "Include games that require a paid plan. Default true — those games are listed and flagged as needing one, so an assistant can say which of them the team cannot currently play rather than pretending they do not exist." } }, "additionalProperties": false }arguments 11 linesfunfriday_get_session reads auth-required 15h ago
Check what is happening in a Fun Friday session right now: whether it is still in the lobby or being played, who has joined, and the current scores. Use this to answer "has everyone joined yet?" or "who is winning?" without opening the browser.
{ "type": "object", "required": [ "room_code" ], "properties": { "room_code": { "type": "string", "description": "The six-character room code for the session, e.g. \"K7PQ2M\". Case-insensitive. Room codes never contain the letters I or O, or the digits 0 or 1." } }, "additionalProperties": false }arguments 13 linesfunfriday_list_sessions reads auth-required 8h ago
List the Fun Friday sessions this team has played recently, most recent first, with the game played, when it happened, how many people took part and who won. Use this for "when did we last do a Fun Friday?" or to summarise the last few weeks.
{ "type": "object", "properties": { "limit": { "type": "number", "default": 10, "description": "How many sessions to return, newest first. 1–50, default 10." } }, "additionalProperties": false }arguments 11 linesfunfriday_get_team reads auth-required 8h ago
Get the user's Fun Friday team: its name, how many members it has, which plan it is on, how many of this week's games remain, and how many custom packs it has and may keep. Use this before hosting to check the team has a game left, before funfriday_create_pack to check there is room for a pack, or to answer questions about the plan and its limits.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesfunfriday_get_leaderboard reads auth-required 8h ago
Get the all-time Fun Friday leaderboard for the user's team — every player's total score, games played and rank across all sessions. Use this for "who is top of the leaderboard?" or to write up a standings summary.
{ "type": "object", "properties": { "limit": { "type": "number", "default": 20, "description": "How many ranked players to return. 1–100, default 20." } }, "additionalProperties": false }arguments 11 linesfunfriday_list_scheduled auth-required 5h ago
List the Fun Friday games the user has planned for later, soonest first, with each one's time, invite link and — once the host has opened it — the room's join link. Use this for "what have we got coming up?" or to find the invite link for the next game.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesfunfriday_get_recap auth-required 5h ago
Get a recap of a finished Fun Friday room: every game played and who won it, the overall table across those games, the top of the team's all-time leaderboard, the user's next planned game if there is one, and a link to the full results page. The text is ready to paste into Slack, Teams or email; the structured result is there for writing your own version. Leave out room_code for the team's most recent finished room. Use this for "write up today's Fun Friday for the team channel". It only reads — post it with your own messaging tools.
{ "type": "object", "properties": { "room_code": { "type": "string", "description": "The six-character room code for the session, e.g. \"K7PQ2M\". Case-insensitive. Room codes never contain the letters I or O, or the digits 0 or 1. Optional: leave it out for the most recent finished room." } }, "additionalProperties": false }arguments 10 linesfunfriday_schedule_session unknown never probed
Plan a Fun Friday game for a future date and time, and get back an invite link to put in the team's calendar invite or chat. The invite page shows the game and time in each person's own timezone and lets them add it to their calendar; when it is time, the host opens the room from the same link and the team joins with the code it shows. Nothing is used up until the room is opened. Use this for "set up trivia for Friday at 4" (or, with repeat_weekly, "every Friday at 4") — use funfriday_create_session instead when the team wants to play now. Confirm the game, day, time and timezone with the user before calling it.
{ "type": "object", "required": [ "game_type", "starts_at", "timezone" ], "properties": { "reminder": { "type": "boolean", "default": false, "description": "Email the organiser a reminder shortly before the start. Needs at least 16 minutes' notice. Default false." }, "timezone": { "type": "string", "description": "The organiser's IANA timezone, e.g. \"Europe/London\" or \"America/New_York\". Used to write the time on the invite." }, "game_type": { "enum": [ "trivia_blitz", "faker", "emoji_story", "two_truths", "caption_this", "hot_takes", "timeline", "drawing_blind", "bid_bluff", "hues_cues", "majority_rules", "typing_sprint", "odd_one_out", "guess_who", "ballpark", "zoomed_in", "plot_twist", "top_rank", "phrase_wheel", "bluff_trivia", "code_clues", "pin_drop", "defuse" ], "type": "string", "description": "Which game to plan. Call funfriday_list_games first if unsure; this is the internal key, not the display name (Imposter is \"faker\", Colour Clue is \"hues_cues\")." }, "starts_at": { "type": "string", "description": "When the game starts, as an ISO 8601 date-time with a UTC offset, e.g. \"2026-11-20T16:00:00+00:00\". Work it out in the user's own timezone; it must be in the future and within a year." }, "repeat_weekly": { "type": "boolean", "default": false, "description": "Repeat every week at the same local time, for a standing slot like \"every Friday at 4\". The invite link stays the same and always opens the next game, so it can go in a recurring calendar invite. Cancelling it on the invite page ends the series. Default false." } }, "additionalProperties": false }arguments 58 linesfunfriday_create_pack unknown never probed
Create a custom content pack for the user's Fun Friday team, so the team plays their own material: Trivia Blitz questions (pack_type "trivia"), Imposter word lists (pack_type "faker") or Emoji Story phrases (pack_type "emoji_story"). A custom pack replaces the game's built-in content with the team's own — in-jokes, company trivia, a theme for the week. Only these three games take custom packs; for any other game, say so rather than calling this. Send the content in the one list that matches pack_type (for Imposter, either words or word_groups), and write it to play well (see each list's description). The host picks the pack in the lobby before pressing Start. Custom packs need a Pro or Business plan, which caps how many a team can keep — call funfriday_get_team first if unsure.
{ "type": "object", "required": [ "pack_type", "name" ], "properties": { "name": { "type": "string", "description": "The pack's name as the team will see it in the lobby, e.g. \"Office trivia\". Up to 60 characters." }, "words": { "type": "array", "items": { "type": "string" }, "maxItems": 500, "minItems": 2, "description": "For pack_type \"faker\" only, when every word belongs to ONE theme: 2–500 related words or short phrases (up to 100 characters each). Each round pairs any two of them — one for the group, a near miss for the imposter — so they must all be the same kind of thing. Pick words close enough that the imposter can bluff (e.g. \"latte\", \"espresso\", \"cappuccino\"), not opposites or unrelated words. Ten or more gives variety across rounds. If the pack covers more than one theme, send word_groups instead." }, "phrases": { "type": "array", "items": { "type": "string" }, "maxItems": 500, "minItems": 1, "description": "For pack_type \"emoji_story\" only: 1–500 phrases for players to tell in emoji — film titles, sayings, team in-jokes (up to 200 characters each). Choose phrases a player could tell with a handful of emoji and the room could guess; avoid abstract or very long ones." }, "pack_type": { "enum": [ "trivia", "faker", "emoji_story" ], "type": "string", "description": "Which game the pack is for: \"trivia\" (Trivia Blitz), \"faker\" (Imposter) or \"emoji_story\" (Emoji Story)." }, "questions": { "type": "array", "items": { "type": "object", "required": [ "text", "options", "correct_index" ], "properties": { "text": { "type": "string", "description": "The question." }, "options": { "type": "array", "items": { "type": "string" }, "maxItems": 4, "minItems": 4, "description": "Exactly four answer options." }, "explanation": { "type": "string", "description": "Optional. One line on why the answer is right, shown to the room after the question closes (up to 300 characters). Worth adding for company or onboarding facts." }, "correct_index": { "type": "integer", "maximum": 3, "minimum": 0, "description": "Index (0–3) of the correct option in options." } }, "additionalProperties": false }, "maxItems": 100, "minItems": 1, "description": "For pack_type \"trivia\" only: the questions, 100 at most. Each has text (up to 300 characters), exactly four options (up to 100 characters each) and correct_index, the 0-based index of the right option. Make the three wrong options plausible, keep options similar in length, and vary which position is correct. Ten to twenty questions makes a good game." }, "word_groups": { "type": "array", "items": { "type": "object", "required": [ "name", "words" ], "properties": { "name": { "type": "string", "description": "What the group's words have in common, e.g. \"Our tools\". Up to 40 characters; players never see it." }, "words": { "type": "array", "items": { "type": "string" }, "minItems": 2, "description": "At least two words or short phrases of the same kind." } }, "additionalProperties": false }, "maxItems": 50, "minItems": 1, "description": "For pack_type \"faker\" only, instead of words, when the pack covers several themes (a company pack with tools, meetings and snacks): up to 50 groups, each with a name and at least 2 words of the same kind. A round deals both of its words from one group, so the imposter's word is always a near miss (\"Slack\" against \"Teams\", never \"Slack\" against \"Biscuits\"). Four or more words per group plays best; 500 words at most across all groups." } }, "additionalProperties": false }arguments 109 linesfunfriday_create_session changes data unknown never probed
Start a new Fun Friday game session and get back the room code and join link to share with the team. This opens a real room that people can join immediately — confirm with the user before calling it. Works without an account: the room is then limited to the free games, and whoever opens the join link first becomes the host and presses Start, so tell the user to open it themselves before sharing it. With a connected account the room runs on the team's plan, uses one of its games for the week, and its results go on the team leaderboard.
{ "type": "object", "required": [ "game_type" ], "properties": { "game_type": { "enum": [ "trivia_blitz", "faker", "emoji_story", "two_truths", "caption_this", "hot_takes", "timeline", "drawing_blind", "bid_bluff", "hues_cues", "majority_rules", "typing_sprint", "odd_one_out", "guess_who", "ballpark", "zoomed_in", "plot_twist", "top_rank", "phrase_wheel", "bluff_trivia", "code_clues", "pin_drop", "defuse" ], "type": "string", "description": "Which game to host. Call funfriday_list_games first if unsure; this is the internal key, not the display name (Imposter is \"faker\", Colour Clue is \"hues_cues\")." } }, "additionalProperties": false }arguments 38 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 id4d2ed9deb6764c4c.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/4d2ed9deb6764c4c/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/4d2ed9deb6764c4c?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
- 1
- ok
- 1
- failed
- 0
- success rate
- 100%
- median latency
- 145ms
- 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
- —
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.