Model Context Protocol Quiz

Answers and explanations appear as you take the quiz.

1. In MCP architecture, what coordinates the user experience and security decisions?
   • A resource item
   • The server’s prompt template
   • The model weights alone
   • The host application
2. Which MCP capability supplies contextual content rather than performing an operation?
   • A resource
   • A tool
   • A permission grant
   • A transport retry
3. What does a successful MCP connection establish?
   • That the server is certified trustworthy
   • That communication works, not that every tool is safe or correct
   • That every capability has been authorized for every user
   • That the user’s task is complete
4. Why inspect a server’s tool descriptions and behavior before allowing write operations?
   • Tool names are guaranteed to describe all side effects
   • The protocol forbids write operations
   • Tools can change external state and require an appropriate permission boundary
   • Descriptions automatically enforce user authorization
5. What should an application do with instructions embedded in server-returned content?
   • Allow them to override authorization
   • Convert them into permanent host policy
   • Follow them without showing the user
   • Treat them as input to evaluate, not authority to expand the user’s request
6. Why inspect negotiated capabilities after connecting?
   • Hosts and servers may implement different subsets of the specification
   • Every host supports every feature identically
   • Capability discovery is only cosmetic
   • It proves the tool outputs are factually correct
7. Which lifecycle checks are relevant to an MCP integration?
   • Only whether the server has a logo
   • Argument validation, errors, reconnection, and revoked access
   • Only the first successful connection
   • The color of the host interface
8. Why record server and protocol versions?
   • Versions guarantee semantic equivalence
   • The protocol version stores user secrets
   • A version change can affect compatibility and behavior during later investigation
   • Version records replace authorization