Your personal action-item list — what you owe and what you're owed. AI proposes; you approve.
Déduit des transports déclarés par cette annonce (streamable-http). Un client absent de cette liste n’est pas écarté pour autant — c’est simplement quelque chose que Forge ne peut pas confirmer.
La vérification confirme l’identité de l’éditeur (la propriété du dépôt), pas la sûreté du code. L’analyse de sécurité couvre les CVE connues et les scripts d’installation suspects.
Lu depuis un véritable échange MCP initialize → tools/list contre l’endpoint déclaré. Aucun outil n’a été invoqué — tools/list est l’appel d’introspection en lecture seule que le protocole prévoit pour cela. Cela reflète ce que le serveur annonçait à cet instant ; un endpoint hébergé n’est figé sur aucune version et peut changer sans préavis.
https://matters.blackdogranch.com/mcp6 outils · 427 msget_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.
| Paramètre | Type | 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. |
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.
| Paramètre | Type | 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 ver… |
| summary | string | One line on what this pass looked at. |
| deltas* | array | 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… |
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.
| Paramètre | Type | Description |
|---|---|---|
| operation* | string | — |
| rule | object | Required for create. |
| rule_id | string | Required for update, pause, resume and delete. |
| patch | object | Fields 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…
| Paramètre | Type | Description |
|---|---|---|
| terms* | array | The 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…
| Paramètre | Type | Description |
|---|---|---|
| title* | string | The thing to do. |
| note | string | Prose context, markdown. A URL belongs in `links`, not here. |
| section* | string | 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 t… |
| 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 c… |
| source | string | Who it involves or where it came from — "Dana", "Tuesday's standup". |
| due | string | YYYY-MM-DD. |
| 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 a… |
| links | array | Up to 3 named links — the thread, the document, the ticket. Prefer these over pasting a URL into the note. |
| priority | string | — |
| flagged | boolean | 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… |
| initiated* | string | 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… |
complete_itemMark an item done, or reopen it. Idempotent.Mark an item done, or reopen it. Idempotent.
| Paramètre | Type | Description |
|---|---|---|
| item_id* | string | — |
| done | boolean | Default true. |
6 outils sur 6 ont publié une description.
Les noms et descriptions d’outils sont écrits par l’éditeur et affichés tels quels, comme du texte inerte. Ce sont les chaînes qu’un client MCP transmet à un modèle, alors Forge y recherche des motifs d’injection de prompt — tout constat apparaît avec l’analyse de sécurité ci-dessus. « Privilégié » est une correspondance de mot-clé sur le nom de l’outil, pas un audit de ce qu’il fait : un nom anodin peut tout de même tout faire.
Your personal action-item list — what you owe and what you're owed. AI proposes; you approve.
Les noms cliquables ouvrent l’index Forge de toutes les entrées observées exposant cet outil. Parcourir tous les outils indexés.
Cette entrée ne publie aucun paquet npm : Forge n'a donc pas d'arbre de dépendances pour elle. C'est une lacune de couverture — pas une affirmation qu'elle n'a aucune dépendance.