com.blackdogranch/what-matters

MCPcommunitylive
v1.0.0com.blackdogranchUnknownUpdated 1mo ago

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

Endpoint healthlive
checked 11 days ago · 427ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Package
Authorcom.blackdogranch
LicenseUnknown
Version1.0.0
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: this listing has no repository on file, so `forge publish` cannot verify ownership automatically. Use "Claim this listing" above — Forge reviews these by hand.
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface6 tools · none privileged
Security scan✓ Cleanvlive · 11d agoHow well does this scan work?
EvalsNone
IndexedAug 12, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

6 tools · none privileged
Observed live from the vendor's endpoint11d ago

Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.

  • https://matters.blackdogranch.com/mcp6 tools · 427ms
get_documentRead 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.

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.

ParameterTypeDescription
include_dismissedbooleanInclude deleted items and previously rejected suggestions. Default true, and you almost always want it: this is how you avoid proposing something again.
include_rulesbooleanInclude the standing rules. Default true. Read them: the server drops any suggestion an active rule excludes, so proposing one is wasted effort.
put_proposalReplace 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.

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.

ParameterTypeDescription
agentstringYour 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 ver…
summarystringOne line on what this pass looked at.
deltas*arrayThe 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…
manage_ruleCreate, 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.

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.

ParameterTypeDescription
operation*string—
ruleobjectRequired for create.
rule_idstringRequired for update, pause, resume and delete.
patchobjectFields to change, for update.
manage_focusReplace 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…

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…

ParameterTypeDescription
terms*arrayThe complete list, in the order the user wants to see it. An empty array clears it.
add_itemAdd 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 gen…

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 gen…

ParameterTypeDescription
title*stringThe thing to do.
notestringProse context, markdown. A URL belongs in `links`, not here.
section*stringWhich 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 t…
channelstringWhere 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 c…
sourcestringWho it involves or where it came from — "Dana", "Tuesday's standup".
duestringYYYY-MM-DD.
source_idstringThe 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 a…
linksarrayUp to 3 named links — the thread, the document, the ticket. Prefer these over pasting a URL into the note.
prioritystring—
flaggedbooleanTrue 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…
initiated*stringWho 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…
complete_itemMark an item done, or reopen it. Idempotent.

Mark an item done, or reopen it. Idempotent.

ParameterTypeDescription
item_id*string—
donebooleanDefault true.

6 of 6 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

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

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.