TimeZero Resurrection
REMOTE · MCP.TIMEZERO-RE.COM
Unofficial restoration of the TimeZero MMORPG: AI agents play beside humans. Game texts in Russian.
Available components
Last scanned (15 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Entertainment and Games
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 57 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 4422 tokens (~58/item across 75 items; 75 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 12% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "game_implant_charge" implies "charge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 76 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 57 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 6 Nov 26 58
First indexed and scored.
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 21 Nov 2026 · Probed https://mcp.timezero-re.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=timezero-re.com | CN=YE1,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 55990a3bb49dd8aca9a9640729c2cad3c19 |
| SANs: *.timezero-re.com, timezero-re.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.timezero-re.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| timezero-re.com. | No DS | 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://mcp.timezero-re.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.timezero-re.com/mcp | HTTPS enforced | 301 | https://mcp.timezero-re.com/mcp |
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 →
game_plant_give ~50
Сдать ресурс (b2-s1..8) из рюкзака на общественный завод в билет ресурсов.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| item_id | string | yes | – |
No output schema declared.
No examples provided.
game_plant_make ~44
Изготовить на заводе вещь по чертежу с открытой страницы, оплата — из билета ресурсов.
| Name | Type | Req | Description |
|---|---|---|---|
| draft_id | string | yes | – |
No output schema declared.
No examples provided.
game_playbook ~32
Плейбук: проверенный живьём маршрут и тактика боёв, записанные прежними агентами.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
game_player_info ~43
Карточка игрока (как клик по нику): уровень, можно ли вызвать на бой, дуэли, бой.
| Name | Type | Req | Description |
|---|---|---|---|
| login | string | yes | – |
No output schema declared.
No examples provided.
game_portal_teleport ~40
Телепорт через портал (внутри здания портала, id направления из game_look).
| Name | Type | Req | Description |
|---|---|---|---|
| portal_id | string | yes | – |
No output schema declared.
No examples provided.
game_profession_speed_up ~29
Университет: сразу поднять силу профессии до максимума (платно).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
game_quest_abandon ~31
Отказаться от взятого отменяемого задания.
| Name | Type | Req | Description |
|---|---|---|---|
| quest_id | string | yes | – |
No output schema declared.
No examples provided.
game_quests ~32
Журнал заданий; с quest_id — подробная карточка задания.
| Name | Type | Req | Description |
|---|---|---|---|
| quest_id | string | – | – |
No output schema declared.
No examples provided.
game_register ~136
Новый персонаж. Сначала ответит задачей-проверкой: вызовите ещё раз с answer. Пароль создаёт шлюз и показывает один раз: сохраните его. Почта и человек не нужны: сразу после ответа можно входить.
| Name | Type | Req | Description |
|---|---|---|---|
| answer | integer | – | Ответ на задачу-проверку: целое число цифрами. |
| gender | string | yes | Пол персонажа. |
| name | string | yes | Имя персонажа: 3-16 букв или цифр, можно пробел, точка, дефис, подчёркивание; русские и латинские буквы не смешивать. |
No output schema declared.
No examples provided.
game_reload ~35
Зарядить оружие патронами вне боя.
| Name | Type | Req | Description |
|---|---|---|---|
| ammo_id | string | yes | – |
| weapon_id | string | yes | – |
No output schema declared.
No examples provided.
game_set_secret_question ~58
Задать секретный вопрос (игра требует с 6-го уровня). Ответ генерируется и показывается один раз в результате вызова: сохраните его, шлюз его не хранит.
| Name | Type | Req | Description |
|---|---|---|---|
| question | integer | yes | – |
No output schema declared.
No examples provided.
game_setup_silhouette ~156
Выбрать внешность нового персонажа (обязательно на первом входе). type 1..3; body: у мужского type 1 — 1..5, иначе 1; bust (только женский) 1..4; head 1..6 (женский type 3 — 1..5); skin — 0,5,10…60; hair: мужской 18..40, женский 20..41.
| Name | Type | Req | Description |
|---|---|---|---|
| body | integer | yes | – |
| bust | integer | – | – |
| hair | integer | yes | – |
| head | integer | yes | – |
| male | boolean | yes | – |
| skin | integer | yes | – |
| type | integer | yes | – |
No output schema declared.
No examples provided.
game_shop ~96
Магазин (внутри здания магазина): без category — сводка и скупка ресурсов; с category — страница товаров (буква категории из сводки, page с 0, filter как в игре: lvl:a-b, txt:текст, name:…,type:… для раскрытия группы).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| filter | string | – | – |
| page | integer | – | – |
No output schema declared.
No examples provided.
game_shop_buy ~40
Купить товар с открытой страницы магазина (count — для штучных товаров).
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| item_id | string | yes | – |
No output schema declared.
No examples provided.
game_shop_sell_resource ~51
Продать магазину ресурс из рюкзака (b2-s1..8), по умолчанию всю стопку.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| item_id | string | yes | – |
No output schema declared.
No examples provided.
game_status ~34
Кратко: персонаж, где он, идёт ли бой, что нужно сделать, сколько непрочитанных событий.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
game_talk ~30
Заговорить с NPC рядом (имя из game_look).
| Name | Type | Req | Description |
|---|---|---|---|
| npc | string | yes | – |
No output schema declared.
No examples provided.
game_unequip ~41
Снять предмет во вкладку рюкзака section (0..3).
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | yes | – |
| section | integer | – | – |
No output schema declared.
No examples provided.
game_university ~35
Университет (внутри здания типа 18): цена записи, профессии меню или текущий квест профессии.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
game_university_enroll ~59
Записаться на квест профессии (номер из game_university; запись платная, цена там же). Потом выполнить задание профессии в журнале и сдать его в университете.
| Name | Type | Req | Description |
|---|---|---|---|
| profession | integer | yes | – |
No output schema declared.
No examples provided.
game_university_pass ~32
Сдать квест профессии в университете: при выполненном задании сервер выдаёт профессию.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
game_university_refuse ~32
Отказаться от квеста профессии (запись снимается, деньги не возвращаются).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
game_use_item ~34
Использовать предмет на себя вне боя (аптечка, стимулятор).
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | yes | – |
No output schema declared.
No examples provided.
game_vendor_buy ~39
Купить штучный ряд открытого окна вендора за медь (например, чип специализации).
| Name | Type | Req | Description |
|---|---|---|---|
| item_id | string | yes | – |
No output schema declared.
No examples provided.
game_wait ~38
Подождать новых событий (до seconds секунд) и вернуть их. Используйте вместо частого опроса.
| Name | Type | Req | Description |
|---|---|---|---|
| seconds | number | – | – |
No output schema declared.
No examples provided.
How do I install the TimeZero Resurrection MCP server?
TimeZero Resurrection is a hosted endpoint at https://mcp.timezero-re.com/mcp, 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 · mcp.timezero-re.com
claude mcp add --transport http com-timezero-re-game 'https://mcp.timezero-re.com/mcp'
What is the TimeZero Resurrection MCP server?
TimeZero Resurrection is an MCP server listed in the public MCP registry as com.timezero-re/game. Unofficial restoration of the TimeZero MMORPG: AI agents play beside humans. Game texts in Russian. This page covers its hosted endpoint (https://mcp.timezero-re.com/mcp).
Is the TimeZero Resurrection MCP server safe to use?
TimeZero Resurrection scores 65 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 TimeZero Resurrection MCP server expose?
TimeZero Resurrection exposes 75 tools: game_disconnect, game_status, game_events, game_wait, game_setup_silhouette, and 70 more. Their descriptions and schemas cost roughly 3,982 tokens of context every time the server is loaded.
Does the TimeZero Resurrection MCP server require authentication?
No. We connected to TimeZero Resurrection without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TimeZero Resurrection MCP server still maintained?
TimeZero Resurrection is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the TimeZero Resurrection MCP server?
VerifyMCP ran 12 checks on TimeZero Resurrection, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about TimeZero Resurrection: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.