# Planner — provable "done" for AI agents (remote · planner.monopoly-gold.com)

Goal decomposition where every "done" is proven by evidence and checked by a judge.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `planner.monopoly-gold.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-monopoly-gold-planner-mcp/mcp.md), [page](https://verifymcp.io/servers/com-monopoly-gold-planner-mcp/mcp)

## Channel facts

- Endpoint: `https://planner.monopoly-gold.com/_mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 6468 tokens (~154/item across 42 items; 38 tools + 4 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 99% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-monopoly-gold-planner-mcp https://planner.monopoly-gold.com/_mcp
```

### Codex

```toml
[mcp_servers.com-monopoly-gold-planner-mcp]
url = "https://planner.monopoly-gold.com/_mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-monopoly-gold-planner-mcp": {
      "type": "remote",
      "url": "https://planner.monopoly-gold.com/_mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-monopoly-gold-planner-mcp --url https://planner.monopoly-gold.com/_mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-monopoly-gold-planner-mcp:
    url: "https://planner.monopoly-gold.com/_mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-monopoly-gold-planner-mcp": {
      "type": "http",
      "url": "https://planner.monopoly-gold.com/_mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 70, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 67)

First indexed and scored.

## MCP tools (38)

### `project-list` (~70 tokens)

List all projects with optional status filter (active/archived/paused). Returns id, title, slug, webUrl, icon, and goals_count for each project. Use project-get for full details with goals breakdown by status.

Input parameters:

- `status` (string): Статус: active / archived / paused

### `project-create` (~236 tokens)

Create a new project container for goals. Requires title and a unique slug (lowercase a-z, 0-9, hyphens). Optional: description, status (active/archived/paused, default active), tags, icon (emoji), repositoryPath, repositoryUrl, isDefault. Returns the created project with id, slug, and webUrl. Slug must be unique — duplicates are rejected with existing slugs list.

Input parameters:

- `description` (string): Описание проекта
- `icon` (string): Иконка (эмодзи, макс. 10 символов)
- `isDefault` (boolean): Сделать проектом по умолчанию
- `repositoryPath` (string): Путь к репозиторию на сервере
- `repositoryUrl` (string): URL репозитория
- `slug` (string, required): Уникальный slug (только a-z, 0-9, дефис)
- `status` (string): Статус: active / archived / paused (default: active)
- `tags` (array): Теги
- `title` (string, required): Название проекта

### `project-get` (~64 tokens)

Fetch full project details: title, slug, status, description, icon, tags, repository info, goals breakdown by status (backlog/in_progress/blocked/done/cancelled counts), and depends_on list of project dependencies.

Input parameters:

- `projectId` (string, required): UUID проекта

### `project-update` (~455 tokens)

Partial update of a project — only the fields you pass are changed; omitted fields are untouched. Updatable: title, slug, description, status (active/archived/paused), tags, icon (emoji), repositoryPath, repositoryUrl, isDefault, redTeamMode (optional/advisory/required), evidenceJudgeMode (off/optional/required), allowedGoalMode (any/grove_only), fmeaGenerationMode (off/on), escalationResolveTimeout (off/1h/4h/24h), escalationAutoResolveBy (none/planner-agent), escalationAutoResolveStrategy (suggest-edit/reject-default). Returns the updated project with all fields.

Input parameters:

- `allowedGoalMode` (string): Разрешённые режимы целей: any, grove_only
- `description` (string): Новое описание
- `escalationAutoResolveBy` (string): Авто-резолвер эскалации: none, planner-agent
- `escalationAutoResolveStrategy` (string): Стратегия авто-резолва: suggest-edit, reject-default
- `escalationResolveTimeout` (string): Таймаут эскалации: off, 1h, 4h, 24h
- `evidenceJudgeMode` (string): Режим судьи доказательств: off, optional, required
- `fmeaGenerationMode` (string): FMEA-генерация: off, on
- `icon` (string): Иконка (эмодзи, макс. 10 символов)
- `isDefault` (boolean): Сделать проектом по умолчанию
- `projectId` (string, required): UUID проекта
- `redTeamMode` (string): Режим red-team: optional, advisory, required
- `repositoryPath` (string): Путь к репозиторию на сервере
- `repositoryUrl` (string): URL репозитория
- `slug` (string): Новый slug (только a-z, 0-9, дефис; должен быть уникальным)
- `status` (string): Новый статус: active, archived, paused
- `tags` (array): Новые теги
- `title` (string): Новое название

### `project-delete` (~86 tokens)

Delete a project. If the project has goals, pass force=true to cascade-delete them all; without force, the call is rejected with the goals count. Returns deleted title, slug, and goals_deleted count.

Input parameters:

- `force` (boolean): Удалить вместе со всеми целями (default: false — откажет если есть цели)
- `projectId` (string, required): UUID проекта

### `project-add-dependency` (~101 tokens)

Declare that one project depends on another (depends-on relationship). Accepts UUID or slug for both sides. Idempotent: if the dependency already exists, returns it with already_existed=true. Self-references are rejected. No cycle detection — the caller is responsible for avoiding circular chains.

Input parameters:

- `dependsOnProjectId` (string, required): UUID или slug проекта, от которого зависит
- `projectId` (string, required): UUID или slug проекта-зависимого

### `project-remove-dependency` (~113 tokens)

Remove a project dependency. Two lookup modes: pass dependency_id (UUID of the link itself), or pass both projectId and dependsOnProjectId (UUID or slug). Returns removed=true on success, removed=false if the dependency was not found.

Input parameters:

- `dependencyId` (string): UUID самой связи
- `dependsOnProjectId` (string): UUID или slug целевого проекта (если dependencyId не задан)
- `projectId` (string): UUID или slug проекта-зависимого (если dependencyId не задан)

### `goal-list` (~186 tokens)

List goals with optional filters: projectId (UUID), status (backlog/in_progress/blocked/done/cancelled), type (goal/milestone/task/habit), parentId (UUID — direct children only). Returns up to limit results (default 50, no offset pagination). Sorted by priority ASC then createdAt DESC. Each entry has id, title, webUrl, status, priority, type, progress, parent_id, project_id.

Input parameters:

- `limit` (integer): Макс. кол-во результатов (default: 50)
- `parentId` (string): UUID родителя (только прямые дети)
- `projectId` (string): UUID проекта (фильтр)
- `status` (string): Статус: backlog, in_progress, blocked, done, cancelled
- `type` (string): Тип: goal, milestone, task, habit

### `goal-create` (~335 tokens)

Create a goal/task/milestone/habit in the planning tree. Two modes: grove (default) — enforces acceptance criteria gate on status transitions (AC required before in_progress, file-evidence per AC before done); standard — carries the same AC but without the evidence gate (advisory linting only). Returns the created goal with id, webUrl, mode, and nextStep hint. Every goal must belong to a project (pass projectId or inherit from parent).

Input parameters:

- `acceptanceCriteria` (array): Список AC-формулировок. Grove: опциональны на create, обязательны до перехода в in_progress, блокирующий quality-линтер. Standard: описательные, линтер advisory
- `deadline` (string): Дедлайн ISO 8601
- `description` (string): Описание
- `estimate` (string): Оценка
- `mode` (string): Режим: grove (default) или standard. Grove enforce-ит I_start на in_progress и I₃ на done; standard несёт те же AC, но без evidence-гейта
- `parentId` (string): UUID родителя (null = root)
- `priority` (integer): Приоритет 1–5 (default: 3)
- `projectId` (string): UUID проекта
- `status` (string): backlog (default) / in_progress
- `tags` (array): Теги
- `title` (string, required): Название цели (макс. 500)
- `type` (string): goal / milestone / task / habit (default: task)

### `goal-get` (~73 tokens)

Fetch full details of a single goal: title, description, status, priority, type, mode, children, acceptance criteria (with evidence coverage), blockers, tags, deadline, estimate, history log, and project. The primary drill-down tool after goal-list or goal-tree.

Input parameters:

- `goalId` (string, required): UUID цели

### `goal-update` (~254 tokens)

Partial update of a goal — only the fields you pass are changed; omitted fields are untouched. Updatable: title, status, priority (1-5), description, type, tags, deadline, estimate, mode. Status transitions are validated (backlog→in_progress→done|cancelled; blocked→in_progress). Grove mode enforces gates: in_progress requires ≥1 AC, done requires file-evidence on every AC + session_history. Returns the updated goal with all fields.

Input parameters:

- `deadline` (string): Новый дедлайн (ISO 8601)
- `description` (string): Новое описание
- `estimate` (string): Новая оценка
- `goalId` (string, required): UUID цели
- `mode` (string): Режим цели: standard или grove. Иммутабелен после mode_locked_at
- `priority` (integer): Новый приоритет (1–5)
- `status` (string): Новый статус: backlog, in_progress, blocked, done, cancelled
- `tags` (array): Новые теги
- `title` (string): Новое название (макс. 500)
- `type` (string): Новый тип: goal, milestone, task, habit

### `goal-delete` (~74 tokens)

IRREVERSIBLY delete a goal and all its descendants (children, evidence, blockers). Prefer goal-update status=cancelled to preserve history, or goal-block to mark an obstacle. Use delete only for erroneous/duplicate entries. Returns the deleted title and children_deleted count.

Input parameters:

- `goalId` (string, required): UUID цели

### `goal-move` (~134 tokens)

Move a goal to a different parent or project. Pass newParentId=UUID to reparent (inherits project from new parent), newParentId=null to make root. Optional projectId=UUID overrides the target project when making root (cross-project move to root). Cascades project change to all descendants. Prevents cycles.

Input parameters:

- `goalId` (string, required): UUID перемещаемой цели
- `newParentId` (string): UUID нового родителя (null = сделать root)
- `projectId` (string): UUID целевого проекта (используется при newParentId=null для cross-project move в корень)

### `goal-reorder` (~78 tokens)

Set display order of sibling goals within the same parent and priority band. Pass an array of goal UUIDs in the desired order — each is assigned position = its array index. All goals must share the same parent and priority.

Input parameters:

- `ids` (array, required): UUID целей в новом порядке (все должны иметь одного родителя и одинаковый priority)

### `goal-block` (~215 tokens)

Add a blocker to a goal (blockers are additive — each call appends a new one, existing blockers are preserved). Sets status to blocked. Optionally create an inline resolver goal (resolverTitle) or link an existing one (linkedGoalId) — mutually exclusive. When the last active blocker is removed via goal-remove-blocker, the goal returns to its previous status.

Input parameters:

- `description` (string, required): Описание блокера — что мешает
- `goalId` (string, required): UUID блокируемой цели
- `linkedGoalId` (string): UUID существующей цели-резолвера (взаимоисключающе с resolverTitle)
- `resolverDescription` (string): Описание цели-резолвера
- `resolverParentId` (string): UUID родителя резолвера (default = goalId, т.е. дочерняя)
- `resolverTitle` (string): Заголовок новой цели-резолвера (взаимоисключающе с linkedGoalId)

### `goal-remove-blocker` (~74 tokens)

Remove a blocker from a goal by blocker UUID. If it was the last active blocker, the goal automatically returns to its previous status (in_progress or backlog). Does not delete the linked resolver goal if one exists.

Input parameters:

- `blockerId` (string, required): UUID блокера
- `goalId` (string, required): UUID цели

### `goal-todo` (~142 tokens)

Quick-capture a task or improvement idea into a project. Creates a backlog task with priority 4 (low) and auto-adds the "suggestion" tag. Resolves project by slug (falls back to the default project). Lightweight alternative to goal-create when you need minimal ceremony.

Input parameters:

- `description` (string): Описание
- `priority` (integer): Приоритет 1–5 (default: 4)
- `project` (string): Slug проекта (если не указан — используется дефолтный)
- `tags` (array): Теги (автоматически добавляется "suggestion")
- `title` (string, required): Название задачи

### `goal-add-note` (~113 tokens)

Add a free-form note (markdown supported) to a goal — decisions taken, dead ends hit, context worth carrying into the next session. Notes are NOT evidence: they hang off the goal rather than an acceptance criterion and never count toward AC coverage or closing a Grove goal — use goal-attach-evidence for proof. Notes are visible in the goal detail panel and returned by goal-get under notes[].

Input parameters:

- `goalId` (string, required): UUID цели
- `text` (string, required): Текст заметки (markdown)

### `goal-remove-note` (~65 tokens)

Remove a note from a goal by note UUID. Note ids come from goal-get (notes[].id). Deletes only the note — never touches acceptance criteria, evidence or blockers.

Input parameters:

- `goalId` (string, required): UUID цели
- `noteId` (string, required): UUID заметки

### `goal-tree` (~94 tokens)

Fetch the full goal hierarchy as a nested tree. Optional filters: projectId (UUID) to scope to one project, rootId (UUID) to get a subtree. Each node includes id, title, status, priority, type, progress, and nested children array.

Input parameters:

- `projectId` (string): UUID проекта (по умолчанию: все проекты)
- `rootId` (string): UUID корня поддерева

### `goal-summary` (~57 tokens)

Aggregate statistics across all goals (or scoped to a projectId): total count, breakdown by status, root count, blocked count, and overdue count. Useful for daily standups and dashboard views.

Input parameters:

- `projectId` (string): UUID проекта

### `goal-add-criterion` (~148 tokens)

Append an acceptance criterion to a goal. The text must describe an observable check over an artifact (e.g. "GET /api/health returns 200 with {status:ok}"), not a subjective approval. Grove mode: AC can only be added while goal is in backlog (frozen once started), quality linter blocks high-severity issues. Standard mode: AC editable until goal is closed, linter is advisory. Returns criterion id, position, text, and any quality findings.

Input parameters:

- `goalId` (string, required): UUID цели
- `position` (integer): Позиция (default = append в конец)
- `text` (string, required): Формулировка критерия

### `goal-update-criterion` (~85 tokens)

Update the text of an acceptance criterion. Grove mode: only while goal is in backlog (frozen once started), quality linter blocks high-severity issues. Standard mode: until goal is done, linter is advisory. Returns updated criterion details and any quality findings.

Input parameters:

- `criterionId` (string, required): UUID acceptance criterion
- `text` (string, required): New criterion text

### `goal-remove-criterion` (~68 tokens)

Remove an acceptance criterion from a goal. Grove mode: only while goal is in backlog (frozen once started). Standard mode: until goal is done. Cascades to all evidence on the criterion. Returns confirmation with removed criterion details.

Input parameters:

- `criterionId` (string, required): UUID acceptance criterion

### `goal-attach-evidence` (~1219 tokens)

PRIMARY path to close a Grove goal: this is the ONLY tool that covers an acceptance criterion. Attach binary evidence (screenshot, log dump, API response, export) to an AC — call it once per criterion to satisfy the close gate. The subordinate goal-add-evidence-text only adds context for proofs with NO bytes (URLs to permanent external sources, manual repro descriptions) and does NOT cover an AC. Caption is optional but strongly recommended: state what the file captures and the reproduction conditions (URL/commit/session/inputs) so a third reviewer can reproduce.

⚠ PICK THE RIGHT TRANSPORT BEFORE YOU CALL THIS TOOL ⚠
• BEST for ANY file > ~1 KB raw — and the ONLY no-token path, so use it in a claude.ai / hosted-agent session that has no raw X-Auth-Token → call the sibling MCP tool `goal-request-upload` with this same criterionId. It returns a one-time {uploadUrl, expiresAt}; then stream the raw bytes with a single PUT: `curl -sS --fail --upload-file "/abs/path/to/file.png" "<uploadUrl>"` (optionally add -H "X-Content-Sha256: <hex sha256>" so corruption fails fast). No base64, no token — the signed ?t= ticket in the URL is the only credential, single-use, criterion-scoped. The PUT response is the same evidence JSON this tool returns.
• ALTERNATIVELY, if you DO have the raw X-Auth-Token in your shell → the `planner-attach.sh` helper (zero-install bash, binary-safe).
The MCP base64 path below is unreliable for non-trivial files: long string arguments get truncated or whitespace-corrupted on the agent side BEFORE the JSON-RPC request is sent. Measured 2026-05-20 on prod: a 4 KB PNG arrived at the server as 1874 decoded bytes (file_hash_mismatch); a 2 KB payload arrived with stray whitespace (failed base64_decode). The server itself accepts up to 25 MiB raw — the bottleneck is the agent-side serialisation of contentBase64, NOT the server.

planner-attach.sh COPY-PASTE RECIPE (replace 3 placeholders, run in your shell):
  curl -sS https://planner.monopoly-gold.com/api/c…

Input parameters:

- `caption` (string): Optional human-readable description, stored in evidence.payload
- `contentBase64` (string, required): File payload, base64-encoded (RFC 4648 §4 standard alphabet, padding optional)
- `contentSha256` (string): Hex-encoded SHA-256 of the raw bytes (before base64). When provided, the server recomputes the hash on the decoded payload and rejects with error=file_hash_mismatch if they diverge — primary defence…
- `createdBy` (string): Identifier of the uploading agent
- `criterionId` (string, required): UUID acceptance criterion the file will be evidence for
- `filename` (string, required): Original filename (used to derive MIME). Path components are stripped.
- `kind` (string): Optional evidence kind override. The only accepted value is `session_history` — marks this attachment as the goal-level «full Claude session transcript» artifact required by the close gate (I4-sessio…
- `mimeType` (string): MIME type — if omitted, derived from filename extension; must be in whitelist

### `goal-request-upload` (~347 tokens)

PREFERRED path to attach a LARGE binary evidence file (screenshot, log dump, PDF, session transcript — anything > ~1 KB) to an acceptance criterion. Returns a one-time {uploadUrl, expiresAt} scoped to this criterion. Then STREAM the raw file to it with a single PUT — no base64, no token:

  curl -sS --fail --upload-file "/abs/path/to/file.png" "<uploadUrl>"

Optionally pass the hex SHA-256 of the file so the server fast-fails on any in-flight corruption:
  curl -sS --fail -H "X-Content-Sha256: <sha256>" --upload-file "/abs/path/to/file.png" "<uploadUrl>"

The PUT response is the same evidence JSON that goal-attach-evidence returns (evidence id, serverSha256, judge verdict, criterion evidenceCount). A non-2xx PUT means the upload was rejected (expired/already-used/wrong-criterion/hash-mismatch) and NO evidence was created — request a fresh URL and retry.

Use this instead of goal-attach-evidence for any non-trivial file. Use goal-add-evidence-text only for byte-less context (external URLs, manual repro notes) — it does NOT cover an AC.

Input parameters:

- `caption` (string): Optional human-readable description, stored on the evidence
- `createdBy` (string): Identifier of the uploading agent
- `criterionId` (string, required): UUID acceptance criterion the file will be evidence for
- `kind` (string): Optional evidence kind override. Only accepted value is `session_history` (goal-level transcript artifact; does NOT cover an AC).

### `goal-add-evidence-text` (~199 tokens)

SUBORDINATE / supplementary path — does NOT close an acceptance criterion. Adds a text-only note (URL to a permanent external source like CI run / GitHub commit / issue, or a description of a manual scenario) as extra context alongside the real proof. The path that actually covers an AC and closes a Grove goal is goal-attach-evidence — use that one for every criterion. Plain evidence NEVER counts toward AC coverage no matter how many you add; it is only a complement to an attached file. NOT for bytes — screenshots, logs, API responses, exports all go through goal-attach-evidence. NOT for filesystem paths — those need goal-attach-evidence with the actual file.

Input parameters:

- `createdBy` (string): Identifier of the uploading agent
- `criterionId` (string, required): UUID acceptance criterion
- `text` (string, required): Text payload: URL to a permanent external source or a description of a manual scenario

### `goal-remove-evidence` (~59 tokens)

Delete an evidence record by UUID. Forbidden if the owning goal is already done (evidence is frozen after close). Removes both the database record and the attached file (if any).

Input parameters:

- `evidenceId` (string, required): UUID evidence-записи

### `goal-add-assumption` (~149 tokens)

Add an assumption to a goal edge (parent→this goal). An assumption is an explicit premise: "why does completing this goal contribute to the parent?" Requires the goal to have a parent (root goals have no edge). Text must pass quality linter (testable, precise, discrete, signposted). Type (cause_effect/causal_link) is auto-classified by LLM.

Input parameters:

- `goalId` (string, required): UUID цели (ребёнка — assumption живёт на ребре parent→child)
- `signpost` (string): Наблюдаемый индикатор провала (опционально)
- `text` (string, required): Формулировка допущения

### `goal-update-assumption` (~72 tokens)

Update text or signpost of an assumption. Status cannot be changed manually — transitions happen only via evidence judge verdicts.

Input parameters:

- `assumptionId` (string, required): UUID допущения
- `signpost` (string): Новый индикатор провала
- `text` (string): Новый текст допущения

### `goal-remove-assumption` (~30 tokens)

Remove an assumption from a goal edge.

Input parameters:

- `assumptionId` (string, required): UUID допущения

### `goal-suggest-assumptions` (~69 tokens)

LLM generates suggested assumptions for a goal edge (parent→child). Returns 2-4 assumptions with signposts and type classification. Author should review, edit, and accept relevant ones via goal-add-assumption.

Input parameters:

- `goalId` (string, required): UUID цели (ребёнка)

### `goal-attach-assumption-evidence` (~125 tokens)

Attach text evidence to an assumption and judge it. The judge evaluates whether the evidence supports or challenges the assumption and automatically transitions its status: supports → supported, first challenges → challenged, second (repeat) challenges → invalidated. Invalidated is terminal — further evidence no longer moves the status. Judge infra failures fail open (errored verdict, no status change).

Input parameters:

- `assumptionId` (string, required): UUID допущения
- `text` (string, required): Текст evidence — наблюдение/данные, подтверждающие или опровергающие допущение

### `goal-request-ac-change` (~123 tokens)

Request a change to an acceptance criterion that appears unreachable. Requires ≥3 failed evidence attempts (weak/mismatch) with 0 matches. An LLM judge evaluates the reason for substantiality. On pass, creates an escalation for the goal owner to resolve (edit AC text, split to sub-goal, drop AC without creating a child, or reject). Grove mode only, goal must be in_progress.

Input parameters:

- `criterionId` (string, required): UUID of the acceptance criterion to escalate
- `reason` (string, required): Structured justification: what is unreachable and what was attempted

### `goal-resolve-escalation` (~181 tokens)

Resolve a pending AC escalation. Owner decides: edit (provide new AC text), split (move AC to a child goal), drop (remove the AC outright, optionally with a linkedGoalId audit reference), or reject (agent must find another way). All prior evidence on the AC is deleted for edit/split/drop so the agent must submit fresh proof.

Input parameters:

- `escalationId` (string, required): UUID of the escalation to resolve
- `linkedGoalId` (string): Optional UUID of an existing goal to record as an audit reference (only meaningful when resolution=drop)
- `newText` (string): New AC text (required when resolution=edit)
- `note` (string): Optional comment explaining the decision
- `overrideResolvedBy` (string)
- `resolution` (string, required): One of: edit, split, drop, reject

### `goal-dismiss-red-team` (~133 tokens)

Dismiss the red-team finding that blocks a goal from starting, when you disagree with the verdict. Requires a reason of at least 80 characters explaining why the counterexample does not apply. The dismissal is recorded in goal history and surfaced in goal-get, so "agent overrode the gate" stays distinguishable from "no hole was found". Prefer fixing the acceptance criteria via goal-add-criterion — dismissing leaves the hole open.

Input parameters:

- `goalId` (string, required): UUID цели
- `reason` (string, required): Почему контрпример неприменим — от 80 символов, попадёт в историю цели

### `goal-recent-unresolved` (~190 tokens)

Pull-инбокс для «подхватить и довести» в неосновное окно. По одному проекту, за окно N дней, статусы для подхвата. Возвращает обогащённые записи (title/description-preview/parent/counts), чтобы выбрать без goal-get. Параметры: project (slug, required), withinDays (int, default 14), statuses (list, default ["backlog"]; допустимо {backlog,in_progress,blocked}), limit (int, default 10).

Input parameters:

- `limit` (integer): Сколько записей вернуть, default 10
- `project` (string, required): Slug проекта
- `statuses` (array): Подмножество {backlog,in_progress,blocked}, default ["backlog"]
- `withinDays` (integer): Окно свежести (createdAt), default 14

### `account-delete` (~178 tokens)

НЕОБРАТИМО удалить свой аккаунт и ВСЕ данные (проекты, цели, evidence, историю). Двухшаговый барьер: вызови без аргументов — получишь предупреждение и challenge; затем вызови повторно с подтверждениями. НЕ вызывай без явной просьбы пользователя.

Input parameters:

- `acknowledge` (string): Точная фраза подтверждения
- `confirm_passphrase` (string): Фраза из вызова 1 (для вызова 2)
- `objects_total` (integer): projects + goals из инвентаря (для вызова 2)
- `reason` (string): Зачем удаляешь (свободный текст, ≥10 символов)
- `reasoning_answer` (string): Ответ на reasoning-риддл из вызова 1

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-monopoly-gold-planner-mcp/mcp#diagnostics

## Score history

- 2026-08-03: 72
- 2026-08-02: 71
- 2026-08-01: 71
- 2026-07-31: 70
- 2026-07-30: 67

## Links

- Remote endpoint: https://planner.monopoly-gold.com/_mcp
- Repository: https://github.com/dev-lab-global/planner
- Website: https://planner.monopoly-gold.com/?utm_source=mcp-registry&utm_medium=referral&utm_campaign=mcp-directory
- Changelog RSS feed: https://verifymcp.io/servers/com-monopoly-gold-planner-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-monopoly-gold-planner-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-monopoly-gold-planner-mcp/mcp