AI Weekly Malaysia

MCP lead maintainers David Soria Parra and Den Delimarsky published a roadmap with five priority areas: agentic messaging primitives (server-initiated events like webhooks/channels, maturing the Tasks extension SEP-2663 toward spec), HTTP-native transport unification (extending the 2026-07-28 remote-server-as-plain-HTTP model to local servers via Streamable HTTP over stdio), agent identity for non-interactive cloud workloads, improved primitives, and SDK DX improvements.

Why: If you build MCP servers or clients, the transport unification means you should plan around Streamable HTTP as the single transport rather than maintaining separate stdio and HTTP code paths. The agent identity work signals that browser-based OAuth approval will be replaced or supplemented by standardized machine identity for cloud-deployed agents, so anyone building non-interactive agent pipelines should track SEP-2663 and the agent identity proposals before hardening auth today.

The article traces the history of Finger, a 1971 protocol from Stanford's AI Lab that let users check who was online and read their .plan and .project text files—effectively the first social network. The protocol still works today, with clients preinstalled on macOS, most Unix systems, and Windows, and public hosts like happynetbox.com letting anyone publish without a server.

Why: There is no practical action item for working builders here; it is a nostalgic history piece. At most, a vibe coder could try `finger random@happynetbox.com` for curiosity, but nothing in the text suggests you should adopt or change anything in your stack.