# What Matters (remote · matters.blackdogranch.com)

Your personal action-item list — what you owe and what you're owed. AI proposes; you approve.

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

## Components

- remote · `matters.blackdogranch.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-blackdogranch-what-matters/matters.md), [page](https://verifymcp.io/servers/com-blackdogranch-what-matters/matters)

## Channel facts

- Endpoint: `https://matters.blackdogranch.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-14.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1744 tokens (~249/item across 7 items; 6 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-blackdogranch-what-matters https://matters.blackdogranch.com/mcp
```

### Codex

```toml
[mcp_servers.com-blackdogranch-what-matters]
url = "https://matters.blackdogranch.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-blackdogranch-what-matters": {
      "type": "remote",
      "url": "https://matters.blackdogranch.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-blackdogranch-what-matters --url https://matters.blackdogranch.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-blackdogranch-what-matters:
    url: "https://matters.blackdogranch.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-blackdogranch-what-matters": {
      "type": "http",
      "url": "https://matters.blackdogranch.com/mcp"
    }
  }
}
```

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

## Changelog

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

### 2026-08-14 (score 76, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-13 (score 76, +40)

- [security improvement] Transport: unverified → pass
- [security] Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: excellent
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 86
- [functional] First check of Schema quality: fail

### 2026-08-12 (score 36)

First indexed and scored.

## MCP tools (6)

### `get_document` (~142 tokens)

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.

Input parameters:

- `include_dismissed` (boolean): Include deleted items and previously rejected suggestions. Default true, and you almost always want it: this is how you avoid proposing something again.
- `include_rules` (boolean): Include the standing rules. Default true. Read them: the server drops any suggestion an active rule excludes, so proposing one is wasted effort.

### `put_proposal` (~209 tokens)

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.

Input parameters:

- `agent` (string): Your name as the user knows you — "Claude" — shown as the review headline ("Claude suggests some changes") and in the notification. Just the name: no model version, no "AI". Omit it and the screen sa…
- `deltas` (array, required): 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 ge…
- `summary` (string): One line on what this pass looked at.

### `manage_rule` (~116 tokens)

Create, change, pause or delete a standing rule, taking effect IMMEDIATELY with no review. Use this only when the user asks you directly — "stop suggesting PTO stuff". A scheduled run must propose rules through put_proposal instead, exactly as it proposes items rather than calling add_item.

Input parameters:

- `operation` (string, required)
- `patch` (object): Fields to change, for update.
- `rule` (object): Required for create.
- `rule_id` (string): Required for update, pause, resume and delete.

### `manage_focus` (~180 tokens)

Replace the list of things the user says matter most — people, projects, whatever they care about. Send the WHOLE list every time, including the terms you are keeping: this replaces, it does not append, so omitting one deletes it. Read the current list from get_document first. Up to 10 terms of 60 characters; longer lists and longer terms are trimmed rather than refused, and the stored result comes back so you can see what landed. ONLY call this when the user asks you directly, in conversation. A scheduled run must never touch it: focus is the user saying what they care about, so a term they did not choose is worse than no term at all. Never infer one from their list.

Input parameters:

- `terms` (array, required): The complete list, in the order the user wants to see it. An empty array clears it.

### `add_item` (~527 tokens)

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 immediately notifies the user's phone. That interruption is the point — reserve it for things that truly cannot wait, because routine "urgent" adds teach the user to ignore the one signal that means look now.

Input parameters:

- `channel` (string): 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 =…
- `due` (string): YYYY-MM-DD.
- `initiated` (string, required): 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…
- `links` (array): Up to 3 named links — the thread, the document, the ticket. Prefer these over pasting a URL into the note.
- `note` (string): Prose context, markdown. A URL belongs in `links`, not here.
- `priority` (string)
- `section` (string, required): 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 a…
- `source` (string): Who it involves or where it came from — "Dana", "Tuesday's standup".
- `source_id` (string): 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, acro…
- `title` (string, required): The thing to do.

### `complete_item` (~38 tokens)

Mark an item done, or reopen it. Idempotent.

Input parameters:

- `done` (boolean): Default true.
- `item_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-blackdogranch-what-matters/matters#diagnostics

## Score history

- 2026-08-14: 76
- 2026-08-13: 76
- 2026-08-12: 36

## Links

- Remote endpoint: https://matters.blackdogranch.com/mcp
- Authorisation metadata: https://matters.blackdogranch.com/.well-known/oauth-protected-resource/mcp
- Website: https://matters.blackdogranch.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-blackdogranch-what-matters/matters.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-blackdogranch-what-matters/matters.json
- HTML version of this page: https://verifymcp.io/servers/com-blackdogranch-what-matters/matters