MCP servers › com.timezero-re › game
MCP server · registry snapshot 2026-11-07 · last tested 2026-11-07
game MCP server
Registry name com.timezero-re/game
TimeZero Resurrection — the publisher's title
by timezero-re.com · domain (the registry's namespace rule)Website ↗
Unofficial restoration of the TimeZero MMORPG: AI agents play beside humans. Game texts in Russian. — the publisher's description
Summary
com.timezero-re/game is a remote MCP server listed in the official MCP registry at version 0.2.0, under the namespace of the domain timezero-re.com. On 2026-11-07 ProtocolProbe connected to it in read-only mode and read its inventory: 75 tools, 0 resources and 0 prompts.
Record checks
1 of 2 record checks met · 7 do not apply
- met: Registry entry is active and says how to run it
- not met: Source repository link opens
- not applicable: Repository is not archived
- not applicable: Code pushed to the repository in the 90 days before our check
- not applicable: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
From public records, not a safety rating. Each check with its reason
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- none needed to open a session
- Tools
- 75
- Last tested
- 2026-11-07
Tool list size
11,427 tokens on Claude Opus 5.5
Added to every request that loads this server's tools (75 tools). Counted with Anthropic's token counter on 2026-11-09, from the tool list we read on 2026-11-07. Median across 28,560 counted servers: 2,657 tokens. How it is counted
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-11-07 (mcp.timezero-re.com), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list at the three APIs
Not sent yet for this version (0.2.0).
Observed fact
This server accepted a session without any credential and lists 5 tools whose name or declaration suggests they change data (game_set_secret_question, game_move, game_move_item, game_cityhall_modify, game_battle_clear). That is our reading of the names; we did not call them. Source: our connection, 2026-11-07.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-11-07
- Mode
- read-only (no tool calls)
- Latest version
- 0.2.0, published 2026-11-06 (registry, as of the 2026-11-07 snapshot)
- First listed version
- 2026-11-06 (earliest version still in the registry; older removed versions would be earlier)
- Registry data
- snapshot 2026-11-07
- Package and repository
- checked 2026-11-07
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
New in the registry: not in the list of 2026-11-06, listed on 2026-11-07 with version 0.2.0 (published 2026-11-06).
Source: the official MCP Registry list on 2026-11-06 and on 2026-11-07.
What it is
What does this server offer?
Observed inventoryNone of its 75 tools are described as changing anything. For 75 the reading was uncertain, so no mark is shown.
- game_disconnect
“Выйти из игры (закрыть соединения).”
Publisher declares: read-only no
Takes no inputs.
- game_statuson 2 other servers
“Кратко: персонаж, где он, идёт ли бой, что нужно сделать, сколько непрочитанных событий.”
Publisher declares: read-only yes
Takes no inputs.
- game_events
“Прочитать новые события игры (сообщения сервера, бой, NPC, инвентарь).”
Publisher declares: read-only yes
1 input
limitinteger
- game_waiton 2 other servers
“Подождать новых событий (до seconds секунд) и вернуть их.”
Publisher declares: read-only yes
1 input
secondsnumber
- game_setup_silhouette
“Выбрать внешность нового персонажа (обязательно на первом входе).”
Publisher declares: read-only no
7 inputs, 6 required
malebooleanrequiredtypeintegerrequiredbodyintegerrequiredbustintegerheadintegerrequiredskinintegerrequiredhairintegerrequired
- game_accept_license
“Принять пользовательское соглашение игры (кнопка окна при первом входе).”
Publisher declares: read-only no
Takes no inputs.
- game_set_secret_question
“Задать секретный вопрос (игра требует с 6-го уровня).”
Publisher declares: read-only no
1 input, 1 required
questionintegerrequired
- game_look
“Осмотреться: клетка, здания (Z для входа), NPC, игроки рядом, соседние клетки; в шахте — карта.”
Publisher declares: read-only yes
Takes no inputs.
- game_move
“Шаг в соседнюю клетку мира.”
Publisher declares: read-only no
2 inputs, 1 required
directionstringrequiredslowboolean
- game_enter_building
“Войти в здание на своей клетке по его Z из game_look.”
Publisher declares: read-only no
1 input, 1 required
zintegerrequired
- game_leave_building
“Выйти из здания на улицу (из шахты — только из комнаты 0).”
Publisher declares: read-only no
Takes no inputs.
- game_portal_teleport
“Телепорт через портал (внутри здания портала, id направления из game_look).”
Publisher declares: read-only no
1 input, 1 required
portal_idstringrequired
Show 63 more tools
- game_talk
“Заговорить с NPC рядом (имя из game_look).”
Publisher declares: read-only no
1 input, 1 required
npcstringrequired
- game_dialog
“Показать открытый диалог с вариантами ответа.”
Publisher declares: read-only yes
Takes no inputs.
- game_dialog_answer
“Выбрать вариант в открытом диалоге (id варианта из game_dialog).”
Publisher declares: read-only no
1 input, 1 required
option_idstringrequired
- game_quests
“Журнал заданий; с quest_id — подробная карточка задания.”
Publisher declares: read-only yes
1 input
quest_idstring
- game_quest_abandon
“Отказаться от взятого отменяемого задания.”
Publisher declares: read-only no
1 input, 1 required
quest_idstringrequired
- game_inventory
“Рюкзак и надетое: id, названия, количество, качество, слоты, требования.”
Publisher declares: read-only yes
1 input
sectioninteger
- game_equip
“Надеть предмет (занятые слоты клиент освободит сам).”
Publisher declares: read-only no
2 inputs, 1 required
item_idstringrequiredslotstring
- game_unequip
“Снять предмет во вкладку рюкзака section (0..3).”
Publisher declares: read-only no
2 inputs, 1 required
item_idstringrequiredsectioninteger
- game_move_item
“Переложить предмет между вкладками рюкзака (0..3).”
Publisher declares: read-only no
2 inputs, 2 required
item_idstringrequiredsectionintegerrequired
- game_reload
“Зарядить оружие патронами вне боя.”
Publisher declares: read-only no
2 inputs, 2 required
weapon_idstringrequiredammo_idstringrequired
- game_use_item
“Использовать предмет на себя вне боя (аптечка, стимулятор).”
Publisher declares: read-only no
1 input, 1 required
item_idstringrequired
- game_open_pack
“Открыть набор или подарок из рюкзака (вещи падают в рюкзак).”
Publisher declares: read-only no
1 input, 1 required
item_idstringrequired
- game_shop
“Магазин (внутри здания магазина): без category — сводка и скупка ресурсов; с category — страница товаров (буква категории из сводки, page с 0, filter как в игре: lvl:a-b, txt:текст, name:…,type:… для…”
Publisher declares: read-only yes
3 inputs
categorystringfilterstringpageinteger
- game_shop_buy
“Купить товар с открытой страницы магазина (count — для штучных товаров).”
Publisher declares: read-only no
2 inputs, 1 required
item_idstringrequiredcountinteger
- game_shop_sell_resource
“Продать магазину ресурс из рюкзака (b2-s1..8), по умолчанию всю стопку.”
Publisher declares: read-only no
2 inputs, 1 required
item_idstringrequiredcountinteger
- game_plant
“Общественный завод (здание типа 36): без category — сводка категорий чертежей, с category — страница по 8 чертежей (page с 0).”
Publisher declares: read-only yes
2 inputs
categorystringpageinteger
- game_plant_buy
“Купить продукт чертежа завода за золото (id чертежа со страницы завода).”
Publisher declares: read-only no
2 inputs, 1 required
draft_idstringrequiredcountinteger
- game_plant_give
“Сдать ресурс (b2-s1..8) из рюкзака на общественный завод в билет ресурсов.”
Publisher declares: read-only no
2 inputs, 2 required
item_idstringrequiredcountintegerrequired
- game_plant_make
“Изготовить на заводе вещь по чертежу с открытой страницы, оплата — из билета ресурсов.”
Publisher declares: read-only no
1 input, 1 required
draft_idstringrequired
- game_auction
“Аукцион (внутри здания типа 56): без category — сводка (комиссия, хранение, срок); с category — страница по 8 (s — ресурсы, 1 — мои лоты; filter пустой — карточки полки, «name:…,type:…» — лоты карточ…”
Publisher declares: read-only yes
3 inputs
categorystringfilterstringpageinteger
- game_auction_buy
“Купить лот с открытой страницы аукциона (цена за штуку; count — для стопки).”
Publisher declares: read-only no
2 inputs, 1 required
item_idstringrequiredcountinteger
- game_auction_sell
“Выставить вещь из рюкзака на аукцион с фиксированной ценой (price — за штуку, строка с точкой; count — для стопки).”
Publisher declares: read-only no
3 inputs, 2 required
item_idstringrequiredpricestringrequiredcountinteger
- game_auction_take
“Забрать свой лот со страницы «Мои вещи» (плата за хранение за каждые начатые сутки).”
Publisher declares: read-only no
2 inputs, 1 required
item_idstringrequiredcountinteger
- game_kalita_open
“Открыть окно скупщика Алекса Калиты (общественный завод Нью-Москвы).”
Publisher declares: read-only no
Takes no inputs.
- game_kalita_sell
“Продать вещь Калите: сначала его цена, потом продажа (берёт только вещи своего списка).”
Publisher declares: read-only no
1 input, 1 required
item_idstringrequired
- game_genetic
“Генетика в больнице (бесплатная операция): перенос параметров один в один, shifts — «str:81,dex:-9,int:-15,pow:-39,acc:-12,intel:-6».”
Publisher declares: read-only no
1 input, 1 required
shiftsstringrequired
- game_hospital_cure
“Лечиться в больнице (внутри здания типа 5): котировка и полный курс за медь — HP, выбитые слоты и отравление.”
Publisher declares: read-only no
Takes no inputs.
- game_implant
“Больница: вживить имплант (insert + slot) или удалить (delete).”
Publisher declares: read-only no
3 inputs
insertstringslotstringdeletestring
- game_implant_charge
“Больница: зарядить вживлённый имплант (медь по цене импланта, 30 дней).”
Publisher declares: read-only no
1 input, 1 required
item_idstringrequired
- game_cityhall_modify
“Модификация брони в мэрии (внутри здания типа 7): переделать вещи комплекта из рюкзака под другую фигуру (мужская ↔ женская), цена — медь за каждую вещь; пару дизайна проверяет сервер.”
Publisher declares: read-only no
1 input, 1 required
item_idsarrayrequired
- game_money_exchange
“Разменять золото (gold) или серебро (silver) на медь, как кнопка «Разменять» в панели денег: сначала курс, потом размен; count — сколько монет, до 0.01.”
Publisher declares: read-only no
2 inputs, 2 required
currencystringrequiredcountnumberrequired
- game_perk_shop
“Окно покупки перков (кнопка «Купить перки» в панели перков, вне боя): ряды вендора «Перки» с id, ценой и требованиями.”
Publisher declares: read-only yes
Takes no inputs.
- game_perk_buy
“Купить за медь один перк из открытого окна game_perk_shop (перк появится в панели перков; перк с применением — game_use_item).”
Publisher declares: read-only no
1 input, 1 required
item_idstringrequired
- game_vendor_buy
“Купить штучный ряд открытого окна вендора за медь (например, чип специализации).”
Publisher declares: read-only no
1 input, 1 required
item_idstringrequired
- game_apply_chip
“Применить чип специализации из рюкзака (специализация сета: перк включается, когда надето нужное число вещей сета).”
Publisher declares: read-only no
1 input, 1 required
item_idstringrequired
- game_university
“Университет (внутри здания типа 18): цена записи, профессии меню или текущий квест профессии.”
Publisher declares: read-only yes
Takes no inputs.
- game_university_enroll
“Записаться на квест профессии (номер из game_university; запись платная, цена там же).”
Publisher declares: read-only no
1 input, 1 required
professionintegerrequired
- game_university_pass
“Сдать квест профессии в университете: при выполненном задании сервер выдаёт профессию.”
Publisher declares: read-only no
Takes no inputs.
- game_university_refuse
“Отказаться от квеста профессии (запись снимается, деньги не возвращаются).”
Publisher declares: read-only no
Takes no inputs.
- game_profession_speed_up
“Университет: сразу поднять силу профессии до максимума (платно).”
Publisher declares: read-only no
Takes no inputs.
- game_military
“Военкомат (внутри здания типа 35, Recruit Base): миссии с временем вылета, призом, набором бойцов, вкладки боекомплекта и повестка в рюкзаке; refresh — заново запросить список.”
Publisher declares: read-only yes
1 input
refreshboolean
- game_military_sign_up
“Подписаться на миссию военкомата (взнос 300 меди): mission_id из game_military, section — боекомплект (1 Штурмовик, 2 Снайпер).”
Publisher declares: read-only no
2 inputs, 2 required
mission_idstringrequiredsectionintegerrequired
- game_military_return
“Сдать повестку военкомата (возвращается половина взноса).”
Publisher declares: read-only no
Takes no inputs.
- game_arsenal
“Склад арсенала (внутри здания типа 2): бесплатные предметы с id, количеством и требованиями.”
Publisher declares: read-only yes
Takes no inputs.
- game_arsenal_take
“Взять предмет со склада арсенала в рюкзак: стопку целиком или count штук; section — вкладка рюкзака 0..3.”
Publisher declares: read-only no
3 inputs, 1 required
item_idstringrequiredcountintegersectioninteger
- game_player_info
“Карточка игрока (как клик по нику): уровень, можно ли вызвать на бой, дуэли, бой.”
Publisher declares: read-only yes
1 input, 1 required
loginstringrequired
- game_duel_challenge
“Вызвать игрока на дуэль с подтверждением (после game_player_info, не раньше чем через секунду; оба на одной клетке вне купола Ocean).”
Publisher declares: read-only no
1 input, 1 required
loginstringrequired
- game_duel_answer
“Ответить на вызов на дуэль: accept=true — начать бой, false — отказать.”
Publisher declares: read-only no
1 input, 1 required
acceptbooleanrequired
- game_duel_cancel
“Отменить свой вызов на дуэль, пока цель не ответила (таймаута у вызова нет).”
Publisher declares: read-only no
Takes no inputs.
- game_battle
“Состояние боя: ход, секунды, ОД, враги с дистанцией, кто в тумане, режимы оружия, лут, план; with_map — карта вокруг.”
Publisher declares: read-only yes
1 input
with_mapboolean
- game_battle_plan
“Добавить действия в план хода (клиент проверит ОД, путь, патроны, зоны): move{bx,by}; shoot{target,fire_type,zone,weapon_id?}; shoot_cell{bx,by,fire_type}; heal{item_id} (предмет в руке); reload{weap…”
Publisher declares: read-only no
1 input, 1 required
actionsarrayrequired
- game_battle_submit
“Отправить план хода серверу (один раз за ход).”
Publisher declares: read-only no
Takes no inputs.
- game_battle_clear
“Очистить неотправленный план хода.”
Publisher declares: read-only no
Takes no inputs.
- game_attack_monsters
“Напасть на монстров на клетке или в комнате шахты (антибот сервера: не часто).”
Publisher declares: read-only no
Takes no inputs.
- game_mine
“Шахта: комната, таймер шага, проходы, NPC-шахтёры, карта вокруг.”
Publisher declares: read-only yes
Takes no inputs.
- game_mine_step
“Шаг по шахте в соседнюю комнату.”
Publisher declares: read-only no
1 input, 1 required
directionstringrequired
- game_mine_metro
“Воспользоваться станцией метро в шахте (нужен Red Key).”
Publisher declares: read-only no
Takes no inputs.
- game_playbook
“Плейбук: проверенный живьём маршрут и тактика боёв, записанные прежними агентами.”
Publisher declares: read-only yes
Takes no inputs.
- game_register
“Новый персонаж.”
Publisher declares: read-only no
3 inputs, 2 required
namestringrequired“Имя персонажа: 3-16 букв или цифр, можно пробел, точка, дефис, подчёркивание; русские и латинские буквы не смешивать.”genderstringrequired“Пол персонажа.”answerinteger“Ответ на задачу-проверку: целое число цифрами.”
- game_login
“Войти в игру персонажем.”
Publisher declares: read-only no
3 inputs, 2 required
loginstringrequired“Имя персонажа.”passwordstringrequired“Пароль персонажа.”answerinteger“Ответ на задачу-проверку: целое число цифрами.”
- game_challenge_answer
“Ответ на задачу-проверку, выданную при входе или в игре (в ленте событий, вид «проверка»).”
Publisher declares: read-only no
1 input, 1 required
answerintegerrequired“Ответ на задачу-проверку: целое число цифрами.”
- game_chat_say
“Сказать в чат локации; to — обращение к игроку рядом.”
Publisher declares: read-only no
2 inputs, 1 required
textstringrequired“Текст.”tostring“Обратиться к игроку рядом: его логин.”
- game_chat_private
“Личное сообщение.”
Publisher declares: read-only no
2 inputs, 2 required
loginstringrequired“Логин: только тот, кто писал вашему персонажу, или сосед по бою.”textstringrequired“Текст.”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-07.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 12% of 89
- Tools with a description
- 100% of 75
- Typical description length
- 105 characters
The tool set
Counted from the listing
- Tools
- 75
- Size of the list
- about 6,778 tokens for an agent to load (characters ÷ 4)
- Naming
- 75 of 75 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 75 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the remote endpoint (Streamable HTTP)
We connected to this URL on 2026-11-07 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://mcp.timezero-re.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"game": {
"url": "https://mcp.timezero-re.com/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"game": {
"type": "http",
"url": "https://mcp.timezero-re.com/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"game","type":"http","url":"https://mcp.timezero-re.com/mcp"}'Claude Code
claude mcp add --transport http game https://mcp.timezero-re.com/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"game": {
"type": "streamableHttp",
"url": "https://mcp.timezero-re.com/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"game": {
"httpUrl": "https://mcp.timezero-re.com/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.game] url = "https://mcp.timezero-re.com/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"game": {
"url": "https://mcp.timezero-re.com/mcp"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.timezero-re.com/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint mcp.timezero-re.com/mcp | Session opened | matches | our test · 2026-11-07 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-11-07 |
Choosing
Record checks
Public records · not a safety rating1 of 2 record checks met · 7 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
- Does not applyRepository is not archivedNo public GitHub repository to read.
- Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
- Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-07. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about com.timezero-re/game
Answered from the data aboveWho publishes com.timezero-re/game?
The registry ties the namespace com.timezero-re to the domain timezero-re.com; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.
Does com.timezero-re/game need an API key or sign-in?
It opened a session without any credential on 2026-11-07. The registry entry declares no required credential; no declaration is not a guarantee.
Has com.timezero-re/game been security tested?
Partly. 2 of the 14 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Open without sign-in
It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: not applicable
2 exercised12 not run (reason given)4 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable
Source: our own test, 2026-11-07, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 1,716 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 75 tools, 0 resources, 0 prompts.
- 5,337 msFinished: 2 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “com.timezero-re/game: MCP server record.” Data checked 2026-11-07. https://protocolprobe.com/mcp/servers/com.timezero-re/game
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/com.timezero-re/game)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology