Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Backlog Quest

REMOTE · BACKLOG-QUEST-LAB.BRIGHT-MOOSE-6173.CHATGPT.SITE

Choose one game from a 2–12-title backlog and return a focused, time-boxed quest.

68 Trust /100

Last scanned (5 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 327 tokens (~327/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 4 Nov 26 68

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://backlog-quest-lab.bright-moose-6173.chatgpt.site/mcp-public

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.bright-moose-6173.chatgpt.site CN=WE1,O=Google Trust Services,C=US 25 Sept 2026 24 Dec 2026 ECDSA 256 ECDSA-SHA256 c146d67eeaba2ccb0e55d72aa3eb7d3c
SANs: *.bright-moose-6173.chatgpt.site
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of backlog-quest-lab.bright-moose-6173.chatgpt.site. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
site. present 31826 13 Verified
chatgpt.site. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://backlog-quest-lab.bright-moose-6173.chatgpt.site/mcp-public Verified 200
http (plaintext) http://backlog-quest-lab.bright-moose-6173.chatgpt.site/mcp-public HTTPS enforced 302 https://backlog-quest-lab.bright-moose-6173.chatgpt.site/mcp-public
MCP tools · 1 exposed · ~298 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_backlog_quest ~298

Read-only: choose exactly one title from an ordered 2–12 game backlog and return the selected game, session length, mood, language, and a ready-to-follow time-boxed instruction. It never launches, buys, installs, modifies, or accesses a game or account. Use quick to start immediately, focus for one clear objective, chill for low-pressure play, or challenge for a difficult but reachable objective. The same seed plus the same ordered games list selects the same game; omit seed for a fresh random choice. No account, store login, or payment is required. Game titles and seed are processed in memory and are not stored; only an aggregate request event is recorded.

NameTypeReqDescription
gamesarrayyesOrdered list of 2–12 distinct game titles to choose from. Order matters when seed is supplied.
langstring–Language of the generated instruction: en for English or ru for Russian. Defaults to en.
minutesinteger–Length of the play session in minutes. Defaults to 60.
moodstring–Quest style: quick starts immediately, focus picks one clear objective, chill avoids progress pressure, and challenge asks for a difficult but reachable objective. Defaults to focus.
seedstring–Optional repeatability key, up to 64 characters. The same seed plus the same normalized ordered games list selects the same game; omit it for a fresh cryptographically random choice.
NameTypeReqDescription
documentation_urlstringyesHuman-readable API and MCP documentation.
human_urlstringyesBrowser version of Backlog Quest with machine-source attribution.
privacystringyesHow request data and aggregate measurement are handled.
questobjectyesThe selected game and the bounded play instruction.

No examples provided.

Install

How do I install the Backlog Quest MCP server?

Backlog Quest is a hosted endpoint at https://backlog-quest-lab.bright-moose-6173.chatgpt.site/mcp-public, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · backlog-quest-lab.bright-moose-6173.chatgpt.site

# add to Claude Code
claude mcp add --transport http site-chatgpt-bright-moose-6173-backlog-quest-lab 'https://backlog-quest-lab.bright-moose-6173.chatgpt.site/mcp-public'
Common questions

What is the Backlog Quest MCP server?

Backlog Quest is an MCP server listed in the public MCP registry as site.chatgpt.bright-moose-6173.backlog-quest-lab/backlog-qu…. Choose one game from a 2–12-title backlog and return a focused, time-boxed quest. This page covers its hosted endpoint (https://backlog-quest-lab.bright-moose-6173.chatgpt.site/mcp-public).

Is the Backlog Quest MCP server safe to use?

Backlog Quest scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Backlog Quest MCP server expose?

Backlog Quest exposes 1 tool: create_backlog_quest. Their descriptions and schemas cost roughly 298 tokens of context every time the server is loaded.

Does the Backlog Quest MCP server require authentication?

No. We connected to Backlog Quest without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Backlog Quest MCP server still maintained?

Backlog Quest is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.