<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Mcp on Pin Xiong</title>
    <link>https://xiongpin.dev/tags/mcp/</link>
    <description>Recent content in Mcp on Pin Xiong</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 Pin Xiong</copyright>
    <lastBuildDate>Sun, 01 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://xiongpin.dev/tags/mcp/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Two specialists, one orchestrator, one catalog</title>
      <link>https://xiongpin.dev/posts/agentcore-a2a-multi-agent-registry/</link>
      <pubDate>Sun, 01 Nov 2026 00:00:00 +0000</pubDate>
      
      <guid>https://xiongpin.dev/posts/agentcore-a2a-multi-agent-registry/</guid>
      <description>&lt;p&gt;Four protocols walk into one project. An orchestrator that speaks AG-UI streams&#xA;its answers as server-sent events, two specialists answer A2A tasks — one of&#xA;them for 115 seconds past any synchronous read timeout — and a billing tool&#xA;server answers MCP calls on EC2 instance types I chose myself. On top of the&#xA;fleet sits a catalog: the Agent Registry, shared across accounts through RAM,&#xA;whose semantic search finds the record named billing when asked for payment&#xA;processing. Every number below was measured in one account, &lt;code&gt;us-east-1&lt;/code&gt;.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
