Talandor
Public MCP report

Delightful's Game Research Starter Pack

https://games.thisisdelightful.com/mcp

Official Registry

Official Registry · com.thisisdelightful/games-research-starter-pack · Publisher: com.thisisdelightful

Last observed

Usable now
Can I use it?

Usable now

A public MCP contract was observed. Add the endpoint to a compatible client below. A Watch can alert you if this contract changes.

https://games.thisisdelightful.com/mcp
Tools6
AuthNo authentication challenge observed
Protocol2025-11-25
EvidencePublic contract observed
Latency10439 ms

See the measured evidence

Client fit

Compatibility is inferred from published configuration rules and is not manually verified in each client.

Claude
Observed 2025-11-25.
Likely compatible · inferred
Cursor
Streamable HTTP and public HTTPS were observed.
Likely compatible · inferred
ChatGPT
Public tool names, descriptions and schemas were observed. Plan and workspace access still apply.
Likely compatible · inferred
VS Code
Public remote HTTP configuration can be assessed.
Likely compatible · inferred
Generic MCP
Observed 2025-11-25.
Likely compatible · inferred
Show compatibility evidence

Rule evidence: Remote HTTPS rule v0.2 · reviewed 2026-09-12 · Remote HTTP rule v0.2 · reviewed 2026-09-12 · Remote app rule v0.2 · reviewed 2026-09-12 · Protocol and transport rule v0.2 · reviewed 2026-09-12

What changed

Public contract stable since
Last compared · No semantic contract change since the previous complete snapshot.
Info
list_trends changed its input schema
· warning · medium confidence · list_trends · Rule: input-schema-changed
Warning

A Watch would alert only if this change may affect the selected client.

Show 1 quieter observation
Public contract stable since
Last compared · No semantic contract change since the previous complete snapshot.
Info
Evidence and limitations

Method: anonymous Streamable HTTP probe. We never invoke a tool.

Attempted protocols: 2026-07-28, 2025-11-25

Protocol2025-11-25
TransportStreamable HTTP
AuthNo authentication challenge observed
EvidencePublic contract observed
Total latency10439 ms
Response bytes8617

No diagnostic errors.

Server-provided content. Tool names, descriptions and schemas below are copied from the MCP server. They may be in another language. Talandor does not translate or verify them.
Tools and declared exposure

Server annotations are declarations, not verified behavior.

