{"version":"2.1.317","anchor":"sdk-mcp-server-urlhost-description-narrowed","canonical_anchor":"sdk-mcp-server-urlhost-description-narrowed","heading":"MCP server host name is now withheld on self-hosted runners","tier":"notice","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/sdk-mcp-server-urlhost-description-narrowed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### MCP server host name is now withheld on self-hosted runners\n\nReports about MCP servers in the SDK now leave out the server's host name unless the worker is known to be hosted by Anthropic\n\n**Unclear.** Only the field's description is known to have changed, so it is not clear whether the host name is actually withheld in practice.\n\n**What**\n\nThe Claude Code SDK lets programs use Claude Code. When the SDK reports on an MCP server, which is an outside program that gives Claude extra tools, it can include the server's host name. The description of that field now says it is left out outside a worker known to be hosted by Anthropic, when configuration is withheld. It gives the reason: a self-hosted runner, meaning a machine you run yourself, could reveal the name of a machine on a customer's network.\n\n**Why**\n\nHost names from your own network are not meant to be exposed when Claude Code runs on a self-hosted runner.\n\n- Area: Self-Hosted Runners\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}