games-research-starter-pack
https://games.thisisdelightful.com
Registry code: 79939705ffda65e6
A free directory of the press, institutions, datasets, media, people and communities behind the video games industry across twelve profiled markets, plus the trends, platforms and genres that frame them. It answers where to look, not what is true: nothing here is ranked or scored, and a figure reached through it carries the authority of the outlet that published it and no more. Every response carries its own date, its licence and its caveats — pass those on rather than dropping them.
- endpoint
- https://games.thisisdelightful.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 games-research-starter-pack live?
- Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
- Is games-research-starter-pack free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does games-research-starter-pack have?
- 6 tools: get_landscape, get_market, get_source, list_trends, search_sources, search_techniques.
- Is games-research-starter-pack 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 98.7%· all time 98.7%
last good check
of 6 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- topic
- games & entertainment games
- used for
- find sources on the video game industry
- research a games market
- list games industry trends
- takes → gives
- text → data
- tools
- 6 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.
list_trends reads open 19h ago
The 50 conversations currently moving the games industry, each with what it is, why it matters, the markets it lands in, its stage, how old the row is, and where it sits on the Three Horizons: H1, the current system running down, H2, the transition and its four groups, H3, the emerging future, or perennial ground. The placements are an editorial reading, not a score, and every answer carries the key to them in horizons. A routing map rather than a synthesis: it names arguments and points at where they are happening, and takes no position on any of them. Filter by horizon, group, market, stage, category or a free-text query; every filter narrows the list and none of them ranks it. Rows come in the order /trends reads them, 14 to a page: page with offset. Name one by slug to read it in full, with its further reading and its claims: a dated timeline, figures, status, consequences, objections, talk and what to watch, each with the link it came from. A claim marked talk: true cites a player community: it shows what players are saying, which moves this industry, and weighs less than reporting. Never quote it as an event or a figure. A claim carrying retired came off its page on that date and is kept as the record: true when written, no longer part of the reading. This is the fastest-decaying data here — every row is dated, and anything older than about six months needs a refresh.
{ "type": "object", "properties": { "slug": { "type": "string", "description": "One trend by its permanent slug, as a list returns it. Comes back with its claims, and with its further reading unless include_further_reading says otherwise. The other filters are ignored when this is set." }, "group": { "enum": [ "makes-room", "rewriting-rules", "prolongs-h1", "stalled-bets" ], "type": "string", "description": "One of the four groups inside h2: shifts that make room for h3, rules being rewritten, moves that prolong h1, and bets that stalled. Only h2 trends carry one." }, "limit": { "type": "number", "description": "Rows per page, default and at most 14 without further reading and 10 with it. A page is the next rows in the order described, never the top ones — nothing here is ranked." }, "query": { "type": "string", "description": "Free text, matched against the name, what it is, why it matters, where to follow it, its category, its horizon label and line, and the titles of its further reading. All words must appear. A word filter, not a semantic search: \"layoffs\" finds the layoff trend, a synonym the rows never use finds nothing. Omit to browse a filter instead." }, "stage": { "enum": [ "Dominant", "Emerging", "Perennial", "Receding" ], "type": "string", "description": "Dominant is sustained mainstream coverage for a year or more. Emerging is real and accelerating. Perennial recurs cyclically. Receding was dominant and is cooling, kept so dated coverage is recognisable as dated." }, "market": { "enum": [ "US", "Global", "JP", "KR", "UK", "Not market specific", "DE", "IN", "BR", "FR", "CN", "MENA", "IT", "SEA", "CA", "Nordics", "MX", "ES", "TR", "NL", "AU", "PL", "TW", "EU", "LATAM", "Asia", "BE" ], "type": "string", "description": "Trends that reach this market: tagged to it directly, reached through an EU tag, or global. Each row then says which, in market_relevance, and the list comes back closest first. Most trends in games are global and apply everywhere." }, "offset": { "type": "number", "description": "Rows to skip before the first one returned, for paging. Default 0. The note on each page says what to pass for the next." }, "horizon": { "enum": [ "h1", "h2", "h3", "perennial" ], "type": "string", "description": "h1 is the currently dominant system, losing its fit. h3 is the early working examples of what may replace it. h2 is the turbulent ground between them, sorted into four groups. perennial is the pressures every horizon has to answer." }, "category": { "enum": [ "Money & business model", "Culture & audience", "Platform & distribution", "Regulation, safety & age", "Geography & power", "Technology" ], "type": "string" }, "include_further_reading": { "type": "boolean", "description": "Default false, and true when slug is given. Further reading roughly doubles a row, so at most 10 rows travel with it; ask for a row by slug to read one in full." } }, "additionalProperties": false }arguments 100 linessearch_sources reads open 19h ago
Search 995 curated sources on the video games industry: press outlets, trade associations, datasets, analysts, podcasts, books, YouTube channels and communities across 26 markets. Every one was opened and read before it was described, and each result says what it lets you find out, who owns it and what it costs. This answers "where would I look for this?" — it is a directory of sources, not a source of facts, and nothing in it is ranked or scored.
{ "type": "object", "properties": { "cost": { "enum": [ "Free", "Paid", "Freemium", "Unknown" ], "type": "string", "description": "Recorded on 592 of 995 rows — the press outlets and the individual people are not priced, so filtering on this excludes them rather than reporting them as not free." }, "group": { "enum": [ "Press", "Institutions", "Media", "Data", "Communities", "People" ], "type": "string", "description": "Broad kind of source." }, "limit": { "type": "number", "description": "Rows per page, default 20, maximum 50. A page is the next rows in file order, never the top ones — nothing here is ranked." }, "query": { "type": "string", "description": "Free text, matched against the name, the description and the owner. All words must appear. Omit to browse a filter instead." }, "market": { "enum": [ "US", "Global", "JP", "KR", "UK", "Not market specific", "DE", "IN", "BR", "FR", "CN", "MENA", "IT", "SEA", "CA", "Nordics", "MX", "ES", "TR", "NL", "AU", "PL", "TW", "EU", "LATAM", "Asia", "BE" ], "type": "string", "description": "Market code. US, JP, KR, UK, DE, IN, BR, FR, CN, MENA, IT, CA have full profiles behind them; SEA, Nordics, MX, ES, TR, NL, AU, PL, TW, EU, LATAM, Asia, BE only tag sources. Global means the source covers everything, and \"Not market specific\" means market is not its axis." }, "medium": { "enum": [ "News outlet", "Organisation", "Forum or community", "Video channel", "Person", "Data tool", "Podcast", "Book or paper", "Company disclosure", "Report or document", "Newsletter", "Research firm", "Link list" ], "type": "string", "description": "What form it takes." }, "offset": { "type": "number", "description": "Rows to skip before the first one returned, for paging. Default 0. The note on each page says what to pass for the next." }, "language": { "enum": [ "English", "Japanese", "Korean", "German", "French", "Spanish", "Portuguese", "Arabic", "Chinese", "Italian", "Turkish", "Dutch", "Polish", "Traditional Chinese", "Multilingual", "Bahasa Indonesia", "Hindi", "Swedish", "Vietnamese", "Finnish", "Danish", "Norwegian", "Thai", "Indonesian", "Malay" ], "type": "string", "description": "The language you would be reading it in." } }, "additionalProperties": false }arguments 123 linessearch_techniques reads open 19h ago
44 search techniques for games research, each with a query you can paste, what it surfaces and why it works. Includes local-language strategies for researching the Japanese, Korean and Chinese markets without reading the language. Use this before searching the open web on a games question — these are the queries that reach material a plain search buries.
{ "type": "object", "properties": { "query": { "type": "string", "description": "Your question in your own words, for example \"what are Japanese players saying about a launch\". Techniques are ranked by how many of its words they mention, so a whole question works better than one keyword." }, "market": { "enum": [ "US", "Global", "JP", "KR", "UK", "Not market specific", "DE", "IN", "BR", "FR", "CN", "MENA", "IT", "SEA", "CA", "Nordics", "MX", "ES", "TR", "NL", "AU", "PL", "TW", "EU", "LATAM", "Asia", "BE" ], "type": "string", "description": "Techniques for this market, plus the ones that apply everywhere." } }, "additionalProperties": false }arguments 43 linesget_landscape reads unknown 7h ago
The platform and genre maps. 38 platforms — storefronts, consoles, livestreaming and UGC — with who owns each and where its data lives. 30 genres with definitions, subgenres, example games, and the terms actually used in Chinese, Korean and Japanese. Read the genre map before comparing two datasets: the industry has no shared taxonomy and this records where the vendors disagree.
{ "type": "object", "required": [ "kind" ], "properties": { "kind": { "enum": [ "platforms", "genres" ], "type": "string", "description": "Which map." } }, "additionalProperties": false }arguments 17 linesget_market reads unknown 7h ago
How to research one of 12 games markets, and the profile behind it. It opens with before_you_start, the research notes for that market: which national annuals are paid and what is free, which venues are closed or could not be verified, which figures overlap or are published on a basis that will not compare, what a weekly chart does and does not count. Then known_gaps, what the directory does not hold for that market and where to go instead. Then a sourced narrative built from claims that each carry the link they came from, a market-size figure with the basis it was published on, a player-population figure with the definition of who was counted, and where that market's data lives. Only these twelve have profiles — for any other market code, search_sources with a market filter is what exists.
{ "type": "object", "required": [ "code" ], "properties": { "code": { "enum": [ "US", "JP", "KR", "UK", "DE", "IN", "BR", "FR", "CN", "MENA", "IT", "CA" ], "type": "string", "description": "Market code." } }, "additionalProperties": false }arguments 27 linesget_source reads unknown 7h ago
Retrieve one source by its slug, with everything recorded about it. Slugs come back from search_sources and are permanent — the same slug names the same source across releases, so it is what to cite.
{ "type": "object", "required": [ "slug" ], "properties": { "slug": { "type": "string", "description": "Permanent identifier, e.g. \"sensor-tower\"." } }, "additionalProperties": false }arguments 13 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 id79939705ffda65e6.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/79939705ffda65e6/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/79939705ffda65e6?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.