{"version":"2.1.269","anchor":"evalmocking-harness-gains-a-withheld-mock-server-concept","canonical_anchor":"evalmocking-harness-gains-a-withheld-mock-server-concept","heading":"Eval\/mocking harness gains a 'withheld' mock-server concept","tier":"internal","area":"Plugin Eval","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/evalmocking-harness-gains-a-withheld-mock-server-concept","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Eval\/mocking harness gains a 'withheld' mock-server concept\n\nEval mocking now supports 'withheld' mock servers that are excluded from without-server checks\n\n**What**\n\nThe evaluation and mocking system (used to test Claude Code against simulated MCP servers, which are external tools\/data sources Claude can connect to) now supports marking a mocked server as `withheld`. A related internal function filters out withheld servers before deciding whether a test case actually ran without a given server dependency.\n\n**Why**\n\nThis lets the eval harness distinguish a server that is deliberately left out of a test from one that's simply absent, so cases aren't miscounted as running \"without\" a server when that server was intentionally withheld.\n\n- Area: Plugin Eval\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}