MCP for buyers and CTOs
Four articles for people who buy MCP servers rather than build them: what to ask a vendor, what to govern, what is stable, and which AI apps support what.
I wrote it for CTOs, architects and procurement teams who need to judge an MCP server without reading the specification. The parts read straight through.
- Part 1

What to require from an MCP server vendor: a buyer’s checklist The questions to put to an MCP server vendor before you sign, drawn from the 2026-07-28 specification, and what a good answer to each looks like.
- Part 2

An MCP governance checklist for the CTO The decisions a CTO has to make before MCP servers reach a company’s AI tools, from who controls each primitive to what the host must enforce.
- Part 3

MCP maturity in October 2026: what’s stable, what’s deprecated, what’s still a bet Which parts of MCP a buyer can rely on in October 2026: five revisions of the specification, what 2026-07-28 removed, and where each extension stands.
- Part 4

MCP host coverage: will the server work in the AI apps your company uses? Tools on a remote server are the only MCP surface all seven hosts support, so check a server against the AI apps your company runs before you buy it.