<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Model-Context-Protocol on AegisGate — Secure Every AI Interaction</title><link>https://aegisgatesecurity.io/tags/model-context-protocol/</link><description>Recent content in Model-Context-Protocol on AegisGate — Secure Every AI Interaction</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 08 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aegisgatesecurity.io/tags/model-context-protocol/feed.xml" rel="self" type="application/rss+xml"/><item><title>We Needed a Secure MCP Server. There Wasn't One. So We Built One.</title><link>https://aegisgatesecurity.io/blog/we-needed-a-secure-mcp-server-there-wasnt-one-so-we-built-one/</link><pubDate>Thu, 08 Oct 2026 00:00:00 +0000</pubDate><guid>https://aegisgatesecurity.io/blog/we-needed-a-secure-mcp-server-there-wasnt-one-so-we-built-one/</guid><description>The Model Context Protocol (MCP) is becoming the standard way AI models interact with external tools, data sources, and services. Claude Desktop uses it. Cursor uses it. Windsurf uses it. The protocol is well-designed, actively developed, and gaining adoption.
It also ships with zero security.
MCP servers execute tool calls, access resources, and broker interactions between AI models and your infrastructure. The official SDK provides the protocol plumbing — transport handling, message routing, session management.</description></item></channel></rss>