{"sources":[{"id":"S1","url":"https://modelcontextprotocol.io/specification/2026-07-28/architecture","title":"Architecture","publisher":"Model Context Protocol","published_at":null,"accessed_at":"2026-11-19","version":"2026-07-28","document_id":"","revision_id":"","limitations":"Versioned public specification; not evidence of an implementation's enforcement."},{"id":"S2","url":"https://modelcontextprotocol.io/specification/2024-11-05/basic/lifecycle","title":"Lifecycle","publisher":"Model Context Protocol","published_at":null,"accessed_at":"2026-11-19","version":"2024-11-05","document_id":"","revision_id":"","limitations":"Historical handshake-based revision."},{"id":"S3","url":"https://modelcontextprotocol.io/specification/2025-11-25/basic/lifecycle","title":"Lifecycle","publisher":"Model Context Protocol","published_at":null,"accessed_at":"2026-11-19","version":"2025-11-25","document_id":"","revision_id":"","limitations":"Historical handshake-based revision; not modern lifecycle behavior."},{"id":"S4","url":"https://modelcontextprotocol.io/specification/2026-07-28/basic/versioning","title":"Versioning and Compatibility","publisher":"Model Context Protocol","published_at":null,"accessed_at":"2026-11-19","version":"2026-07-28","document_id":"","revision_id":"","limitations":"Opened through the lifecycle URL, which redirected to this final URL; compatibility depends on implementation support."},{"id":"S5","url":"https://modelcontextprotocol.io/specification/2026-07-28/basic/transports/stdio","title":"stdio","publisher":"Model Context Protocol","published_at":null,"accessed_at":"2026-11-19","version":"2026-07-28","document_id":"","revision_id":"","limitations":"Transport requirements do not establish process sandboxing."},{"id":"S6","url":"https://modelcontextprotocol.io/specification/2026-07-28/basic/transports/streamable-http","title":"Streamable HTTP","publisher":"Model Context Protocol","published_at":null,"accessed_at":"2026-11-19","version":"2026-07-28","document_id":"","revision_id":"","limitations":"Modern cancellation and subscription semantics differ from legacy revisions."},{"id":"S7","url":"https://py.sdk.modelcontextprotocol.io/run/","title":"Running your server","publisher":"MCP Python SDK maintainers","published_at":null,"accessed_at":"2026-11-19","version":"v2 documentation snapshot; no installed patch version established","document_id":"","revision_id":"","limitations":"Mutable maintainer documentation; integration described, not executed."},{"id":"S8","url":"https://ts.sdk.modelcontextprotocol.io/v2/serving/stdio.html","title":"Serve over stdio","publisher":"MCP TypeScript SDK maintainers","published_at":null,"accessed_at":"2026-11-19","version":"v2 documentation snapshot","document_id":"","revision_id":"","limitations":"No SDK package installation or transport execution performed."},{"id":"S9","url":"https://ts.sdk.modelcontextprotocol.io/v2/serving/http.html","title":"Serve over HTTP","publisher":"MCP TypeScript SDK maintainers","published_at":null,"accessed_at":"2026-11-19","version":"v2 documentation snapshot","document_id":"","revision_id":"","limitations":"Handler construction is distinct from hosting and security middleware; no integration test supplied."},{"id":"S10","url":"https://ts.sdk.modelcontextprotocol.io/v2/servers/tools.html","title":"Tools","publisher":"MCP TypeScript SDK maintainers","published_at":null,"accessed_at":"2026-11-19","version":"v2 documentation snapshot","document_id":"","revision_id":"","limitations":"Used for registration and validation semantics, not proof of notebook code execution."},{"id":"S11","url":"https://cheatsheetseries.owasp.org/cheatsheets/LLM_Prompt_Injection_Prevention_Cheat_Sheet.html","title":"LLM Prompt Injection Prevention Cheat Sheet","publisher":"OWASP","published_at":null,"accessed_at":"2026-11-19","version":"Live documentation snapshot","document_id":"","revision_id":"","limitations":"Defensive guidance; not a measured universal prevention guarantee."},{"id":"S12","url":"https://modelcontextprotocol.io/specification/2026-07-28/server/tools","title":"Tools","publisher":"Model Context Protocol","published_at":null,"accessed_at":"2026-11-19","version":"2026-07-28","document_id":"","revision_id":"","limitations":"List-change mechanics are protocol facts; approval invalidation strategy is application policy."},{"id":"S13","url":"https://www.rfc-editor.org/rfc/rfc8707.html","title":"RFC 8707: Resource Indicators for OAuth 2.0","publisher":"IETF / RFC Editor","published_at":"2020-02","accessed_at":"2026-11-19","version":"RFC 8707","document_id":"","revision_id":"","limitations":"Defines resource indicators and audience restriction; does not implement token validation."},{"id":"S14","url":"https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization","title":"Authorization","publisher":"Model Context Protocol","published_at":null,"accessed_at":"2026-11-19","version":"2025-11-25","document_id":"","revision_id":"","limitations":"Explicit historical authorization baseline, used for recipient validation and separate upstream tokens; not a full modern authorization implementation guide."},{"id":"S15","url":"https://modelcontextprotocol.io/docs/2025-11-25/tutorials/security/security_best_practices","title":"Security Best Practices","publisher":"Model Context Protocol","published_at":null,"accessed_at":"2026-11-19","version":"2025-11-25 path; live guidance snapshot","document_id":"","revision_id":"","limitations":"Final URL redirected from specification security_best_practices; proxy consent discussion has specific preconditions."},{"id":"S16","url":"https://cheatsheetseries.owasp.org/cheatsheets/OS_Command_Injection_Defense_Cheat_Sheet.html","title":"OS Command Injection Defense Cheat Sheet","publisher":"OWASP","published_at":null,"accessed_at":"2026-11-19","version":"Live documentation snapshot","document_id":"","revision_id":"","limitations":"Generic defense guidance; no claim that the original Git payload executes."},{"id":"S17","url":"https://git-scm.com/docs/git-log","title":"git-log","publisher":"Git project","published_at":null,"accessed_at":"2026-11-19","version":"Manual last changed in 2.56.0; page lists 2.56.1 as unchanged","document_id":"","revision_id":"","limitations":"Syntax evidence only; Git was not executed."},{"id":"S18","url":"https://cheatsheetseries.owasp.org/cheatsheets/Path_Traversal_Prevention_Cheat_Sheet.html","title":"Path Traversal Prevention Cheat Sheet","publisher":"OWASP","published_at":null,"accessed_at":"2026-11-19","version":"Live documentation snapshot","document_id":"","revision_id":"","limitations":"Containment depends on operating system, APIs and filesystem mutability; lab does not exercise paths."},{"id":"S19","url":"https://cheatsheetseries.owasp.org/cheatsheets/Server_Side_Request_Forgery_Prevention_Cheat_Sheet.html","title":"Server Side Request Forgery Prevention Cheat Sheet","publisher":"OWASP","published_at":null,"accessed_at":"2026-11-19","version":"Live documentation snapshot","document_id":"","revision_id":"","limitations":"General SSRF guidance; connection-time critique also follows inspection of the original separate lookup and request calls."},{"id":"S20","url":"https://cloudsecurityalliance.org/blog/2025/02/06/agentic-ai-threat-modeling-framework-maestro","title":"Agentic AI Threat Modeling Framework: MAESTRO","publisher":"Cloud Security Alliance","published_at":"2025-02-06","accessed_at":"2026-11-19","version":"Original framework article, live snapshot","document_id":"","revision_id":"","limitations":"Framework attribution and layer taxonomy; notebook mappings and numerical scores are original exercises."},{"id":"S21","url":"https://learn.microsoft.com/en-us/azure/security/develop/threat-modeling-tool-threats","title":"Microsoft Threat Modeling Tool threats","publisher":"Microsoft","published_at":null,"accessed_at":"2026-11-19","version":"Live documentation snapshot","document_id":"","revision_id":"","limitations":"STRIDE definition table was readable despite a generic authorization notice; no standardized STRIDE-AI claim is made."},{"id":"S22","url":"https://simonwillison.net/2025/Jun/16/the-lethal-trifecta/","title":"The lethal trifecta for AI agents: private data, untrusted content, and external communication","publisher":"Simon Willison","published_at":"2025-06-16","accessed_at":"2026-11-19","version":"Original explanatory article","document_id":"","revision_id":"","limitations":"Primary attribution for the formulation; not a calibrated scoring method or evidence of this lab's security."},{"id":"S23","url":"https://docs.pytest.org/en/stable/how-to/parametrize.html","title":"How to parametrize fixtures and test functions","publisher":"pytest maintainers","published_at":null,"accessed_at":"2026-11-19","version":"Stable documentation snapshot","document_id":"","revision_id":"","limitations":"API syntax evidence only; no installed pytest version or executed test report."},{"id":"S24","url":"https://vitest.dev/api/test","title":"Test API reference","publisher":"Vitest maintainers","published_at":null,"accessed_at":"2026-11-19","version":"Live documentation snapshot","document_id":"","revision_id":"","limitations":"API syntax evidence only; no installed Vitest version or executed test report."},{"id":"S25","url":"https://blog.modelcontextprotocol.io/posts/client_registration/","title":"Evolving OAuth Client Registration in the Model Context Protocol","publisher":"Model Context Protocol; Paul Carleton","published_at":"2025-08-22","accessed_at":"2026-11-19","version":"Saved public original and live public page","document_id":"23e40b4b0af0a8cde3a571155ae5a57b","revision_id":"edc04c0faa71610c0079a6303359573a","limitations":"Historical discussion of client registration and impersonation, not a current normative mandate."},{"id":"S26","title":"JSON-RPC 2.0 Specification","publisher":"JSON-RPC Working Group","published_at":"2013-01-04","accessed_at":"2026-11-19","version":"2.0","url":"https://www.jsonrpc.org/specification","document_id":"","revision_id":"","limitations":"Direct web reference for the scoped claim."},{"id":"S27","title":"Resources","publisher":"Model Context Protocol","published_at":"2026-07-28","accessed_at":"2026-11-19","version":"2026-07-28","url":"https://modelcontextprotocol.io/specification/2026-07-28/server/resources","document_id":"","revision_id":"","limitations":"Direct web reference for the scoped claim."},{"id":"S28","title":"Migration Guide: v1 to v2","publisher":"MCP Python SDK","published_at":null,"accessed_at":"2026-11-19","version":"v2","url":"https://py.sdk.modelcontextprotocol.io/migration/","document_id":"","revision_id":"","limitations":"Direct web reference for the scoped claim."},{"id":"S29","title":"SQL Injection Prevention Cheat Sheet","publisher":"OWASP Cheat Sheet Series","published_at":null,"accessed_at":"2026-11-19","version":"Living documentation","url":"https://cheatsheetseries.owasp.org/cheatsheets/SQL_Injection_Prevention_Cheat_Sheet.html","document_id":"","revision_id":"","limitations":"Direct web reference for the scoped claim."}],"claims":[{"id":"C1","text":"The adaptation retains seven modules and uses synthetic, bounded examples rather than a deployable server.","location":"architecture opening and scope; import-coverage.json","evidence":[],"limitations":"Coverage is an editorial mapping, not technical validation of the supplied original.","kind":"process","basis":"Direct inspection of the seven supplied section IDs and original inventory; comparison with the seven numbered article modules and returned assets."},{"id":"C2","text":"MCP uses host/client/server roles; the host coordinates clients and consent, while modern requests are self-contained.","location":"architecture introductory explanation","evidence":[{"source_id":"S1","passage":"every request is self-contained and carries its own protocol version and capabilities","location":"Architecture opening; Core Components / Host"}],"limitations":"The distinction between offering a tool and object-level authorization is the notebook's defensive interpretation, not a claimed automatic protocol guarantee.","kind":"source","basis":"Versioned architecture passage and host responsibility list."},{"id":"C3","text":"The 2024 and 2025 revisions use initialize and initialized before normal operation and define transport termination rather than a shutdown RPC.","location":"architecture lifecycle table and following paragraph","evidence":[{"source_id":"S2","passage":"No specific shutdown messages are defined","location":"Shutdown; Initialization"},{"source_id":"S3","passage":"After successful initialization, the client MUST send an initialized notification","location":"Initialization, with initialized formatted as code; Operation and Shutdown"}],"limitations":"Historical protocol behavior only; the quotation omits typographic code delimiters, not words.","kind":"source","basis":"Both versioned lifecycle pages were opened and their initialization/operation/shutdown passages read."},{"id":"C4","text":"Revision 2026-07-28 replaces the initialization handshake with per-request version metadata and supports discovery and explicit unsupported-version errors.","location":"architecture lifecycle comparison","evidence":[{"source_id":"S4","passage":"There is no negotiation handshake.","location":"Opening; Protocol Version Negotiation; Backward Compatibility"}],"limitations":"Dual-era behavior depends on implementation support; no claim all deployed servers use this revision.","kind":"source","basis":"Versioning page and compatibility matrix."},{"id":"C5","text":"Modern stdio uses subprocess standard streams for newline-delimited protocol messages, stderr for diagnostics, and stdin closure for graceful shutdown.","location":"architecture transport table; checklist item 1; Q1","evidence":[{"source_id":"S5","passage":"The server MUST NOT write anything to its stdout that is not a valid MCP message.","location":"Opening transport rules; Receiving Messages; Shutdown"}],"limitations":"Transport hygiene does not sandbox the process. Startup and shutdown testing is a proposed review practice.","kind":"source","basis":"stdio framing, response correlation and shutdown sections."},{"id":"C6","text":"Modern Streamable HTTP uses POST and JSON or request-scoped SSE responses, removes sessions/GET streams, uses listen subscriptions and treats SSE stream closure as cancellation; Origin validation and local binding guidance apply.","location":"architecture lifecycle and transport tables","evidence":[{"source_id":"S6","passage":"Removal of protocol-level sessions.","location":"Opening changes; Security & Endpoint; Receiving Messages; Cancellation"},{"source_id":"S6","passage":"Closing the SSE response stream MUST be treated by the server as cancellation of that request.","location":"Cancellation"}],"limitations":"The historical HTTP+SSE transport and legacy cancellation rules differ; the article scopes these statements to 2026-07-28.","kind":"source","basis":"Modern transport page read through cancellation and metadata sections."},{"id":"C7","text":"The six numbered boundaries and server-scoped identity/definition review policy are an original application threat-model decomposition.","location":"architecture figure and six-item explanation; threats rows 2–3; checklist item 15","evidence":[],"limitations":"Not official MCP layers, not complete wire traffic, and not proof that metadata fingerprints authenticate runtime behavior.","kind":"original_example","basis":"Editable draw.io cells and the rendered SVG with six separate boundary routes, checked against the figure and explanation."},{"id":"C8","text":"Current Python v2 documentation uses MCPServer and tool decorators; run selects transports and accepts transport options.","location":"implementations SDK integration","evidence":[{"source_id":"S7","passage":"Transport options go to run(), not to MCPServer(...).","location":"Running your server / Streamable HTTP warning"}],"limitations":"No installed SDK patch version or integration execution is established; the original FastMCP code is not declared compatible.","kind":"source","basis":"Maintainer examples and run option descriptions."},{"id":"C9","text":"TypeScript v2 uses registerTool, serveStdio factories and createMcpHandler for HTTP; HTTP identity and endpoint checks must precede the handler.","location":"implementations SDK integration; architecture transport comparison; checklist item 2","evidence":[{"source_id":"S8","passage":"serveStdio replaces the new StdioServerTransport() + server.connect(transport) wiring","location":"Coming from v1?"},{"source_id":"S9","passage":"The handler trusts its caller: it validates no Host header, no Origin header, and no token.","location":"Validate Host and Origin in front of it"},{"source_id":"S10","passage":"registerTool takes a name, a config, and a handler.","location":"Add a tool"}],"limitations":"Code typography normalized in quotations. No server listener or complete authentication adapter is included. Documentation is a v2 snapshot.","kind":"source","basis":"Read maintainer stdio, HTTP factory/authInfo and tool registration passages."},{"id":"C10","text":"The original in-memory Python and TypeScript policies check schema, audience, server/tool identity, revision, metadata, object, action and approval in the same order for the supplied ASCII cases.","location":"implementations prose and code; lab.py; tests case table","evidence":[],"limitations":"Only the standalone Python lab was executed; trusted adapter inputs are assumed. Symbolic audience and booleans do not verify credentials. Unicode length semantics differ. No I/O or action execution occurs.","kind":"original_example","basis":"Inspectable decide functions, baseline values and CASES. Two positive cases and nine single-field negative cases can be traced through the explicit branch order."},{"id":"C11","text":"Invisible text can conceal instructions; character removal and prompt delimiters do not establish injection resistance, and permissions must be enforced at tool boundaries.","location":"threats row 1; checklist items 13–14; Q3","evidence":[{"source_id":"S11","passage":"do not treat text labels or prompt wording as an enforcement boundary","location":"Structured Prompts with Clear Separation"},{"source_id":"S11","passage":"Tag characters also render some flag emoji.","location":"Input Validation and Sanitization / Invisible characters"}],"limitations":"No protection rate or universally effective filter is claimed. The lab metadata flag is not a detector.","kind":"source","basis":"Read invisible-character, structured-prompt and tool-boundary guidance."},{"id":"C12","text":"Tool lists can change, and modern list-change notifications are delivered to clients subscribed for those changes.","location":"threats row 2; checklist item 15","evidence":[{"source_id":"S12","passage":"toolsListChanged: true","location":"List Changed Notification, subscription condition"}],"limitations":"Reapproval policy is the notebook's recommendation; not every list change is malicious and notifications do not prove code integrity.","kind":"source","basis":"Tools capabilities and List Changed Notification sections."},{"id":"C13","text":"RFC 8707 defines the resource request parameter, while aud may express audience restrictions; MCP's cited authorization baseline requires intended-recipient validation and separate downstream tokens.","location":"threats row 4; checklist item 3; Q6","evidence":[{"source_id":"S13","passage":"Indicates the target service or resource to which access is being requested.","location":"Section 2, resource definition; audience representation paragraph"},{"source_id":"S14","passage":"The MCP server MUST NOT pass through the token it received from the MCP client.","location":"Access Token Privilege Restriction"}],"limitations":"The lab compares a synthetic string only; full authenticity, issuer, expiry and scope validation are outside it. MCP source is explicitly revision 2025-11-25.","kind":"source","basis":"RFC resource/audience passages and MCP token requirements read directly."},{"id":"C14","text":"MCP OAuth proxies need per-client consent; client identity cannot be inferred merely from a displayed registration name.","location":"threats row 4; Q6; source-check disclosure","evidence":[{"source_id":"S15","passage":"Maintain a registry of approved client_id values per user","location":"Confused Deputy Problem / Required Protections / Per-Client Consent Storage"},{"source_id":"S25","passage":"the authorization server must be able to trust the client information it has","location":"Background on OAuth"}],"limitations":"Proxy consent guidance has specific preconditions. The saved article is historical background, not proof of current implementation behavior.","kind":"source","basis":"Read saved document 23e40b4b0af0a8cde3a571155ae5a57b revision edc04c0faa71610c0079a6303359573a and opened its public page; read proxy consent guidance."},{"id":"C15","text":"Avoid direct OS commands where possible; structured arguments still need command-specific validation because argument interpretation remains.","location":"threats row 5; checklist items 5–6; Q4","evidence":[{"source_id":"S16","passage":"The primary defense is to avoid calling OS commands directly.","location":"Primary Defenses / Defense Option 1; Parameterization in conjunction with Input Validation"}],"limitations":"No original payload is reproduced or claimed to work. Validation depends on the chosen program and operation.","kind":"source","basis":"Read OWASP argument-injection and primary-defense passages."},{"id":"C16","text":"git log places path operands after --, so the original branch variable in that position does not implement the advertised branch-selection behavior.","location":"threats correction paragraph; checklist item 6; Q4","evidence":[{"source_id":"S17","passage":"git log [<options>] [<revision-range>] [[--] <path>…​]","location":"SYNOPSIS, formatting normalized"}],"limitations":"Syntax inspection, not a Git execution or vulnerability reproduction. The original simulated execution claim is not established.","kind":"source","basis":"Compared the decoded original cmd array with the official git-log synopsis."},{"id":"C17","text":"Prefer server-side object identifiers; raw string prefixes and pre-open canonicalization alone do not establish race-resistant filesystem containment.","location":"threats row 6; checklist items 7–9; Q2","evidence":[{"source_id":"S18","passage":"Resolving links before the check helps, but leaves a time-of-check to time-of-use (TOCTOU) race","location":"Symbolic Links and Race Conditions; Avoid User Input in File Paths"}],"limitations":"The synthetic object allowlist is not a filesystem test. Null-byte rejection is a proposed input check, not sufficient containment.","kind":"source","basis":"Read identifier mapping, component containment and symbolic-link sections."},{"id":"C18","text":"SSRF defenses need destination/address policy and redirect handling; the original separate lookup and HTTP request do not bind the later connection to the checked result.","location":"threats egress paragraph; checklist items 10–12","evidence":[{"source_id":"S19","passage":"Disable the support for the following of the redirection in your web client","location":"Case 1 / Application layer, redirect note; Domain name DNS-pinning discussion"}],"limitations":"Connection-binding critique is an inference from original validate_url_ssrf returning a URL followed by a separate httpx get. No DNS/network experiment was performed.","kind":"source","basis":"OWASP redirect and DNS-pinning guidance plus static inspection of the supplied original's two separate operations."},{"id":"C19","text":"The four vendor-risk rows are proposed evidence requests for untrusted content, authority, implementation flaws and dependency changes, not incident claims about particular vendors.","location":"threats vendor-risk table","evidence":[],"limitations":"No container, lockfile or named vendor is certified secure; no claimed CVE mapping.","kind":"original_example","basis":"Original four-row vendor-risk learning inventory transformed into explicit review tasks and evidence fields; technical premises separately covered by C11, C13, C15, C17 and C18."},{"id":"C20","text":"MAESTRO uses seven layers: Foundation Models, Data Operations, Agent Frameworks, Deployment and Infrastructure, Evaluation and Observability, Security and Compliance, and Agent Ecosystem; L6 is vertical/cross-cutting.","location":"threat-modeling MAESTRO table and explanation","evidence":[{"source_id":"S20","passage":"seven-layer reference architecture described by Ken Huang","location":"Section 3.2; Layer-Specific Threat Modeling headings for Layers 7 through 1"},{"source_id":"S20","passage":"This vertical layer cuts across all other layers","location":"Layer 6: Security and Compliance"}],"limitations":"Notebook-specific review questions and mappings are original, not an official OWASP crosswalk or validation of scoring.","kind":"source","basis":"Read each layer heading and L6 description in the CSA framework article."},{"id":"C21","text":"Microsoft STRIDE covers spoofing, tampering, repudiation, information disclosure, denial of service and elevation of privilege.","location":"threat-modeling STRIDE table","evidence":[{"source_id":"S21","passage":"Microsoft uses the STRIDE model, which categorizes different types of threats","location":"STRIDE model introduction and six-row category table"}],"limitations":"MCP examples are the notebook's interpretation; no standardized STRIDE-AI framework is asserted.","kind":"source","basis":"Readable Microsoft category table and definitions."},{"id":"C22","text":"Willison's lethal-trifecta formulation combines private data, untrusted content and external communication.","location":"threat-modeling capability paragraph; Q5","evidence":[{"source_id":"S22","passage":"Access to your private data","location":"Opening three-item capability list"},{"source_id":"S22","passage":"Exposure to untrusted content","location":"Opening three-item capability list"},{"source_id":"S22","passage":"The ability to externally communicate","location":"Opening three-item capability list"}],"limitations":"Used for attribution and composition reasoning, not calibrated scoring or certainty of compromise.","kind":"source","basis":"Read the original 16 June 2025 explanation and its three capability definitions."},{"id":"C23","text":"The framework review prompts, STRIDE adaptations, capability exercise, register scores and hypothetical update are original synthetic planning exercises.","location":"threat-modeling tables and exercises; register-template.txt; Q5","evidence":[],"limitations":"Ordinal products are prioritization conventions, not probabilities or expected loss. The T3 update is conditional on evidence not supplied here.","kind":"original_example","basis":"Explicit scores: 4×4=16, 3×5=15, 4×5=20, 3×4=12 and hypothetical 2×5=10. Layer prompts and register fields are inspectable in the article and blank template."},{"id":"C24","text":"The five decision exercises change one baseline field and predict a denial with its check present, versus allowance if only that check is omitted.","location":"decision-exercises table and limitations; Q3","evidence":[],"limitations":"Counterfactual policy reasoning only; no real Unicode detection, token verification, path access or command parsing is demonstrated.","kind":"original_example","basis":"lab.py baseline and checks; table changes metadata_reviewed, action, audience and object_id. For action=other, removing the action allowlist leaves the note-specific approval test inactive."},{"id":"C25","text":"Paired original suites cover two positive and nine negative cases plus malformed values, non-mutation, repeatability and revision changes; they are unexecuted policy tests.","location":"tests prose, case table, code and test-policy-pytest.txt","evidence":[],"limitations":"No passing execution count, SDK integration coverage or operational protection claim.","kind":"original_example","basis":"Direct inspection of CASES and the matching Vitest rows, four malformed values and the repeatability/revision test. No source-supplied code was executed."},{"id":"C26","text":"Pytest parametrize supports running the policy test against multiple argument sets.","location":"tests Pytest explanation and code","evidence":[{"source_id":"S23","passage":"allows one to define multiple sets of arguments and fixtures at the test function or class","location":"Parametrization overview, pytest.mark.parametrize bullet"}],"limitations":"API support does not prove the proposed tests pass in an installed environment.","kind":"source","basis":"Official parametrization documentation read; notebook cases are original."},{"id":"C27","text":"Vitest test.each supports the corresponding table-driven policy test.","location":"tests Vitest explanation and code","evidence":[{"source_id":"S24","passage":"Use test.each when you need to run the same test with different variables.","location":"test.each API section"}],"limitations":"No installed Vitest or TypeScript compiler version established; execution remains illustrative.","kind":"source","basis":"Official API examples read without execution."},{"id":"C28","text":"The checklist and notes template are an original evidence-oriented adaptation of all 15 supplied control objectives.","location":"checklist; notes-template.txt","evidence":[],"limitations":"Completing a checklist is not certification. Technical premises are mapped to C5–C18; null-byte and metadata-endpoint items are proposed bounded checks.","kind":"original_example","basis":"Comparison of each supplied checklistItems entry against numbered items 1–15; retained six domain names and added explicit evidence/limitations fields in notes-template.txt."},{"id":"C29","text":"The supplied script contains five static scenario narratives, six quiz objectives and 15 checklist items across six domains; adaptation and evidence disclosures describe actual inspection rather than execution or expert verification.","location":"source-checks; editorial notes throughout; import-coverage.json","evidence":[],"limitations":"The coordinator-supplied byte count/hash is not independently recomputed here. Source audit and rendering provenance are separate from this author package.","kind":"process","basis":"The coordinator embeds the complete original HTML for direct inspection of payloadScenarios, selectPayloadScenario, quizQuestions and checklistItems. import-coverage.json maps the adaptations to the rendered sections. The original scripts were used only as text evidence."},{"id":"C30","text":"One client per server and the exposure of tools, resources and prompts accompany basic JSON-RPC request, reply and notification framing.","location":"Architecture topology and JSON-RPC examples","limitations":"Fictional envelope examples omit version-specific MCP metadata.","kind":"source","basis":"Direct primary publication passages and scoped notebook examples.","evidence":[{"source_id":"S1","passage":"Communicates with exactly one server","location":"Clients"},{"source_id":"S1","passage":"Expose resources, tools and prompts via MCP primitives","location":"Servers"},{"source_id":"S26","passage":"A Notification is a Request object without an \"id\" member.","location":"4.1 Notification"},{"source_id":"S26","passage":"Either the result member or error member MUST be included, but both members MUST NOT be included.","location":"5 Response object"}]},{"id":"C31","text":"Legacy resource subscriptions use subscribe and unsubscribe; modern resources are watched with the resourceSubscriptions filter on subscriptions/listen.","location":"Resource subscription lifecycle","limitations":"Synthetic delivery and cleanup exercise; no transport execution.","kind":"source","basis":"Direct primary publication passages and scoped notebook examples.","evidence":[{"source_id":"S27","passage":"using the resourceSubscriptions filter","location":"Capabilities"},{"source_id":"S28","passage":"removes resources/subscribe and resources/unsubscribe from the 2026-07-28 wire","location":"Client resource-subscription methods deprecated"}]},{"id":"C32","text":"Bind database values separately from query structure and check the caller’s object access independently.","location":"Query structure and data","limitations":"Defensive design example; no database connected.","kind":"source","basis":"Direct primary publication passages and scoped notebook examples.","evidence":[{"source_id":"S29","passage":"Define the SQL structure separately from its data values and bind those values through the database API","location":"Parameterized Queries"}]},{"id":"C33","text":"A protocol test should cover discovery, dispatch, result correlation, tool-level failure and protocol-level error with an in-memory fixture.","location":"In-memory protocol integration exercise","limitations":"Original planned test, not SDK conformance or an executed test.","kind":"source","basis":"Direct primary publication passages and scoped notebook examples.","evidence":[{"source_id":"S26","passage":"This member is used to correlate the context between the two objects.","location":"4 Request object"}]}]}