<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on William Collins</title><link>https://wcollins.io/tags/security/</link><description>Recent content in Security on William Collins</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 William Collins</copyright><lastBuildDate>Wed, 22 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wcollins.io/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Your MCP Config Is Leaking Secrets</title><link>https://wcollins.io/posts/2026/your-mcp-config-is-leaking-secrets/</link><pubDate>Wed, 22 Apr 2026 00:00:00 +0000</pubDate><guid>https://wcollins.io/posts/2026/your-mcp-config-is-leaking-secrets/</guid><description>&lt;p&gt;Open up the &lt;code&gt;claude_desktop_config.json&lt;/code&gt; or &lt;code&gt;mcp.json&lt;/code&gt; of the average AI tinkerer right now and tell me you don&amp;rsquo;t flinch. API keys sitting in plaintext. GitHub PATs with repo scope pasted next to a GitLab token that somebody will forget about in six months. A Slack bot token that absolutely should not be in a file backed up to iCloud. We collectively spent a decade teaching engineers not to do this - and then MCP showed up and everybody speed-ran the mistake all over again.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://wcollins.io/posts/2026/your-mcp-config-is-leaking-secrets/featured.png"/></item></channel></rss>