com.monopoly-gold.planner/mcp

Est-ce que com.monopoly-gold.planner/mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.monopoly-gold.planner/mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 43 outils

• account-delete≈ 245 tokens

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

  Paramètres, retour & exemple (5)

  Paramètres

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

  Exemple d'appel

  {"name": "account-delete", "arguments": {"reason": "texte", "acknowledge": "texte", "objects_total": 1, "reasoning_answer": "texte", "confirm_passphrase": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-add-assumption≈ 208 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.

  Paramètres, retour & exemple (3)

  Paramètres

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

  Exemple d'appel

  {"name": "goal-add-assumption", "arguments": {"text": "texte", "goalId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-add-criterion≈ 825 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. Each criterion has a class: pre-merge (default — proved in CI / by attached evidence) or post-deploy (proved by an executable probe against the deployed prod instance). A post-deploy criterion MUST carry probeSpec {method, url, expect:{http_code, body:{field: expectedValue}}} — the request the runner sends and the answer it must get; without it the call is rejected with error=probe_required. Passing probeSpec alone implies probeClass=post-deploy. Set visualEvidenceSuggested=true only when adopting visualAcSuggestion from goal-create, goal-get, or the ready_for_work advisory returned by goal-update; it remains an ordinary AC. Grove mode: AC (class and probe included) can only be added while goal is in backlog, except accepting a visual advisory in ready_for_work: that starts a direct checking_ac recheck, without intermediate backlog. Other edits are 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, probeClass, probeSpec and any quality findings.

  Paramètres, retour & exemple (6)

  Paramètres

  • text · string · requis
    Формулировка критерия
  • goalId · string · requis
    UUID цели
  • position · integer · optionnel
    Позиция (default = append в конец)
  • probeSpec · ? · optionnel
    Исполнимая проба post-deploy критерия: {method: GET|HEAD|POST|PUT|PATCH|DELETE, url: абсолютный http(s), expect: {http_code: 200, body: {field: expectedValue, nested: {field: value}}}}. Ожидаемые значения фиксируются сейчас; единственная подстановка времени прогона — "{{deployed_revision}}" (SHA развёрнутой ревизии). Пример: {"method":"GET","url":"https://planner.monopoly-gold.com/api/healthz","expect":{"http_code":200,"body":{"status":"ok","revision":"{{deployed_revision}}"}}}
  • probeClass · string · optionnel · pre-merge | post-deploy | None
    Класс критерия: pre-merge (default; доказывается в CI / приложенным evidence) или post-deploy (доказывается исполнимой пробой против прода; требует probeSpec)
  • visualEvidenceSuggested · boolean · optionnel
    True only when this AC accepts Planner's visual-AC advisory

  Exemple d'appel

  {"name": "goal-add-criterion", "arguments": {"text": "texte", "goalId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-add-evidence-text≈ 297 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.

  Paramètres, retour & exemple (3)

  Paramètres

  • text · string · requis
    Text payload: URL to a permanent external source or a description of a manual scenario
  • createdBy · string · optionnel
    Identifier of the uploading agent
  • criterionId · string · requis
    UUID acceptance criterion

  Exemple d'appel

  {"name": "goal-add-evidence-text", "arguments": {"text": "texte", "criterionId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-add-note≈ 179 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[].

  Paramètres, retour & exemple (2)

  Paramètres

  • text · string · requis
    Текст заметки (markdown)
  • goalId · string · requis
    UUID цели

  Exemple d'appel

  {"name": "goal-add-note", "arguments": {"text": "texte", "goalId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-attach-assumption-evidence≈ 204 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).

  Paramètres, retour & exemple (2)

  Paramètres

  • text · string · requis
    Текст evidence — наблюдение/данные, подтверждающие или опровергающие допущение
  • assumptionId · string · requis
    UUID допущения

  Exemple d'appel

  {"name": "goal-attach-assumption-evidence", "arguments": {"text": "texte", "assumptionId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-attach-evidence≈ 1426 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/cli/planner-attach.sh \ | PLANNER_TOKEN="<same X-Auth-Token you use for MCP>" bash -s -- \ --criterion-id "<CRITERION_UUID>" \ --file "/abs/path/to/file.png" \ --caption "what is captured and the repro conditions" \ --created-by "<your agent id>" Where to get each value: - PLANNER_TOKEN: the very same token that is already in your MCP config under the X-Auth-Token header for the `planner` server. NOT a separate credential. - CRITERION_UUID: the AC id you got from goal-get / goal-list. Same UUID you would pass to this MCP tool. - file path: absolute path on YOUR (agent) machine — the script reads it locally and streams multipart. The planner server never sees your filesystem. The helper computes SHA-256 itself and ships it as `contentSha256`, so any in-flight corruption fails fast with HTTP 400 instead of poisoning the evidence row. Output on stdout is the same JSON shape this MCP tool returns; non-zero exit means HTTP ≥ 400 (stderr explains). Without curl/bash? Fall back to raw multipart: POST https://planner.monopoly-gold.com/api/criteria/<id>/evidence/file, header X-Auth-Token, form fields file=@..., contentSha256=..., caption, createdBy. • File ≤ ~1 KB raw → this MCP tool is fine. ALWAYS pass `contentSha256` (hex SHA-256 of raw bytes BEFORE base64). Without it, a silently truncated PNG looks valid to the MIME sniffer; the server cannot distinguish a truncated 4 KB PNG from a valid 1 KB one and the vision judge burns ~30s on broken bytes. With the hash, the server fast-fails with error=file_hash_mismatch and points back here at the multipart endpoint. Validates MIME whitelist (png/jpeg/webp/gif/mp4/pdf/txt/json/zip), per-file size cap (ATTACHMENTS_MAX_FILE_BYTES, default 25 MiB), per-project attachments quota. Returns evidence record + file URL + serverSha256.

  Paramètres, retour & exemple (8)

  Paramètres

  • kind · string · optionnel
    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-session-history). Such evidence does NOT cover any AC and is NOT sent to the evidence judge. Omit for normal per-AC proof (kind is derived from MIME). NOTE: transcripts are usually > 1 KB → use goal-request-upload (pass kind=session_history) or the multipart helper, not this base64 path.
  • caption · string · optionnel
    Optional human-readable description, stored in evidence.payload
  • filename · string · requis
    Original filename (used to derive MIME). Path components are stripped.
  • mimeType · string · optionnel
    MIME type — if omitted, derived from filename extension; must be in whitelist
  • createdBy · string · optionnel
    Identifier of the uploading agent
  • criterionId · string · requis
    UUID acceptance criterion the file will be evidence for
  • contentBase64 · string · requis
    File payload, base64-encoded (RFC 4648 §4 standard alphabet, padding optional)
  • contentSha256 · string · optionnel
    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 against MCP base64 truncation.

  Exemple d'appel

  {"name": "goal-attach-evidence", "arguments": {"filename": "texte", "criterionId": "texte", "contentBase64": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-attach-file≈ 425 tokens

  Attach a small file (mockup, diagram, screenshot, PDF) to a GOAL as a description attachment — NOT evidence: it is not bound to any acceptance criterion, is never judged and never counts toward closing the goal. Returns {attachment.url, attachment.markdown}; paste `markdown` into the goal description (goal-update description) and the web UI renders images inline. contentBase64 is reliable only for payloads ≤ ~1 KB (long string arguments get truncated on the agent side before the request is sent). For anything bigger call goal-request-upload with goalId and stream the file with a single PUT — same result shape, no base64.

  Paramètres, retour & exemple (7)

  Paramètres

  • goalId · string · requis
    UUID of the goal the file illustrates
  • caption · string · optionnel
    Optional alt-text / caption used in the markdown fragment
  • filename · string · requis
    Original file name (basename only; used for download + markdown alt)
  • mimeType · string · optionnel
    Optional MIME hint; server sniffs bytes when omitted or not whitelisted
  • createdBy · string · optionnel
    Identifier of the uploading agent
  • contentBase64 · string · requis
    File bytes, standard base64 (RFC 4648). Tiny files only — see description.
  • contentSha256 · string · optionnel
    Optional hex sha256 of the raw bytes — server fails fast on transport corruption

  Exemple d'appel

  {"name": "goal-attach-file", "arguments": {"goalId": "texte", "filename": "texte", "contentBase64": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-block≈ 305 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.

  Paramètres, retour & exemple (6)

  Paramètres

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

  Exemple d'appel

  {"name": "goal-block", "arguments": {"goalId": "texte", "description": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-create≈ 634 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 ready_for_work, 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. For an explicit visible UI result, the response may include an advisory visualAcSuggestion; adopt its criterion through goal-add-criterion with visualEvidenceSuggested=true, or ignore it. Every goal must belong to a project (pass projectId or inherit from parent).

  Paramètres, retour & exemple (12)

  Paramètres

  • mode · string · optionnel
    Режим: grove (default) или standard. Grove enforce-ит I_start на ready_for_work и I₃ на done; standard несёт те же AC, но без evidence-гейта
  • tags · array · optionnel
    Теги
  • type · string · optionnel
    goal / milestone / task / habit (default: task)
  • title · string · requis
    Название цели (макс. 500)
  • status · string · optionnel
    backlog (default) / ready_for_work (объявить контракт готовым; grove в проекте с обязательным red-team объявляется только через goal-update)
  • deadline · string · optionnel
    Дедлайн ISO 8601
  • estimate · string · optionnel
    Оценка
  • parentId · string · optionnel
    UUID родителя (null = root)
  • priority · integer · optionnel
    Приоритет 1–5 (default: 3)
  • projectId · string · optionnel
    UUID проекта
  • description · string · optionnel
    Описание
  • acceptanceCriteria · array · optionnel
    Список AC: строка (pre-merge критерий) или объект {text, probeClass?: pre-merge|post-deploy, probeSpec?}. post-deploy критерий обязан нести исполнимую пробу probeSpec {method, url, expect:{http_code, body:{field: expectedValue}}} — иначе error=probe_required; probeSpec без probeClass = post-deploy. Grove: опциональны на create, обязательны до объявления ready_for_work, блокирующий quality-линтер. Standard: описательные, линтер advisory

  Exemple d'appel

  {"name": "goal-create", "arguments": {"title": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-delete≈ 135 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • goalId · string · requis
    UUID цели

  Exemple d'appel

  {"name": "goal-delete", "arguments": {"goalId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-dismiss-red-team≈ 204 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.

  Paramètres, retour & exemple (2)

  Paramètres

  • goalId · string · requis
    UUID цели
  • reason · string · requis
    Почему контрпример неприменим — от 80 символов, попадёт в историю цели

  Exemple d'appel

  {"name": "goal-dismiss-red-team", "arguments": {"goalId": "texte", "reason": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-get≈ 145 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. For a Planner goal URL, do not browse the UI: extract the UUID after /goal/ and pass it as required goalId.

  Paramètres, retour & exemple (1)

  Paramètres

  • goalId · string · requis
    UUID цели

  Exemple d'appel

  {"name": "goal-get", "arguments": {"goalId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-list≈ 295 tokens

  List goals with optional filters: projectId (UUID), status (backlog/checking_ac/checking_ac_failed/checking_ac_errored/ready_for_work/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.

  Paramètres, retour & exemple (5)

  Paramètres

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

  Exemple d'appel

  {"name": "goal-list", "arguments": {"type": "texte", "limit": 1, "status": "texte", "parentId": "texte", "projectId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-move≈ 207 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.

  Paramètres, retour & exemple (3)

  Paramètres

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

  Exemple d'appel

  {"name": "goal-move", "arguments": {"goalId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-read-evidence-content≈ 440 tokens

  Read attached evidence through MCP without changing its format. Pass evidenceId from goal-get. Text (text/plain, JSON, NDJSON) returns newline-preserving redacted lines; offset/limit are zero-based line pagination. Images return a native MCP image with original MIME and bytes. For a complete video, PDF, ZIP or other binary, binaryDelivery=link (default) returns a resource_link to the authenticated original download — no base64 and no conversion. If the client cannot open external links, binaryDelivery=base64 embeds the exact original bytes in a resource blob; this expands data by about 33% plus JSON overhead and can consume the client context window, so use it only when needed. byteOffset/byteLimit require binaryDelivery=base64. Text secrets are redacted; binary evidence is unmodified.

  Paramètres, retour & exemple (6)

  Paramètres

  • limit · integer · optionnel
    Number of whole lines to return (1–500)
  • offset · integer · optionnel
    Zero-based line offset
  • byteLimit · integer · optionnel
    Number of bytes to return for binary evidence; omit with byteOffset for the complete original
  • byteOffset · integer · optionnel
    Zero-based byte offset for binary evidence
  • evidenceId · string · requis
    UUID of file-backed evidence from goal-get
  • binaryDelivery · string · optionnel · link | base64
    Complete binary: link to the original (default), or base64 fallback for clients without external links

  Exemple d'appel

  {"name": "goal-read-evidence-content", "arguments": {"evidenceId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-recent-unresolved≈ 308 tokens

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

  Paramètres, retour & exemple (4)

  Paramètres

  • limit · integer · optionnel
    Сколько записей вернуть, default 10
  • project · string · requis
    Slug проекта
  • statuses · array · optionnel
    Подмножество {backlog,checking_ac,checking_ac_failed,checking_ac_errored,ready_for_work,in_progress,blocked}, default ["backlog"]
  • withinDays · integer · optionnel
    Окно свежести (createdAt), default 14

  Exemple d'appel

  {"name": "goal-recent-unresolved", "arguments": {"project": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-record-iteration-certificate≈ 496 tokens

  Record one completed LeanSolver iteration against the current tracked contract. Result artifact refs must resolve to existing evidence or goal_attachment rows owned by this goal. Rework iterations accept only registered finding IDs and require a separate judged evidence row as repeatCheckEvidenceId; Planner derives the repeat verdict server-side. Only certificates admitted here may affect the numeric implementation rework rate.

  Paramètres, retour & exemple (12)

  Paramètres

  • action · string · requis
    Action that changed the result
  • goalId · string · requis
    Goal UUID
  • outcome · string · requis
    Observable completed result
  • acVerdict · string · requis
    matches, weak, mismatch, or errored
  • reworkClass · string · requis
    implementation, contract, proof_only, or unknown
  • artifactRefs · array · requis
    Existing goal-owned evidence/goal_attachment refs
  • precondition · string · requis
    Observable state before the iteration
  • coverageDelta · array · optionnel
    Structured coverage change
  • afterFingerprint · string · requis
    Lowercase SHA-256 of the completed result
  • beforeFingerprint · string · optionnel
    Optional lowercase SHA-256 of the prior result
  • addressesFindingIds · array · optionnel
    Registered finding UUIDs addressed by this iteration
  • repeatCheckEvidenceId · string · optionnel
    Separate judged evidence UUID; mandatory when findings are addressed

  Exemple d'appel

  {"name": "goal-record-iteration-certificate", "arguments": {"action": "texte", "goalId": "texte", "outcome": "texte", "acVerdict": "texte", "reworkClass": "texte", "artifactRefs": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-register-iteration-finding≈ 264 tokens

  Register an immutable LeanSolver finding against the currently tracked goal contract. subjectRefs must be goal-scoped refs of kind goal, criterion, or assumption. Returns the server-generated finding id to pass later as addressesFindingId; rejects stale contract tracking.

  Paramètres, retour & exemple (5)

  Paramètres

  • kind · string · requis
    evidence_mismatch, red_team_hole, assumption_invalidated, acceptance_gap, or manual_checkpoint
  • goalId · string · requis
    Goal UUID
  • summary · string · requis
    Concise observable weakness or gap
  • sourceRefs · array · optionnel
    Optional immutable source refs (validated structurally; resolved by the certificate recorder)
  • subjectRefs · array · requis
    Goal-scoped subject refs

  Exemple d'appel

  {"name": "goal-register-iteration-finding", "arguments": {"kind": "texte", "goalId": "texte", "summary": "texte", "subjectRefs": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-remove-assumption≈ 76 tokens

  Remove an assumption from a goal edge.

  Paramètres, retour & exemple (1)

  Paramètres

  • assumptionId · string · requis
    UUID допущения

  Exemple d'appel

  {"name": "goal-remove-assumption", "arguments": {"assumptionId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-remove-blocker≈ 135 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.

  Paramètres, retour & exemple (2)

  Paramètres

  • goalId · string · requis
    UUID цели
  • blockerId · string · requis
    UUID блокера

  Exemple d'appel

  {"name": "goal-remove-blocker", "arguments": {"goalId": "texte", "blockerId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-remove-criterion≈ 135 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • criterionId · string · requis
    UUID acceptance criterion

  Exemple d'appel

  {"name": "goal-remove-criterion", "arguments": {"criterionId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-remove-evidence≈ 111 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).

  Paramètres, retour & exemple (1)

  Paramètres

  • evidenceId · string · requis
    UUID evidence-записи

  Exemple d'appel

  {"name": "goal-remove-evidence", "arguments": {"evidenceId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-remove-note≈ 126 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.

  Paramètres, retour & exemple (2)

  Paramètres

  • goalId · string · requis
    UUID цели
  • noteId · string · requis
    UUID заметки

  Exemple d'appel

  {"name": "goal-remove-note", "arguments": {"goalId": "texte", "noteId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-reorder≈ 140 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • ids · array · requis
    UUID целей в новом порядке (все должны иметь одного родителя и одинаковый priority)

  Exemple d'appel

  {"name": "goal-reorder", "arguments": {"ids": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-request-ac-change≈ 426 tokens

  Request a change to an acceptance criterion. grounds=unreachable (default): the AC cannot be proven — requires ≥3 failed evidence attempts (weak/mismatch) with 0 matches. grounds=wrong_criterion: the AC measures the wrong thing (owner never approved this wording, or a revealed fact shows it tracks something else) — no failed attempts required, but you MUST pass quotedFragment: a verbatim slice of the criterion text you claim is wrong (checked against the stored text), and the reason must name the unapproved wording or the finding; difficulty alone is rejected. An LLM judge screens the reason either way. 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.

  Paramètres, retour & exemple (4)

  Paramètres

  • reason · string · requis
    Structured justification. For unreachable: what is unreachable and what was attempted. For wrong_criterion: which wording/threshold the owner never approved, or what finding showed the criterion measures something else
  • grounds · string · optionnel
    Subject of the request: 'unreachable' (default) or 'wrong_criterion'
  • criterionId · string · requis
    UUID of the acceptance criterion to escalate
  • quotedFragment · string · optionnel
    Verbatim slice of the criterion text claimed to be wrong — required when grounds=wrong_criterion, ignored otherwise

  Exemple d'appel

  {"name": "goal-request-ac-change", "arguments": {"reason": "texte", "criterionId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-request-upload≈ 584 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. GOAL ATTACHMENTS (description illustrations, NOT evidence): pass goalId INSTEAD of criterionId. The PUT then creates a goal attachment and returns {attachment.url, attachment.markdown} — paste `markdown` into the goal description and the web UI renders images inline. Such a file is not bound to any AC and never counts toward closing the goal.

  Paramètres, retour & exemple (5)

  Paramètres

  • kind · string · optionnel
    Optional evidence kind override. Only accepted value is `session_history` (goal-level transcript artifact; does NOT cover an AC).
  • goalId · string · optionnel
    UUID of a goal — issues a ticket for a DESCRIPTION ATTACHMENT (not evidence); mutually exclusive with criterionId
  • caption · string · optionnel
    Optional human-readable description, stored on the evidence
  • createdBy · string · optionnel
    Identifier of the uploading agent
  • criterionId · string · optionnel
    UUID acceptance criterion the file will be evidence for (omit when goalId is given)

  Exemple d'appel

  {"name": "goal-request-upload", "arguments": {"kind": "texte", "goalId": "texte", "caption": "texte", "createdBy": "texte", "criterionId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-resolve-escalation≈ 291 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.

  Paramètres, retour & exemple (6)

  Paramètres

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

  Exemple d'appel

  {"name": "goal-resolve-escalation", "arguments": {"resolution": "texte", "escalationId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-start-iteration-tracking≈ 150 tokens

  Explicitly start LeanSolver iteration tracking for the goal contract currently stored by Planner. Planner computes the contract fingerprint server-side from title, description, acceptance criteria, and assumptions. Calling again without a contract change is idempotent; after a contract change it starts a new version while retaining old certificates as superseded history.

  Paramètres, retour & exemple (1)

  Paramètres

  • goalId · string · requis

  Exemple d'appel

  {"name": "goal-start-iteration-tracking", "arguments": {"goalId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-suggest-assumptions≈ 118 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • goalId · string · requis
    UUID цели (ребёнка)

  Exemple d'appel

  {"name": "goal-suggest-assumptions", "arguments": {"goalId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-summary≈ 102 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • projectId · string · optionnel
    UUID проекта

  Exemple d'appel

  {"name": "goal-summary", "arguments": {"projectId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-todo≈ 237 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.

  Paramètres, retour & exemple (5)

  Paramètres

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

  Exemple d'appel

  {"name": "goal-todo", "arguments": {"title": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-tree≈ 139 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.

  Paramètres, retour & exemple (2)

  Paramètres

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

  Exemple d'appel

  {"name": "goal-tree", "arguments": {"rootId": "texte", "projectId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-update≈ 780 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, attemptCommit (git SHA of the attempt commit; once a deployed revision contains it, post-deploy probes of this goal run automatically and record machine verdicts — pass "" to clear), dismissVisualAcSuggestion. Status transitions follow a matrix: backlog→ready_for_work (author; grove: requires ≥1 AC, red-team check when the project requires it — the goal parks in checking_ac and becomes ready_for_work, checking_ac_failed (hole in AC set) or checking_ac_errored (check did not run)); ready_for_work|checking_ac_errored→in_progress (executor, no checks); in_progress→done (file-evidence on every AC + session_history) | blocked | cancelled. A visible-UI goal with an outstanding visualAcSuggestion returns an advisory before ready_for_work freezes the AC contract: accept it through goal-add-criterion(visualEvidenceSuggested=true), or retry this same update with dismissVisualAcSuggestion=true. The first MCP dismissal persists the choice and notifies Product Events with the goal title and link, full proposed AC, and why screenshot proof was useful; UI, repeat, and no-active dismissals are silent, and notification failures do not undo the dismissal. backlog→in_progress and backlog→done are rejected. Returns the updated goal with all fields.

  Paramètres, retour & exemple (12)

  Paramètres

  • mode · string · optionnel
    Режим цели: standard или grove. Иммутабелен после mode_locked_at
  • tags · array · optionnel
    Новые теги
  • type · string · optionnel
    Новый тип: goal, milestone, task, habit
  • title · string · optionnel
    Новое название (макс. 500)
  • goalId · string · requis
    UUID цели
  • status · string · optionnel
    Новый статус: backlog, ready_for_work, in_progress, blocked, done, cancelled (checking_ac* выставляет система)
  • deadline · string · optionnel
    Новый дедлайн (ISO 8601)
  • estimate · string · optionnel
    Новая оценка
  • priority · integer · optionnel
    Новый приоритет (1–5)
  • description · string · optionnel
    Новое описание
  • attemptCommit · string · optionnel
    git SHA коммита попытки (7–64 hex). Когда развёрнутая ревизия содержит его (предок, не равенство), post-deploy пробы цели стартуют сами по событию деплоя; повторная установка = новая попытка (отметки доставки и пробы сбрасываются); "" снимает
  • dismissVisualAcSuggestion · boolean · optionnel
    Отклонить advisory visual-AC; для ready_for_work это явный выбор «продолжить без предложения»

  Exemple d'appel

  {"name": "goal-update", "arguments": {"goalId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-update-assumption≈ 143 tokens

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

  Paramètres, retour & exemple (3)

  Paramètres

  • text · string · optionnel
    Новый текст допущения
  • signpost · string · optionnel
    Новый индикатор провала
  • assumptionId · string · requis
    UUID допущения

  Exemple d'appel

  {"name": "goal-update-assumption", "arguments": {"assumptionId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• goal-update-criterion≈ 580 tokens

  Update an acceptance criterion: its text and/or its class + probe. probeClass=post-deploy requires an executable probeSpec {method, url, expect:{http_code, body}} (kept from the criterion when omitted and one already exists; otherwise error=probe_required); probeSpec alone implies post-deploy; probeClass=pre-merge drops the probe. 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 (text, probeClass, probeSpec) and any quality findings.

  Paramètres, retour & exemple (4)

  Paramètres

  • text · string · optionnel
    New criterion text (omit to keep)
  • probeSpec · ? · optionnel
    Исполнимая проба post-deploy критерия: {method, url, expect: {http_code, body: {field: expectedValue}}}; "{{deployed_revision}}" в ожидаемых значениях = SHA развёрнутой ревизии. Пример: {"method":"GET","url":"https://planner.monopoly-gold.com/api/healthz","expect":{"http_code":200,"body":{"status":"ok","revision":"{{deployed_revision}}"}}}
  • probeClass · string · optionnel · pre-merge | post-deploy | None
    Класс критерия: pre-merge (доказывается в CI / приложенным evidence; сбрасывает пробу) или post-deploy (доказывается исполнимой пробой против прода; требует probeSpec — свой или уже сохранённый)
  • criterionId · string · requis
    UUID acceptance criterion

  Exemple d'appel

  {"name": "goal-update-criterion", "arguments": {"criterionId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• project-add-dependency≈ 176 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.

  Paramètres, retour & exemple (2)

  Paramètres

  • projectId · string · requis
    UUID или slug проекта-зависимого
  • dependsOnProjectId · string · requis
    UUID или slug проекта, от которого зависит

  Exemple d'appel

  {"name": "project-add-dependency", "arguments": {"projectId": "texte", "dependsOnProjectId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• project-create≈ 396 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, sourceRef ({type:"git",url,ref} — remote-research source), isDefault. Returns the created project with id, slug, and webUrl. Slug must be unique — duplicates are rejected with existing slugs list.

  Paramètres, retour & exemple (10)

  Paramètres

  • icon · string · optionnel
    Иконка (эмодзи, макс. 10 символов)
  • slug · string · requis
    Уникальный slug (только a-z, 0-9, дефис)
  • tags · array · optionnel
    Теги
  • title · string · requis
    Название проекта
  • status · string · optionnel
    Статус: active / archived / paused (default: active)
  • isDefault · boolean · optionnel
    Сделать проектом по умолчанию
  • sourceRef · object · optionnel
    Источник кода для remote-research: {type:"git",url,ref}
  • description · string · optionnel
    Описание проекта
  • repositoryUrl · string · optionnel
    URL репозитория
  • repositoryPath · string · optionnel
    Путь к репозиторию на сервере

  Exemple d'appel

  {"name": "project-create", "arguments": {"slug": "texte", "title": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• project-delete≈ 153 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.

  Paramètres, retour & exemple (2)

  Paramètres

  • force · boolean · optionnel
    Удалить вместе со всеми целями (default: false — откажет если есть цели)
  • projectId · string · requis
    UUID проекта

  Exemple d'appel

  {"name": "project-delete", "arguments": {"projectId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• project-get≈ 123 tokens

  Fetch full project details: title, slug, status, description, icon, tags, repository info, sourceRef ({type,url,ref} for remote-research or null), goals breakdown by status (backlog/in_progress/blocked/done/cancelled counts), and depends_on list of project dependencies.

  Paramètres, retour & exemple (1)

  Paramètres

  • projectId · string · requis
    UUID проекта

  Exemple d'appel

  {"name": "project-get", "arguments": {"projectId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• project-list≈ 110 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • status · string · optionnel
    Статус: active / archived / paused

  Exemple d'appel

  {"name": "project-list", "arguments": {"status": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• project-remove-dependency≈ 190 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.

  Paramètres, retour & exemple (3)

  Paramètres

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

  Exemple d'appel

  {"name": "project-remove-dependency", "arguments": {"projectId": "texte", "dependencyId": "texte", "dependsOnProjectId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• project-update≈ 743 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, sourceRef ({type:"git",url,ref} — remote-research source), clearSourceRef (true → сбрасывает Project.sourceRef в null; несовместим с sourceRef), 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.

  Paramètres, retour & exemple (19)

  Paramètres

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

  Exemple d'appel

  {"name": "project-update", "arguments": {"projectId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://planner.monopoly-gold.com/_mcp