Show 6 of 6 server-provided tool definitions
get_landscape
No effect details provided
Show server-provided details
Server description (copied; language not verified)
The platform and genre maps. 35 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.
Input schema (server-provided preview — do not copy)
{
  "type": "object",
  "required": [
    "kind"
  ],
  "properties": {
    "kind": {
      "enum": [
        "platforms",
        "genres"
      ],
      "type": "string",
      "description": "Which map."
    }
  },
  "additionalProperties": false
}
get_market
No effect details provided
Show server-provided details
Server description (copied; language not verified)
How to research one of 10 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 ten have profiles — for any other market code, search_sources with a market filter is what exists.
Input schema (server-provided preview — do not copy)
{
  "type": "object",
  "required": [
    "code"
  ],
  "properties": {
    "code": {
      "enum": [
        "US",
        "JP",
        "KR",
        "UK",
        "DE",
        "FR",
        "CN",
        "MENA",
        "IT",
        "CA"
      ],
      "type": "string",
      "description": "Market code."
    }
  },
  "additionalProperties": false
}
get_source
No effect details provided
Show server-provided details
Server description (copied; language not verified)
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.
Input schema (server-provided preview — do not copy)
{
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Permanent identifier, e.g. \"sensor-tower\"."
    }
  },
  "additionalProperties": false
}
list_trends
No effect details provided
Show server-provided details
Server description (copied; language not verified)
The 37 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 dated further reading on request. 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 market, stage, category or a free-text query; every filter narrows the list and none of them orders it. Rows come 14 to a page: page with offset, or name one by slug to read it with its further reading. This is the fastest-decaying data here — every row is dated, and anything older than about six months needs a refresh.
Input schema (server-provided preview — do not copy)
{
  "type": "object",
  "properties": {
    "slug": {
      "type": "string",
      "description": "One trend by its permanent slug, as a list returns it. Comes back with its further reading unless include_further_reading says otherwise. The other filters are ignored when this is set."
    },
    "limit": {
      "type": "number",
      "description": "Rows per page, default 14, at most 37 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 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",
        "Perennial",
        "Emerging",
        "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",
        "Not market specific",
        "UK",
        "DE",
        "FR",
        "CN",
        "MENA",
        "IT",
        "SEA",
        "CA",
        "Nordics",
        "BR",
        "IN",
        "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."
    },
    "category": {
      "enum": [
        "Money & business model",
        "Regulation, safety & age",
        "Platform & distribution",
        "Culture & audience",
        "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
}
search_sources
No effect details provided
Show server-provided details
Server description (copied; language not verified)
Search 923 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.
Input schema (server-provided preview — do not copy)
{
  "type": "object",
  "properties": {
    "cost": {
      "enum": [
        "Free",
        "Paid",
        "Freemium",
        "Unknown"
      ],
      "type": "string",
      "description": "Recorded on 533 of 923 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",
        "Media",
        "Institutions",
        "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",
        "Not market specific",
        "UK",
        "DE",
        "FR",
        "CN",
        "MENA",
        "IT",
        "SEA",
        "CA",
        "Nordics",
        "BR",
        "IN",
        "MX",
        "ES",
        "TR",
        "NL",
        "AU",
        "PL",
        "TW",
        "EU",
        "LATAM",
        "Asia",
        "BE"
      ],
      "type": "string",
      "description": "Market code. US, JP, KR, UK, DE, FR, CN, MENA, IT, CA have full profiles behind them; SEA, Nordics, BR, IN, 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",
        "Italian",
        "Chinese",
        "Turkish",
        "Dutch",
        "Polish",
        "Traditional Chinese",
        "Bahasa Indonesia",
        "Multilingual",
        "Swedish",
        "Vietnamese",
        "Finnish",
        "Danish",
        "Norwegian",
        "Thai",
        "Hindi",
        "Indonesian",
        "Malay"
      ],
      "type": "string",
      "description": "The language you would be reading it in."
    }
  },
  "additionalProperties": false
}
search_techniques
No effect details provided
Show server-provided details
Server description (copied; language not verified)
39 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.
Input schema (server-provided preview — do not copy)
{
  "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",
        "Not market specific",
        "UK",
        "DE",
        "FR",
        "CN",
        "MENA",
        "IT",
        "SEA",
        "CA",
        "Nordics",
        "BR",
        "IN",
        "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
}

How to use this MCP

Talandor checks the server; it does not connect the server to your assistant.

Choose your client below, then copy the endpoint or configuration. Authentication is completed with the MCP provider, never inside Talandor.

Open the official client guide (opens in a new tab)
Observation history
Operational
· stable since
2025-11-25 · 6 tools · no change · 3 checks
Operational
· stable since
2025-11-25 · 6 tools · no change · 12 checks
Operational
2025-11-25 · 6 tools
Complete public contract · 2025-11-25 · 6 tools
9cbae0424dde
Complete public contract · 2025-11-25 · 6 tools
5581544057a5
Complete public contract · 2025-11-25 · 6 tools
5581544057a5

Deep monitoring eligibility

Eligible for deep monitoring

A complete public tools/list contract was observed, so a future deep-monitoring baseline can be compared safely.

Personal Watch is not open yet. This report does not start a Watch or a payment.

See public monitoring
Watch · 9 €/month

Watch this MCP

Your agent depends on this MCP. We tell you before a change breaks it.

  • Know when it goes downWe confirm an outage before we alert you, so a single failed check is not treated as a lasting outage.
  • Know when its contract changesWe compare complete public tool catalogs and authentication surfaces over time.
  • Know what changed and what to fixAn alert names the change and the next step for the client you selected.

Full public-contract coverage: Availability, protocol, auth and public tool contract changes can be compared.

Full WatchAvailability, protocol, auth and public tool contract changes
Surface WatchAvailability, TLS, protocol and auth surface — no private tool diff

When Watch is open, you will be able to add, pause, resume, replace, or remove up to five endpoints. Watch checkout is not open. This page does not start a payment. You can sign in from the header; that creates an account, not a Watch. Opening date: not announced yet. Hosted checkout remains closed.

See Watch price, terms and refunds