{"version":"2.1.268","anchor":"mcpb-and-plugin-mcp-config-load-errors-now-redact-urlspaths","canonical_anchor":"mcpb-and-plugin-mcp-config-load-errors-now-redact-urlspaths","heading":"MCPB and plugin MCP-config load errors now redact URLs\/paths before logging","tier":"internal","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/mcpb-and-plugin-mcp-config-load-errors-now-redact-urlspaths","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### MCPB and plugin MCP-config load errors now redact URLs\/paths before logging\n\nMCPB and plugin MCP-config loading errors now redact URLs and file paths before logging them\n\n**What**\n\nAcross several places that load MCPB packages and plugin MCP configuration, such as downloading an MCPB package, checking a modification-time cache, resolving a directory-loaded plugin's source, and loading `.mcp.json`, raw URLs and file paths that end up in log or error messages are now passed through a redaction helper first, and diffs are formatted through a separate helper. For example, a log line now reads `Downloading MCPB from ${mf(e)}` instead of including the raw URL directly.\n\n**Why**\n\nThis keeps potentially sensitive URLs and file paths out of logs and error output when something goes wrong loading MCPB packages or plugin MCP configuration.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}