# Darylmcd Roslyn Backed MCP MCP Server Stress > Darylmcd Roslyn Backed Mcp Mcp Server Stress - Skill: `tomevault-io/darylmcd-roslyn-backed-mcp-mcp-server-stress` (Agent Skill, multi-file: 2 files) - Install (CLI): `npx skillmds@latest add tomevault-io/darylmcd-roslyn-backed-mcp-mcp-server-stress` - Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/darylmcd-roslyn-backed-mcp-mcp-server-stress/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: tomevault-io (https://skillmd.com/u/tomevault-io) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/tomevault-io/darylmcd-roslyn-backed-mcp-mcp-server-stress --- # /mcp-server-stress $ARGUMENTS Maintainer-only repo-local alias for `/mcp-server-surface-test --output-mode=fragments`. Routes to the canonical audit prompt at `${CLAUDE_PLUGIN_ROOT}/skills/mcp-server-surface-test/prompts/full.md` with fragments-mode emission so findings produce `/backlog.d/.md` files for the `/backlog-intake` pipeline. ## What this skill does Invoke `/mcp-server-surface-test --output-mode=fragments` against the current Claude Code session's repo root (the only path the Roslyn MCP server's sanctioned-root restriction permits — see *Limitations* below). Forward any additional flags (`--no-worktree`, `--single-agent`, `--quick`) verbatim. ## Why this skill exists (and why it's a thin alias) Before v1.X.Y, `/mcp-server-stress` used a separate `maintainer-overlay.md` prompt that duplicated ~85% of `full.md` while adding three repo-coupled phases (backlog.d/ fragment emission, ai_docs/audit-reports/ report path, ai_docs/backlog.md regression cross-check). Every prompt fix had to be applied to both files, and they drifted in subtle ways. The v1.X.Y refactor folded the maintainer-overlay's unique content into `full.md` behind: - `--output-mode=fragments` → Phase 19 emits backlog.d/ fragments (the maintainer-overlay's Phase 19 behavior). - Auto-detection of `ai_docs/audit-reports/` vs `audit-reports/` → reports land in the maintainer's doc-audit schema location when that schema exists, top-level otherwise. - Auto-detection of `ai_docs/backlog.md` vs `backlog.md` for regression source → Phase 18's "prior source" probe handles both. `/mcp-server-stress` survives as a 1-line alias because: 1. **Muscle memory.** The maintainer types `/mcp-server-stress` reflexively; renaming to `/mcp-server-surface-test --output-mode=fragments` everywhere is friction. 2. **Repo-local discoverability.** This skill is only available from Claude Code sessions rooted in Roslyn-Backed-MCP (per `.claude/skills/` discovery). The repo-local placement signals that fragments-mode is the maintainer-standard invocation. ## Invocation The skill body delegates entirely to `/mcp-server-surface-test`. The agent should: 1. Read `${CLAUDE_PLUGIN_ROOT}/skills/mcp-server-surface-test/SKILL.md` for the canonical preconditions, flag handling, and prompt-execution flow. 2. Execute that skill with `--output-mode=fragments` prepended to any `$ARGUMENTS` the operator passed. 3. The audited repo is the current Claude Code session's repo root (no `--target=` — see *Limitations*). Functionally equivalent to typing `/mcp-server-surface-test --output-mode=fragments $ARGUMENTS`. ## Limitations - **No cross-repo `--target=` flag.** The Roslyn MCP server's `workspace_load` refuses any path outside the Claude Code client's sanctioned root, which is fixed at session-start time to the directory Claude Code was opened in. To audit a different repo, **open Claude Code in that repo** and invoke `/mcp-server-surface-test --output-mode=fragments` from that session (the skill is plugin-shipped, so it's available from any repo). This is a structural limitation of the MCP root-sanction model; the cross-repo `--target=` invocation that the prior version of this skill advertised never actually worked end-to-end and has been removed. ## Hard rules (inherited from `/mcp-server-surface-test`) - **Server-required.** No generic non-MCP fallback exists. If `mcp__roslyn__server_info` is not callable or `connection.state` is not `ready`, halt. - **Read-only against `main`.** Phase 6 apply-mode mutations confine to the disposable worktree the prompt creates. Never push or merge from inside this skill. - **Mutation isolation contract.** Phase 7 / 8b / 13 writes target the disposable worktree only. Run-end primary-checkout `git status` MUST be empty (Phase 0 baseline + Final surface closure step 3a hard gate). - **No silent truncation.** Subagent phases that return `skipped-budget` / `skipped-context` / `truncated` markers are hard FAILs; orchestrator re-dispatches or records `phase-failed-budget` as P1. - **P0 / security findings never go to GitHub Issues** under findings mode. Under fragments mode, `area: security` triggers `/backlog-intake --publish`'s refusal contract when the fragment is later published. ## Exit annotation This skill is a thin alias and does not track its own semantic-call count. To verify that the underlying surface-test run made meaningful Roslyn tool calls, check the audit report's **tool-invocation section** (Phase 17 in `full.md`): it records the complete list of MCP tools called and their call counts for the session. If the tool-invocation section is absent or shows zero semantic calls (only infrastructure calls such as `workspace_load` / `server_info`), treat the run as potentially incomplete and re-invoke with an explicit `--single-agent` flag to reduce context-budget pressure. --- > Source: [darylmcd/Roslyn-Backed-MCP](https://github.com/darylmcd/Roslyn-Backed-MCP) — distributed by [TomeVault](https://tomevault.io).