discovery-source-tracker

Étoiles9

Forks1

Mis à jour19 mai 2026 à 16:19

Implement discovery-source attribution tracking for MCP tool enumeration by creating a dedicated tracker interface with first-writer-wins semantics, recording at discovery call sites (not in the doctor/reporter), and wiring both in-process and OOP paths to agree on provenance. WHEN: the doctor or a reporting surface infers tool source heuristically, adding source attribution to a new discovery path, or aligning in-process and OOP discovery provenance.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

usepowershell

usepowershell/PoshMcp

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	discovery-source-tracker
description	Implement discovery-source attribution tracking for MCP tool enumeration by creating a dedicated tracker interface with first-writer-wins semantics, recording at discovery call sites (not in the doctor/reporter), and wiring both in-process and OOP paths to agree on provenance. WHEN: the doctor or a reporting surface infers tool source heuristically, adding source attribution to a new discovery path, or aligning in-process and OOP discovery provenance.
domain	api-design
confidence	high
source	earned

Context

Use this when a doctor/reporting surface needs authoritative provenance for discovered tools, but the existing implementation is inferring source after the fact. It is especially useful when both in-process and out-of-process discovery paths must agree byte-for-byte.

Patterns

Create a dedicated tracker interface that matches the existing provenance seam shape (RecordToolSource(...), snapshot property, first-writer-wins semantics).
Populate the tracker at the discovery call sites, not in the doctor/reporting consumer.
In-process: record during the existing Get-Command enumeration loops so no extra probes are added.
Out-of-process: read the wire-format Source* fields directly and translate missing fields to unknown rather than inferring.
Make the doctor/reporting consumer depend on the tracker and treat missing entries as unknown.

Examples

PoshMcp.Server/PowerShell/IToolImportSourceTracker.cs
PoshMcp.Server/McpToolFactoryV2.cs
PoshMcp.Server/Diagnostics/DoctorService.cs
PoshMcp.Tests/Integration/ToolImportParityTests.cs

Anti-Patterns

Re-running discovery commands inside doctor/report generation just to recover provenance.
Keeping an old heuristic alive once authoritative data is available.
Treating older OOP hosts as if they had authoritative source data.

Plus depuis ce dépôt

même dépôt

skill-name

usepowershell/PoshMcp

{what this skill teaches agents}

2026-07-179

cli-bool-flag-pattern

usepowershell/PoshMcp

Add boolean configuration flags to the update-config CLI command using TryParseRequiredBoolean() for argument parsing and GetOrCreateObject() for JSON section navigation, following the three-step flow and nesting conventions established across PRs #85, #86, and #92. WHEN: adding a new --flag to update-config, nesting a config value under a JSON section, or writing unit tests for CLI config flag parsing.

2026-05-199

cli-config-resolution

usepowershell/PoshMcp

Resolve configuration file paths in CLI commands using the same shared pipeline as the doctor/diagnostics so all commands target the same effective config file. WHEN: adding a new CLI command that reads or writes config, debugging a command that mutates a different config file than doctor reports, or implementing config-aware CLI behavior in a multi-location config environment.

2026-05-199

mcp-entra-oauth

usepowershell/PoshMcp

Implement OAuth 2.1 + Entra ID authentication for an MCP server using a lightweight AS metadata proxy — handling RFC 9728 protected resource metadata, RFC 8414 AS metadata, and a /register endpoint that eliminates client_id prompts for all MCP clients. WHEN: adding OAuth to an MCP server, MCP clients ask users to paste a client_id, authorization redirects go to the wrong endpoint, or debugging Entra DCR limitations.

2026-05-199

nuget-github-packages

usepowershell/PoshMcp

Publish .NET NuGet packages to GitHub Packages using GitHub PAT authentication — covering gh auth token retrieval, write:packages scope verification, dotnet pack/push workflow, and owner resolution from git remote. WHEN: publishing a NuGet package to GitHub Packages, debugging 401 on dotnet nuget push, adding a GitHub Packages NuGet source, or resolving write:packages scope errors.

2026-05-199

oop-wire-format-extension

usepowershell/PoshMcp

Extend the PoshMcp OOP discover wire format (RemoteToolSchema + parallel payload) safely without breaking backward compatibility with older OOP hosts or C# servers. WHEN: adding new fields to OOP discover responses, threading per-command metadata across the JSON-RPC boundary, or adding new top-level optional payload objects to the discover response.

2026-05-199