<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mcp-Go on Project Wintermute</title><link>https://wintermutecore.com/tags/mcp-go/</link><description>Recent content in Mcp-Go on Project Wintermute</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 08 Nov 2026 14:22:43 +0000</lastBuildDate><atom:link href="https://wintermutecore.com/tags/mcp-go/index.xml" rel="self" type="application/rss+xml"/><item><title>mcp-go tightens request capabilities and JSON handling</title><link>https://wintermutecore.com/posts/mcp-go-request-capabilities-json-replay-fixes/</link><pubDate>Sun, 08 Nov 2026 14:22:43 +0000</pubDate><guid>https://wintermutecore.com/posts/mcp-go-request-capabilities-json-replay-fixes/</guid><description>&lt;p&gt;&lt;a href="https://github.com/mark3labs/mcp-go"&gt;mcp-go&lt;/a&gt; is a Go library for Model Context Protocol clients and servers. Its activity on November 2 and 3 adds request specific capability declarations and fixes how tool results and replayed events travel through the library. For engineers exposing catalog queries or ingestion controls through MCP, these changes deserve attention because they affect the contract between a caller and a data service.&lt;/p&gt;</description></item></channel></rss>