Study MCP architecture
Jump & context
Week 5: RAG ACLs, PII UUID Gateway, Training-Data Poisoning & Agent/MCP Foundations
The five hours
- 01
Concepts & system design
60 min· read · map the mechanismR21 — MCP Specification: architecture, lifecycle, transports, and security
Read the assigned sections; map the mechanism, threat model and trade-offs.
- 02
Project implementation
120 min· build · integrate · debugStudy Model Context Protocol (MCP) architecture: client/server roles, tool discovery, JSON-RPC 2.0 messages, transports, and trust boundaries. Build a local MCP server exposing 2 safe repository-exploration tools.
Build, integrate, debug and improve the increment in the active project.
- 03
Security lab
60 min· attack your own systemMap every trust boundary between the LLM, agent host, MCP client,
mcp-proxy(D2), and MCP server.Test the abuse case, failure path, authorization bypass or resource limit.
- 04
Verification & evidence
30 min· test · record evidenceWorking local MCP server + protocol data-flow and trust-boundary diagram.
Add or run regression tests; record the 9-point evidence record.
- 05
Deliberate practice & Socratic review
30 min· explain aloud · update gapsAnswer the 8 Socratic questions without notes: What? Why? How? What if? Why not? How can I prove it? Where can it break? What have I learned?
Re-explain the hardest concept aloud, inspect one edge case, update the gap log.
- total5 h
Read today · inside the concepts block
R21Official specification: client/server lifecycle, JSON-RPC messages, tool discovery, authorization, and trust boundaries.
Read only the named sections needed for today's task. Reading sits inside the 60-minute concepts block; it is not extra time.
Free resources for this day
5 curated- docsModel Context Protocol · ~45 min readSpecification - Model Context Protocol
Defines the host/client/server roles, JSON-RPC 2.0 message shapes, lifecycle negotiation and stdio vs Streamable HTTP transports that the local two-tool server must implement.
R21checked 2026-11-11 - videoCaleb Curry · ~40 minConnect AI to Anything - Build your First MCP Server (Model Context Protocol)
Walks transport choice (stdio vs http), the three primitives (resources, prompts, tools) and a full tool registration, ending in a working server you can point at your own repo.
R21checked 2026-11-11 - videoOxylabs · ~15 minBuild an MCP Server in Python (Full Tutorial)
Builds a minimal FastMCP server and explains the `@mcp.tool` decorator and tool discovery, so you see the tools/list payload your repo-exploration tools will advertise.
R21checked 2026-11-11 - articleCodilime · ~15 min readModel Context Protocol (MCP) explained: A practical technical overview for developers and architects
Explains the stateful session, JSON-RPC framing, and where the trust boundary sits between client and server — the architecture part the day asks you to study before writing code.
R21moved 2026-11-11 - courseModel Context Protocol · ~30 min hands-onBuild an MCP server - Model Context Protocol
Official step-by-step that ships a two-tool server and connects it to a host, which is the exact shape of the day's deliverable before you swap in read-only repo tools.
R21checked 2026-11-11
Evidence record · 9-point standard
A lab is complete only when it produces evidence. Installing PyRIT, Garak, Presidio or TransformerLens is not completion. Saved on this device only.
Day notes
emptyThe two source formulations
verbatim · nothing summarisedProject & Deliverable Target
P3 | `D2` (Sandboxed MCP Proxy) | S3
Core Implementation
Study Model Context Protocol (MCP) architecture: client/server roles, tool discovery, JSON-RPC 2.0 messages, transports, and trust boundaries. Build a local MCP server exposing 2 safe repository-exploration tools.
Security Lab
Map every trust boundary between the LLM, agent host, MCP client, mcp-proxy (D2), and MCP server.
Verification & Evidence
Working local MCP server + protocol data-flow and trust-boundary diagram.
Read Today (60m Concepts Block)
R21 (MCP Specification: architecture, lifecycle, transports, and security).
---