Lesson deck
Model Context Protocol and tool ecosystems flashcards
Reviewing needs JavaScript. You can read every card in the list below.
Loading your cards...
Back to the lesson6 cards in this deck
Read all 6 cards as a list
- Front
- What problem does MCP solve and how does it relate to function calling?
- Back
- It replaces N x M custom integrations with N + M through a standard host-to-server protocol. Function calling is the model-facing interface; MCP standardises how the host discovers and invokes tools. They compose.
- Front
- Name three MCP security risks and a mitigation for each.
- Back
- Injection through tool descriptions or results (treat as untrusted, show inputs, approvals); over-broad or passed-through tokens (least privilege, accept only tokens issued for the server); malicious or changed servers (pin, allow-list, sandbox).
- Front
- Where does the USB-C analogy for MCP break?
- Back
- The model never talks to the server; the host mediates, so controls live there. Connecting a server means trusting text it controls, and trust is per server and per user, not plug-and-play.
- Front
- What are tools, resources and prompts, and who controls each?
- Back
- Tools are actions the model invokes (model-controlled). Resources are URI-identified context (application-driven). Prompts are templates the user picks (user-controlled).
- Front
- What changed in MCP revision 2026-07-28?
- Back
- Stateless requests with version and capabilities on each request (no initialize handshake, server/discover added), no protocol-level sessions or Mcp-Session-Id, multi round-trip requests for server-initiated input, and Roots, Sampling and Logging deprecated.
- Front
- Which transports are standard in current MCP, and how is state kept across calls?
- Back
- stdio for local subprocesses and Streamable HTTP for remote servers (HTTP+SSE is deprecated). Without sessions, a server returns an explicit handle that the model passes back as a tool argument, and the server checks ownership.