mcp-registry/com.monopoly-gold.planner/mcp · v2.1.1
As of 2026-10-17 10:42 UTC, the Monopoly Gold Planner MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 18 outages in 90 days, with a median recovery of 4 minutes.
Goal and task planning MCP for Codex and AI agents, with evidence-backed completion.
Claude Code
claude mcp add --transport http monopoly-gold-planner-mcp-server https://planner.monopoly-gold.com/_mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"monopoly-gold-planner-mcp-server": {
"type": "http",
"url": "https://planner.monopoly-gold.com/_mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
43 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter.
2 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays.
2 parameter(s) across 2 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.
Handshake + tools/list takes ~2,586 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.monopoly-gold.planner%2Fmcp/fixes
{
"name": "goal-add-criterion",
"description": "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 ",
"inputSchema": {
"type": "object",
"required": [
"goalId",
"text"
],
"properties": {
"text": {
"type": "string",
"description": "Формулировка критерия"
},
"goalId": {
"type": "string",
"description": "UUID цели"
},
"position": {
"type": "integer",
"default": null,
"description": "Позиция (default = append в конец)"
},
"probeSpec": {
"default": null,
"properties": {
"url": {
"type": "string",
"description": "Absolute http(s) URL the runner requests on the deployed instance"
},
"expect": {
"type": "object",
"properties": {
"body": {
"type": "object",
"additionalProperties": true
},
"http_code": {
"type": "integer",
"maximum": 599,
"minimum": 100
}
},
"description": "What the response must contain: http_code (exact) and/or body (subset of fields with expected scalar values; nested objects = nested fields; \"{{deployed_revision}}\" = SHA of the revision that triggered the probe)"
},
"method": {
"enum": [
"GET",
"HEAD"
],
"type": "string",
"description": "HTTP method of the probe request"
}
},
"description": "Исполнимая проба 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}}\"}}}",
"type": "string"
},
"probeClass": {
"enum": [
"pre-merge",
"post-deploy",
null
],
"type": "string",
"default": null,
"description": "Класс критерия: pre-merge (default; доказывается в CI / приложенным evidence) или post-deploy (доказывается исполнимой пробой против прода; требует probeSpec)"
},
"visualEvidenceSuggested": {
"type": "boolean",
"default": false,
"description": "True only when this AC accepts Planner's visual-AC advisory"
}
}
},
"annotations": {
"readOnlyHint": false,
"idempotentHint": false
}
}{
"name": "goal-update-criterion",
"description": "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. Ret",
"inputSchema": {
"type": "object",
"required": [
"criterionId"
],
"properties": {
"text": {
"type": "string",
"default": null,
"description": "New criterion text (omit to keep)"
},
"probeSpec": {
"default": null,
"properties": {
"url": {
"type": "string",
"description": "Absolute http(s) URL the runner requests on the deployed instance"
},
"expect": {
"type": "object",
"properties": {
"body": {
"type": "object",
"additionalProperties": true
},
"http_code": {
"type": "integer",
"maximum": 599,
"minimum": 100
}
},
"description": "What the response must contain: http_code (exact) and/or body (subset of fields with expected scalar values; nested objects = nested fields; \"{{deployed_revision}}\" = SHA of the revision that triggered the probe)"
},
"method": {
"enum": [
"GET",
"HEAD"
],
"type": "string",
"description": "HTTP method of the probe request"
}
},
"description": "Исполнимая проба 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}}\"}}}",
"type": "string"
},
"probeClass": {
"enum": [
"pre-merge",
"post-deploy",
null
],
"type": "string",
"default": null,
"description": "Класс критерия: pre-merge (доказывается в CI / приложенным evidence; сбрасывает пробу) или post-deploy (доказывается исполнимой пробой против прода; требует probeSpec — свой или уже сохранённый)"
},
"criterionId": {
"type": "string",
"description": "UUID acceptance criterion"
}
}
},
"annotations": {
"readOnlyHint": false,
"idempotentHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.monopoly-gold.planner/mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.monopoly-gold.planner/mcp"}) over MCP.
project-update ~709 tokensgoal-add-criterion ~664 tokensgoal-create ~625 tokensgoal-attach-evidence ~610 tokensgoal-update-criterion ~584 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.monopoly-gold.planner%2Fmcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.monopoly-gold.planner%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.monopoly-gold.planner%2Fmcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.monopoly-gold.planner%2Fmcp.svg :target: https://glimind.com/server/mcp-registry%2Fcom.monopoly-gold.planner%2Fmcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:f61dc34e7ee0b6de…, first seen 2026-10-17, included at leaf 6261 of 17,426. Version history · verify what your client received.
Compare: most reliable security servers · most reliable productivity servers · most reliable knowledge servers · most reliable files servers · most reliable retrieval servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-17 10:42 UTC, the Monopoly Gold Planner MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 18 outages in 90 days, with a median recovery of 4 minutes.
Monopoly Gold Planner MCP server advertises 43 tools, including account-delete, goal-add-assumption, goal-add-criterion, goal-add-evidence-text, goal-add-note.
Point your MCP client at this streamable-http endpoint: https://planner.monopoly-gold.com/_mcp
Glimind scanned all 43 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.