mcp-registry/com.blackdogranch/what-matters · v1.0.0
As of 2026-10-25 10:26 UTC, the Blackdogranch What Matters MCP server is unknown with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks.
Your personal action-item list — what you owe and what you're owed. AI proposes; you approve.
Point your MCP client at this streamable-http endpoint: https://matters.blackdogranch.com/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →
2 tool definition(s) exceed ~1,200 tokens each (largest: put_proposal, ~5,155).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~5,249 tokens every session. How to fix →
6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
3 parameter(s) across 3 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. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~1,848 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. How to fix →
In the last 30 days: 0 tool(s) removed and 2 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.blackdogranch%2Fwhat-matters/fixes
{
"name": "add_item",
"description": "Add an item immediately, without review. Normally use this ONLY when the user has just asked for it in conversation — they are the human in the loop at that moment, so set initiated: \"human\". Anything found by scanning on a schedule belongs in put_proposal instead, with ONE exception: something genuinely urgent that cannot wait for review may be added with initiated: \"auto\" and priority: \"high\", which lands on the list at once. Nothing notifies the user. Reserve it for things that truly cannot w",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"title",
"section",
"initiated"
],
"properties": {
"due": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "YYYY-MM-DD."
},
"note": {
"type": "string",
"maxLength": 10000,
"description": "Prose context, markdown. A URL belongs in `links`, not here."
},
"links": {
"type": "array",
"items": {
"type": "object",
"required": [
"label",
"url"
],
"properties": {
"url": {
"type": "string",
"format": "uri",
"maxLength": 1000,
"description": "The full URL, http or https only. Up to 1000 characters."
},
"label": {
"type": "string",
"maxLength": 80,
"minLength": 1,
"description": "What to call it — \"the Teams thread\", \"the signed contract\". Never the raw URL."
}
}
},
"maxItems": 3,
"description": "Up to 3 named links — the thread, the document, the ticket. Prefer these over pasting a URL into the note."
},
"title": {
"type": "string",
"maxLength": 500,
"minLength": 1,
"description": "The thing to do."
},
"source": {
"type": "string",
"maxLength": 200,
"description": "Who it involves or where it came from — \"Dana\", \"Tuesday's standup\"."
},
"channel": {
"enum": [
"self",
"teams",
"email",
"meeting",
"other"
],
"type": "string",
"description": "Where it came from, which is what makes an item legible days later. self = the user thought of it themselves, no external trigger. teams = a Teams message or chat. email = an email thread. meeting = raised in or arising from a meeting. other = anywhere else. Describe the ORIGIN, not who added it — an item you add from an email is still email."
},
"flagged": {
"type": "boolean",
"description": "True marks the task as urgent — needing the user’s attention now. Set it only when the user asked for the flag, or something genuinely cannot wait; it changes no ordering and no due date."
},
"section": {
"enum": [
"action",
"waiting",
"note"
],
"type": "string",
"description": "Which list it belongs in. action = something the user owes someone or themselves. waiting = something owed TO them; they are blocked and the next move is not theirs. note = worth knowing, no action attached. Pick waiting over action whenever the ball is in someone else's court — the distinction is the whole point of the two lists."
},
"priority": {
"enum": [
"low",
"medium",
"high"
],
"type": "string"
},
"initiated": {
"enum": [
"human",
"auto"
],
"type": "string",
"description": "Who set this add in motion. \"human\" = the user asked for it in this conversation — whoever is talking to you, not one specific person. \"auto\" = you are adding it on your own initiative with no direct instruction. Be truthful: \"auto\" combined with priority \"high\" bypasses review."
},
"source_id": {
"type": "string",
"maxLength": 500,
"description": "The stable id of whatever this came from — a Teams message id, an Outlook internetMessageId, a calendar event id. Set it whenever you have one: it is how the app recognises the same thing again, across runs and after rewording."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "get_document",
"description": "Read everything: action items, the record of what has already been dismissed, and \"focus\" — the handful of terms the user says matter most. Always call this before proposing changes: it is the only way to know what was already deleted or rejected, and re-suggesting those is the main failure mode.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"properties": {
"include_rules": {
"type": "boolean",
"description": "Include the standing rules. Default true. Read them: the server drops any suggestion an active rule excludes, so proposing one is wasted effort."
},
"include_dismissed": {
"type": "boolean",
"description": "Include deleted items and previously rejected suggestions. Default true, and you almost always want it: this is how you avoid proposing something again."
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "put_proposal",
"description": "Replace the pending set of suggested changes. This is the ONLY write the scheduled run should make — nothing here reaches the list until the user reviews and accepts it. Replaces any previous proposal wholesale, so include everything still worth suggesting, up to 100 deltas.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"deltas"
],
"properties": {
"agent": {
"type": "string",
"maxLength": 40,
"minLength": 1,
"description": "Your name as the user knows you — \"Claude\" — shown as the review headline (\"Claude suggests some changes\"). Just the name: no model version, no \"AI\". Omit it and the screen says \"Your AI agent\"."
},
"deltas": {
"type": "array",
"items": {
"oneOf": [
{
"type": "object",
"required": [
"kind",
"item"
],
"properties": {
"item": {
"type": "object",
"required": [
"title",
"section"
],
"properties": {
"due": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "YYYY-MM-DD. Anything dated today or earlier surfaces in the Today section, so only set this when there is a real deadline — a speculative date drags it to the top."
},
"note": {
"type": "string",
"maxLength": 2000,
"description": "Optional detail or context, markdown. Leave empty unless it genuinely adds something. Up to 2000 characters — a paragraph or two, not a transcript."
},
"links": {
"type": "array",
"items": {
"type": "object",
"required": [
"label",
"url"
],
"properties": {
"url": {
"type": "string",
"format": "uri",
"maxLength": 1000,
"description": "The full URL, http or https only. Up to 1000 characters."
},
"label": {
"type": "string",
"maxLength": 80,
"minLength": 1,
"description": "What to call it — \"the Teams thread\", \"the signed contract\". Never the raw URL."
}
}
},
"default": [],
"maxItems": 3,
"description": "Up to 3 named links — the thread, the document, the ticket. Prefer these over pasting a URL into the note: they render as buttons rather than as a wall of text."
},
"title": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "The thing to do, phrased as an action the user can act on. Prefer \"Reply to Dana about the audit dates\" over \"Dana email\". Keep it to one line — 200 characters at most, and anything approaching that belongs in the note instead."
},
"source": {
"type": "string",
"maxLength": 200,
"description": "Who it involves or where it came from — \"Dana\", \"You → Dana\", \"Tuesday's standup\". Free text: sometimes a person, sometimes an occasion."
},
"status": {
"enum": [
"open",
"done"
],
"type": "string",
"description": "open or done. Leave it out for anything the user still has to act on — which is almost always. Send \"done\" only when adding something that ALREADY happened and is worth keeping as a record."
},
"channel": {
"enum": [
"self",
"teams",
"email",
"meeting",
"other"
],
"type": "string",
"default": "self",
"description": "Where it came from, which is what makes an item legible days later. self = the user thought of it themselves, no external trigger. teams = a Teams message or chat. email = an email thread. meeting = raised in or arising from a meeting. other = anywhere else. Describe the ORIGIN, not who added it — an item you add from an email is still email."
},
"flagged": {
"type": "boolean",
"description": "True marks this task as urgent — needing the user’s attention now. The user toggles it in the app, and the daily briefing offers it on critical findings. It changes no ordering and no due date: a flag is attention, not a deadline. Set it only when something genuinely cannot wait; flag everything and it means nothing. Absent means not flagged."
},
"section": {
"enum": [
"action",
"waiting",
"note"
],
"type": "string",
"description": "Which list it belongs in. action = something the user owes someone or themselves. waiting = something owed TO them; they are blocked and the next move is not theirs. note = worth knowing, no action attached. Pick waiting over action whenever the ball is in someone else's court — the distinction is the whole point of the two lists."
},
"priority": {
"enum": [
"low",
"medium",
"high"
],
"type": "string",
"default": "medium",
"description": "How much this matters: low, medium or high. Defaults to medium — most things are medium, so use high only when someone is blocked or a real deadline is close, and low for things that genuinely can wait. Marking everything high makes the list useless."
},
"initiated": {
"enum": [
"human",
"auto"
],
"type": "string",
"description": "Only two values, and only for AI adds. \"human\" = the user asked for this item in conversation just now — any user, whoever is talking to the MCP server, not one specific person. \"auto\" = the AI added it on its own initiative, with no direct instruction. Absent on items the user typed into the app themselves."
},
"source_id": {
"type": "string",
"maxLength": 500,
"description": "The stable id of whatever this came from — a Teams message id, an Outlook internetMessageId, a calendar event id. Set it whenever you have one. It is how the app recognises the same thing again after you have reworded the title, which you are otherwise told to do."
}
}
},
"kind": {
"type": "string",
"const": "add"
},
"reason": {
"type": "string",
"maxLength": 500,
"description": "Why you are suggesting this, in one line. Shown next to the row when he reviews it, so it is what he judges the suggestion on — \"She has asked twice and the second went unanswered\" beats \"found in email\"."
}
},
"description": "Suggest a new item the user does not have yet."
},
{
"type": "object",
"required": [
"kind",
"item_id"
],
"properties": {
"kind": {
"type": "string",
"const": "complete"
},
"reason": {
"type": "string",
"maxLength": 500,
"description": "Why you are suggesting this, in one line. Shown next to the row when he reviews it, so it is what he judges the suggestion on — \"She has asked twice and the second went unanswered\" beats \"found in email\"."
},
"item_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "The \"id\" of an existing item, exactly as returned by get_document."
}
},
"description": "Suggest an item is already DONE — the meeting happened, the reply was sent. This is almost always what you want when something looks finished. It keeps the record that he completed it; use remove only when the item should never have been there."
},
{
"type": "object",
"required": [
"kind",
"item_id"
],
"properties": {
"kind": {
"type": "string",
"const": "remove"
},
"reason": {
"type": "string",
"maxLength": 500,
"description": "Why you are suggesting this, in one line. Shown next to the row when he reviews it, so it is what he judges the suggestion on — \"She has asked twice and the second went unanswered\" beats \"found in email\"."
},
"item_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "The \"id\" of an existing item, exactly as returned by get_document."
}
},
"description": "Suggest an item should be cleared without being done — a duplicate, or something that stopped being relevant. If it was actually finished, use complete instead."
},
{
"type": "object",
"required": [
"kind",
"item_id",
"patch"
],
"properties": {
"kind": {
"type": "string",
"const": "update"
},
"patch": {
"type": "object",
"properties": {
"due": {
"anyOf": [
{
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$"
},
{
"type": "null"
}
],
"description": "YYYY-MM-DD. Anything dated today or earlier surfaces at the top, so only set this when there is a real deadline — a speculative date drags it up. Omit to leave the due date alone; null clears it."
},
"note": {
"anyOf": [
{
"type": "string",
"maxLength": 2000
},
{
"type": "null"
}
],
"description": "Optional detail or context, markdown. Prose only — a URL belongs in `links`, not here. Up to 2000 characters. Omit to leave the note alone; null clears it."
},
"links": {
"type": "array",
"items": {
"type": "object",
"required": [
"label",
"url"
],
"properties": {
"url": {
"type": "string",
"format": "uri",
"maxLength": 1000,
"description": "The full URL, http or https only. Up to 1000 characters."
},
"label": {
"type": "string",
"maxLength": 80,
"minLength": 1,
"description": "What to call it — \"the Teams thread\", \"the signed contract\". Never the raw URL."
}
}
},
"maxItems": 3,
"description": "Up to 3 named links — the thread, the document, the ticket. PUT URLS HERE, never pasted into the note: they render as buttons rather than a wall of text. Replaces the whole list, so include any existing links you want to keep. Omit to leave them alone."
},
"title": {
"type": "string",
"maxLength": 200,
"minLength": 1,
"description": "The thing to do, phrased as an action the user can act on. Prefer \"Reply to Dana about the audit dates\" over \"Dana email\". Keep it to one line — 200 characters at most, and anything approaching that belongs in the note instead."
},
"source": {
"anyOf": [
{
"type": "string",
"maxLength": 200
},
{
"type": "null"
}
],
"description": "Who it involves or where it came from — \"Dana\", \"You → Dana\", \"Tuesday's standup\". Omit to leave it alone; null clears it."
},
"channel": {
"enum": [
"self",
"teams",
"email",
"meeting",
"other"
],
"type": "string",
"description": "Where it came from, which is what makes an item legible days later. self = the user thought of it themselves, no external trigger. teams = a Teams message or chat. email = an email thread. meeting = raised in or arising from a meeting. other = anywhere else. Describe the ORIGIN, not who added it — an item you add from an email is still email."
},
"flagged": {
"type": "boolean",
"description": "True marks this task as urgent — needing the user’s attention now; false clears the flag. It changes no ordering and no due date: a flag is attention, not a deadline. Set true only when something genuinely cannot wait. Omit to leave the flag alone."
},
"section": {
"enum": [
"action",
"waiting",
"note"
],
"type": "string",
"description": "Which list it belongs in. action = something the user owes someone or themselves. waiting = something owed TO them; they are blocked and the next move is not theirs. note = worth knowing, no action attached. Pick waiting over action whenever the ball is in someone else's court — the distinction is the whole point of the two lists."
},
"priority": {
"enum": [
"low",
"medium",
"high"
],
"type": "string",
"description": "How much this matters: low, medium or high. Use high only when someone is blocked or a real deadline is close, and low for things that genuinely can wait. Marking everything high makes the list useless. Omit to leave the current priority alone."
}
}
},
"reason": {
"type": "string",
"maxLength": 500,
"description": "Why you are suggesting this, in one line. Shown next to the row when he reviews it, so it is what he judges the suggestion on — \"She has asked twice and the second went unanswered\" beats \"found in email\"."
},
"item_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "The \"id\" of an existing item, exactly as returned by get_document."
}
},
"description": "Suggest changing fields on an existing item — a slipped due date, a better title. Include only the fields that change; anything omitted is left alone."
},
{
"type": "object",
"required": [
"kind",
"rule"
],
"properties": {
"kind": {
"type": "string",
"const": "add_rule"
},
"rule": {
"type": "object",
"required": [
"action",
"match",
"reason",
"origin"
],
"properties": {
"match": {
"type": "object",
"required": [
"conditions"
],
"properties": {
"op": {
"enum": [
"all",
"any"
],
"type": "string",
"default": "all"
},
"conditions": {
"type": "array",
"items": {
"type": "object",
"required": [
"field",
"op",
"value"
],
"properties": {
"op": {
"enum": [
"equals",
"not_equals",
"contains"
],
"type": "string"
},
"field": {
"enum": [
"section",
"channel",
"source",
"title",
"priority",
"due_relative"
],
"type": "string"
},
"value": {
"type": "array",
"items": {
"type": "string",
"maxLength": 200
},
"maxItems": 20,
"minItems": 1
}
}
},
"maxItems": 10,
"minItems": 1
}
}
},
"action": {
"enum": [
"exclude",
"recategorize",
"always_keep",
"boost"
],
"type": "string"
},
"origin": {
"type": "object",
"required": [
"from"
],
"properties": {
"from": {
"enum": [
"rejections",
"manual"
],
"type": "string"
},
"count": {
"type": "integer",
"default": 0,
"maximum": 9007199254740991,
"minimum": 0
},
"rejection_ids": {
"type": "array",
"items": {
"type": "string"
},
"default": [],
"maxItems": 50
}
}
},
"params": {
"type": "object",
"default": {},
"properties": {
"channel": {
"enum": [
"self",
"teams",
"email",
"meeting",
"other"
],
"type": "string",
"description": "Where it came from, which is what makes an item legible days later. self = the user thought of it themselves, no external trigger. teams = a Teams message or chat. email = an email thread. meeting = raised in or arising from a meeting. other = anywhere else. Describe the ORIGIN, not who added it — an item you add from an email is still email."
},
"section": {
"enum": [
"action",
"waiting",
"note"
],
"type": "string",
"description": "Which list it belongs in. action = something the user owes someone or themselves. waiting = something owed TO them; they are blocked and the next move is not theirs. note = worth knowing, no action attached. Pick waiting over action whenever the ball is in someone else's court — the distinction is the whole point of the two lists."
},
"priority": {
"enum": [
"low",
"medium",
"high"
],
"type": "string"
}
}
},
"reason": {
"type": "string",
"maxLength": 300,
"minLength": 1,
"description": "Why this rule exists, in the user's terms. Shown next to it on the rules page."
},
"status": {
"enum": [
"active",
"paused"
],
"type": "string"
}
}
},
"reason": {
"type": "string",
"maxLength": 500,
"description": "Why you are suggesting this, in one line. Shown next to the row when he reviews it, so it is what he judges the suggestion on — \"She has asked twice and the second went unanswered\" beats \"found in email\"."
}
},
"description": "Suggest a standing rule, mined from a pattern in the rejections list. Only when 3 or more rejections share a trait and no active rule already covers it — one rejection is never a pattern. Never auto-applied: it does nothing until the user accepts it."
},
{
"type": "object",
"required": [
"kind",
"rule_id",
"patch"
],
"properties": {
"kind": {
"type": "string",
"const": "update_rule"
},
"patch": {
"type": "object",
"properties": {
"match": {
"type": "object",
"required": [
"conditions"
],
"properties": {
"op": {
"enum": [
"all",
"any"
],
"type": "string",
"default": "all"
},
"conditions": {
"type": "array",
"items": {
"type": "object",
"required": [
"field",
"op",
"value"
],
"properties": {
"op": {
"enum": [
"equals",
"not_equals",
"contains"
],
"type": "string"
},
"field": {
"enum": [
"section",
"channel",
"source",
"title",
"priority",
"due_relative"
],
"type": "string"
},
"value": {
"type": "array",
"items": {
"type": "string",
"maxLength": 200
},
"maxItems": 20,
"minItems": 1
}
}
},
"maxItems": 10,
"minItems": 1
}
}
},
"action": {
"enum": [
"exclude",
"recategorize",
"always_keep",
"boost"
],
"type": "string"
},
"params": {
"type": "object",
"properties": {
"channel": {
"enum": [
"self",
"teams",
"email",
"meeting",
"other"
],
"type": "string",
"description": "Where it came from, which is what makes an item legible days later. self = the user thought of it themselves, no external trigger. teams = a Teams message or chat. email = an email thread. meeting = raised in or arising from a meeting. other = anywhere else. Describe the ORIGIN, not who added it — an item you add from an email is still email."
},
"section": {
"enum": [
"action",
"waiting",
"note"
],
"type": "string",
"description": "Which list it belongs in. action = something the user owes someone or themselves. waiting = something owed TO them; they are blocked and the next move is not theirs. note = worth knowing, no action attached. Pick waiting over action whenever the ball is in someone else's court — the distinction is the whole point of the two lists."
},
"priority": {
"enum": [
"low",
"medium",
"high"
],
"type": "string"
}
}
},
"reason": {
"type": "string",
"maxLength": 300,
"minLength": 1,
"description": "Why this rule exists, in the user's terms. Shown next to it on the rules page."
},
"status": {
"enum": [
"active",
"paused"
],
"type": "string"
}
}
},
"reason": {
"type": "string",
"maxLength": 500,
"description": "Why you are suggesting this, in one line. Shown next to the row when he reviews it, so it is what he judges the suggestion on — \"She has asked twice and the second went unanswered\" beats \"found in email\"."
},
"rule_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "The \"id\" of an existing item, exactly as returned by get_document."
}
},
"description": "Suggest changing an existing rule — usually to narrow one that is too broad."
},
{
"type": "object",
"required": [
"kind",
"rule_id"
],
"properties": {
"kind": {
"type": "string",
"const": "remove_rule"
},
"reason": {
"type": "string",
"maxLength": 500,
"description": "Why you are suggesting this, in one line. Shown next to the row when he reviews it, so it is what he judges the suggestion on — \"She has asked twice and the second went unanswered\" beats \"found in email\"."
},
"rule_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "The \"id\" of an existing item, exactly as returned by get_document."
}
},
"description": "Suggest deleting a rule outright."
},
{
"type": "object",
"required": [
"kind",
"rule_id"
],
"properties": {
"kind": {
"type": "string",
"const": "pause_rule"
},
"reason": {
"type": "string",
"maxLength": 500,
"description": "Why you are suggesting this, in one line. Shown next to the row when he reviews it, so it is what he judges the suggestion on — \"She has asked twice and the second went unanswered\" beats \"found in email\"."
},
"rule_id": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
"description": "The \"id\" of an existing item, exactly as returned by get_document."
}
},
"description": "Suggest pausing a rule, leaving it in the list so it can be resumed."
}
]
},
"description": "The proposed changes — add, complete, remove or update, plus the rule kinds. At most 100: send the ones that matter most and let the rest wait for the next run, because a review too long to finish gets dismissed whole. An empty array clears the proposal. Prefer complete over remove for anything that actually got done."
},
"summary": {
"type": "string",
"maxLength": 1000,
"description": "One line on what this pass looked at."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": 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.blackdogranch/what-matters"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.blackdogranch/what-matters"}) over MCP.
put_proposal ~5,155 tokensmanage_rule ~1,294 tokensadd_item ~951 tokensget_document ~236 tokensmanage_focus ~227 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.blackdogranch%2Fwhat-matters?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.blackdogranch%2Fwhat-matters?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.blackdogranch%2Fwhat-matters.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.blackdogranch%2Fwhat-matters.svg :target: https://glimind.com/server/mcp-registry%2Fcom.blackdogranch%2Fwhat-matters?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:65585679de65c7bd…, first seen 2026-10-17, included at leaf 2557 of 75,141. Version history · verify what your client received.
Compare: most reliable productivity servers · most reliable knowledge 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-25 10:26 UTC, the Blackdogranch What Matters MCP server is unknown with a Glimind reliability score of 84/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks.
Blackdogranch What Matters MCP server advertises 6 tools, including add_item, complete_item, get_document, manage_focus, manage_rule.
Point your MCP client at this streamable-http endpoint: https://matters.blackdogranch.com/mcp
Glimind scanned all 6 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.