org.agile-today/agile-today

Est-ce que org.agile-today/agile-today est sûr ?

Au dernier audit MCP Hub, le serveur MCP « org.agile-today/agile-today » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 8 outils

• check_gate≈ 1410 tokens

  Evaluates gate g.g0 … g.g10 against your evidence. Outcome precedence: Stop > Recycle > Hold > Conditional go > Go, with the rule that fired (outcome_reason). Critical evidence missing or stale → Hold; required non-critical missing, or a waiver without a reason or an approver who decides at this gate → Conditional go; a waiver with both → Go with the Waiver modifier (under regulation a waived critical artifact stays Conditional go until the deviation is recorded with the quality approval); optional gaps are notes. Modifiers: Work started without the gate, Overdue, Stale, Waiver. gate.deciders decide, gate.advisors take part. A disproved key product hypothesis is a Recycle, not a Stop: pass earlier_stage_invalid:true with invalid_stage:'st.discovery'. At G8 (go / no-go), work_started_beyond:true means production was changed before the decision: Hold (R3), not a Go with a modifier. Call without evidence to list what the gate needs. Returns a receipt hash of the inputs.

  Paramètres, retour & exemple (12)

  Paramètres

  • gate · string · requis
    Gate id, e.g. g.g5
  • lang · string · optionnel · en | ru
    Answer language, default en
  • context · object · optionnel
    Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data.
  • evidence · object · optionnel
    Map artifact id → state or {state, reason, ref, by, date}. A waiver is {state:'waived', reason, by}: by is the role id of a decider of this gate (see gate.deciders, e.g. r.client_owner) or 'name, role'. Unknown ids are reported as warnings with a suggestion.
  • grace_days · number · optionnel
    Overrides both limits. Default: 80% of planned_stage_days, else by approach (predictive/hybrid 10, agile/flow 5); required evidence then waits twice as long
  • days_in_stage · number · optionnel
  • invalid_stage · string · optionnel
    With earlier_stage_invalid: the stage to return to, if known
  • invalid_artifact · string · optionnel
    With earlier_stage_invalid: the artifact that is no longer true, to find where to return
  • planned_stage_days · number · optionnel
    Planned length of the stage in days. With it, missing critical evidence is overdue after 80% of it and missing required evidence after all of it
  • business_case_valid · boolean · optionnel
    false → Stop
  • work_started_beyond · boolean · optionnel
    True if work of later stages already started (adds the 'work started without the gate' modifier; at G8 it is a Hold)
  • earlier_stage_invalid · boolean · optionnel
    true → Recycle; the answer names the stage to return to

  Exemple d'appel

  {"name": "check_gate", "arguments": {"gate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• check_mix≈ 771 tokens

  For a set of ids: antipatterns in the set and detected by rules, conflicts, redundant alternatives (e.g. seven estimation methods), items to avoid or not applicable here, risks, missing inputs and suggested additions. ok = no antipatterns, conflicts, avoid or not-applicable items; a detected pattern of severity warning (e.g. output over outcome on a client contract) does not change ok.

  Paramètres, retour & exemple (3)

  Paramètres

  • ids · array · requis
  • lang · string · optionnel · en | ru
    Answer language, default en
  • context · object · optionnel
    Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data.

  Exemple d'appel

  {"name": "check_mix", "arguments": {"ids": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• explain_node≈ 210 tokens

  One node with its description, conditions, source, level and its links grouped by type, each with a link id (Lxxxx) to cite. Filter with link_types, direction and limit.

  Paramètres, retour & exemple (5)

  Paramètres

  • id · string · requis
  • lang · string · optionnel · en | ru
    Answer language, default en
  • limit · integer · optionnel
  • direction · string · optionnel · in | out | both
  • link_types · array · optionnel

  Exemple d'appel

  {"name": "explain_node", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_context≈ 150 tokens

  Call first. Returns the context dimensions and flags (with defaults and how many rules each flag drives), stages, gates, evidence states and levels, the gate outcome precedence and the suggested workflow.

  Paramètres, retour & exemple (1)

  Paramètres

  • lang · string · optionnel · en | ru
    Answer language, default en

  Exemple d'appel

  {"name": "list_context", "arguments": {"lang": "en"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• plan_project≈ 899 tokens

  Route from presale to closure for a project context. Default is compact (ids by strength + a names dictionary, core items and gate evidence for all stages, about 6–10k characters). Ask for one stage with stages:['st.design'] and format:'full' for reasons, avoid texts and gate details. 'core' = do it here (context rule, flag or gate-critical artifact), at most 8 work items per stage (producers of the gate's critical artifacts first, then context rules, then flags).

  Paramètres, retour & exemple (6)

  Paramètres

  • lang · string · optionnel · en | ru
    Answer language, default en
  • format · string · optionnel · compact | full
    Default compact
  • stages · array · optionnel
    Stage ids or codes, e.g. ['st.analysis','design']. Default: all
  • context · object · optionnel
    Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data.
  • include · array · optionnel
    Default all four
  • min_strength · string · optionnel · core | recommended | all
    Default: core for all stages, all when stages are given

  Exemple d'appel

  {"name": "plan_project", "arguments": {"lang": "en", "format": "compact", "stages": [], "context": {}, "include": [], "min_strength": "core"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_graph≈ 210 tokens

  Search names, ids, descriptions and aliases in English and Russian (word stems, small typos tolerated). Returns total and the best matches.

  Paramètres, retour & exemple (4)

  Paramètres

  • lang · string · optionnel · en | ru
    Answer language, default en
  • type · string · optionnel · school | stage | gate | scenario | stream | event | practice | technique
  • limit · integer · optionnel
  • query · string · requis

  Exemple d'appel

  {"name": "search_graph", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• validate_plan≈ 903 tokens

  Checks an ordered list of steps (stages, gates, events, practices, techniques, notations, artifacts). Errors: empty plan, unknown ids, non-step types, stage order (analysis and design work planned early is only a warning 'early'; building before G3–G5 is an order error), contract after delivery gates, a gate after the step it authorises (G8 after the cutover), antipatterns, avoid or not-applicable items. Warnings: duplicates, redundant alternatives, early work, a cutover with no G8 or go / no-go meeting before it, antipatterns of severity warning. 'Shadow start' looks at the order: G4 or G5 must come before the first build step. 'expected' lists gate evidence not yet produced by earlier steps.

  Paramètres, retour & exemple (4)

  Paramètres

  • lang · string · optionnel · en | ru
    Answer language, default en
  • steps · array · requis
  • context · object · optionnel
    Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data.
  • evidence · object · optionnel
    Artifacts that already exist

  Exemple d'appel

  {"name": "validate_plan", "arguments": {"steps": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• when_to_use≈ 736 tokens

  For one event, practice, technique, notation, tool, artifact or antipattern: does it fit this context (fits / avoid / not_applicable / antipattern), its strength and why, alternatives and their group advice, risks, and which gates require it.

  Paramètres, retour & exemple (3)

  Paramètres

  • id · string · requis
    e.g. t.planning_poker, p.stage_gating, x.velocity_kpi
  • lang · string · optionnel · en | ru
    Answer language, default en
  • context · object · optionnel
    Project context. Unknown keys and values are rejected in the answer envelope with did_you_mean. Defaults: software, hybrid, complicated, tm, single, medium size, ui, data.

  Exemple d'appel

  {"name": "when_to_use", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://agile-today.org/api/mcp?src=mcp-registry