Skip to content
T threat.cafe

Tag

#specification

1 post

  1. · Constance Ibe-Whitmore · Regulation and frameworks · on threat.cafe

    The MCP spec's own security MUSTs, read by a buyer: five requirements to make any MCP vendor prove

    The MCP spec already sets security obligations: no token passthrough, per-client consent, verified requests, exact-command consent, safe URL handling. Ask vendors to prove each, in the spec's own words.