News, with our take

RSS feed

We link to the original and add a short note on what it means for installing and securing MCP servers. Our own catalog changes are listed alongside.

Stories

Our changelog

26 current servers added to the catalog

Axis MCP catalog

Vendor-official, actively maintained servers, each checked against its upstream source on Oct 11 with setup examples for six clients and a reviewed write-up. Retired listings now point to their maintained successors.

Our changelog

A page for each server

Axis MCP catalog

Every configurable server now has its own page with a reviewed write-up, example tools, setup for each client and the sources it was checked against. Archived and deprecated listings stay reachable for existing users but are not offered to search engines.

Our changelog

About, Privacy and Contact pages

Axis MCP catalog

The site now says who runs it, what it collects and how to send a correction or a server for review.

Explainer

MCP was always a bad idea?  (opens in a new tab)

Simon Willison

Our take. Willison's reply: if you don't want an agent with unrestricted shell and internet access, MCP gives you control over which services it reaches, auth that keeps API keys away from the agent, and audit logging. That is the practical case for installing servers instead of handing an agent raw keys. Our auth and security guide covers where each client keeps those credentials.

Spec and SDKs

The New MCP Roadmap  (opens in a new tab)

MCP blog

Our take. Next priorities include running local servers over Streamable HTTP and agent identity built on existing standards "rather than pasted API keys and long-lived tokens." Nothing changes in your config today. Our remote vs local guide explains how the two transports differ now.

Advisory

How Cloudflare detects MCP traffic and helps secure it  (opens in a new tab)

Cloudflare blog

Our take. Cloudflare Gateway can now flag inspected MCP traffic by its MCP-Protocol-Version header and block direct connections that skip an approved MCP Portal. It cannot see local stdio servers, which never touch the network. If your company runs Gateway, a remote server you add yourself may be blocked unless IT puts it behind the Portal; see remote vs local.

Spec and SDKs

The 2026-07-28 Specification  (opens in a new tab)

MCP blog

Our take. Clients must now validate the OAuth issuer before redeeming a code, Dynamic Client Registration is deprecated in favour of client metadata documents, and the legacy HTTP+SSE transport starts a year-long offramp. Expect OAuth sign-in prompts for remote servers to change as clients update. Supabase says the new multi round-trip requests let its tools confirm costly or destructive actions first; see our Supabase survey.

Spec and SDKs

The Official Ruby SDK for MCP Reaches 1.0  (opens in a new tab)

MCP blog

Our take. The mcp gem's 1.0 passes every server and client conformance scenario and supports stdio and Streamable HTTP. It implements the 2025-06-18 and 2025-11-25 revisions; 2026-07-28 support is in progress. Relevant if you build servers rather than install them.

Advisory

Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)  (opens in a new tab)

Glama blog

Our take. It cites three incidents, including CVE-2025-6514, and argues Docker and IAM alone don't bound what an agent-driven tool does; its advice is to match the sandbox to the workload and keep network egress rules beneath it. Before running a local server, check which folders and networks it can reach. The Filesystem server, for example, only gets the directories you list.

Headlines link to the original publisher. Notes are ours, written from each article on Oct 15, 2026.