Tag
Everything tagged MCP, most recent first.
7 entries
Securing the Agentic Tool Layer: A Runtime Defense Framework for MCP Agent Deployments
Talk and demo at CloudX 2026 on defending Model Context Protocol agents against attacks that arrive through the tools they already trust, built on ShieldMCP and the SAFE-MCP technique catalogue.
Four spec revisions, an official registry, the Linux Foundation, and the ecosystem that adopted it.
The closing piece of the MCP series: the four revisions that shaped the protocol through its first year and a half, the official registry and MCP Apps, the move to the Linux Foundation and open governance, how it went from one release to an industry standard, and where the 2026 roadmap points.
OAuth 2.1, the resource-server model, RFC 8707, and the threats the protocol cannot solve for you.
The security axis of MCP: how authorization works on the HTTP transport with OAuth 2.1, the server-as-resource-server model and RFC 8707 resource indicators, the later OIDC discovery and incremental-consent refinements, and the three threat classes, token passthrough, confused deputy, and prompt injection via tool output, with the guard for each.
JSON-RPC, the lifecycle handshake, and the two transports, stdio and Streamable HTTP.
How MCP messages actually move. The JSON-RPC base, the initialize handshake and capability negotiation that set up every connection, and the two standard transports, stdio for local servers and Streamable HTTP for remote ones, plus why the old HTTP-plus-SSE transport was replaced.
Tools, resources, prompts, sampling, roots, elicitation, organized by who is in control.
The heart of MCP is six primitives: three the server offers (tools, resources, prompts) and three the client offers (sampling, roots, elicitation). This piece defines each precisely, with method names and the one question that organizes them, plus what the 2025-11-25 revision added around them: async tasks, tool-calling in sampling, richer elicitation, and icons.
Generating working MCP servers straight from the OpenAPI specs you already have: the mechanical field mapping, why it takes a library and not a script, the production traps, and the guardrails to set before an agent touches real users.
What the Model Context Protocol is, the pieces it is made of, and the map of the rest.
The Model Context Protocol is how an AI application reaches the tools and data it needs. By mid-2026 it is a Linux Foundation standard with an official registry and support across the major platforms. This opening piece lays out the problem, the client-host-server architecture, the six primitives, and the map, anchoring a five-part series.
