What Matters
REMOTE · MATTERS.BLACKDOGRANCH.COM · SCANNED AUG 14
Your personal action-item list — what you owe and what you're owed. AI proposes; you approve.
Available components
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. How we score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · matters.blackdogranch.com
claude mcp add --transport http com-blackdogranch-what-matters https://matters.blackdogranch.com/mcp
[mcp_servers.com-blackdogranch-what-matters] url = "https://matters.blackdogranch.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-blackdogranch-what-matters": {
"type": "remote",
"url": "https://matters.blackdogranch.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-blackdogranch-what-matters --url https://matters.blackdogranch.com/mcp --transport streamable-http
mcp_servers:
com-blackdogranch-what-matters:
url: "https://matters.blackdogranch.com/mcp" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 14 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Aug 26 +40
- 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. security
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 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 functional
- 12 Aug 26 36
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 14 Aug 2026 · Probed https://matters.blackdogranch.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=blackdogranch.com | CN=WE1,O=Google Trust Services,C=US | 6 Aug 2026 | 4 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 42ff91498339d50413d65c5737c9d22e |
| SANs: blackdogranch.com, matters.blackdogranch.com, *.matters.blackdogranch.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of matters.blackdogranch.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| blackdogranch.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="what-matters", resource_metadata="https://matters.blackdogranch.com/.well-known/oauth-protected-resource/mcp"
Bearer realm="what-matters", resource_metadata="https://matters.blackdogranch.com/.well-known/oauth-protected-resource/mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=2592000 |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Document | https://matters.blackdogranch.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Problem | metadata_incomplete |
| Resource | https://matters.blackdogranch.com/mcp |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://matters.blackdogranch.com/mcp | Verified | 200 | |
| http (plaintext) | http://matters.blackdogranch.com/mcp | HTTPS enforced | 301 | https://matters.blackdogranch.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
add_item ~527
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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 | yes | The thing to do. |
No output schema declared.
No examples provided.
complete_item ~38
Mark an item done, or reopen it. Idempotent.
| Name | Type | Req | Description |
|---|---|---|---|
| done | boolean | – | Default true. |
| item_id | string | yes | – |
No output schema declared.
No examples provided.
get_document ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
manage_focus ~180
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.
| Name | Type | Req | Description |
|---|---|---|---|
| terms | array | yes | The complete list, in the order the user wants to see it. An empty array clears it. |
No output schema declared.
No examples provided.
manage_rule ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| operation | string | yes | – |
| patch | object | – | Fields to change, for update. |
| rule | object | – | Required for create. |
| rule_id | string | – | Required for update, pause, resume and delete. |
No output schema declared.
No examples provided.
put_proposal ~209
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.