{ "schema": "varexis-index-free-publication-preview/1", "catalogue_version": "ice-12-tranche-72-v1", "route_id": "agentic_reviewed_mcp_stepup_scope_union_continuity", "record_id": "VXI-EXT-ICE12-MCP-STEPUP-SCOPE-UNION-CONTINUITY-01-v1", "question": "Should an MCP client request only the newest challenged scope during reauthorisation?", "answer": "MCP 2026-07-28 describes computing the union of the client's previously requested scope set and the current challenge before reauthorisation. It also recommends including challenged scopes alongside previously granted ones to avoid losing permissions for other operations. This is request-set continuity, not evidence that the authorisation server granted the union.", "records": [ { "record_id": "VXI-EXT-ICE12-MCP-STEPUP-SCOPE-UNION-CONTINUITY-01-v1", "url": "/varexis-index/records/mcp-stepup-scope-union-continuity.json", "content_sha256": "e5b3bafcd138bac8b961b94eadb3d2caa988ea5efee87bb8801a45ca819744c1", "evidence": { "schema": "varexis-public-evidence-record/0.3", "generated_at_utc": "2026-10-31T14:11:02.820224+00:00", "record_id": "VXI-EXT-ICE12-MCP-STEPUP-SCOPE-UNION-CONTINUITY-01-v1", "record_kind": "external_reference", "title": "MCP reauthorisation scope accumulation", "system": "Model Context Protocol", "evidence_family": "vendor_evidence_review", "index_status": "PUBLIC_SAFE_SOURCE_REVIEW", "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY", "canonical_question": "Should an MCP client request only the newest challenged scope during reauthorisation?", "near_questions": [ "How should MCP clients retain scopes across step-up authorisation?", "Can requesting only a new MCP scope drop earlier permissions?", "Does the MCP scope union prove the server granted all permissions?", "Which scope history should an MCP client retain for reauthorisation?" ], "supported_claims": [ { "claim": "MCP 2026-07-28 describes computing the union of the client's previously requested scope set and the current challenge before reauthorisation. It also recommends including challenged scopes alongside previously granted ones to avoid losing permissions for other operations. This is request-set continuity, not evidence that the authorisation server granted the union.", "reliance": "DOCUMENTED_CAPABILITY_ONLY" } ], "not_demonstrated_claims": [ "Refuse to treat a scope request as effective authority. Preserve the relevant resource and authorisation context, reconcile requested versus granted scopes, and do not carry unrelated credentials or authority across issuers.", "Buyer implementation, live runtime enforcement, settled payment, verified deletion or certification are not established.", "No expanded capabilities or licences for existing INDEX executables." ], "public_summary": "MCP 2026-07-28 describes computing the union of the client's previously requested scope set and the current challenge before reauthorisation. It also recommends including challenged scopes alongside previously granted ones to avoid losing permissions for other operations. This is request-set continuity, not evidence that the authorisation server granted the union.", "related_record_ids": [], "source_review": { "source_type": "official_external_documentation", "source_title": "MCP HTTP authorization, specification 2026-07-28", "source_url": "https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization.md", "checked_on": "2026-10-31", "candidate_record_id": "VXI-EXT-ICE12-MCP-STEPUP-SCOPE-UNION-CONTINUITY-01-v1", "candidate_record_sha256": "bdf53535f8824a38a05b792412d996ad7490cfc12ae30534b6e0319885c3aee3", "method": "Primary documentation reviewed for the published bounded statement.", "deployment_tested_by_varexis": false, "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research." }, "answer_policy": { "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY", "bounded_answer": "MCP 2026-07-28 describes computing the union of the client's previously requested scope set and the current challenge before reauthorisation. It also recommends including challenged scopes alongside previously granted ones to avoid losing permissions for other operations. This is request-set continuity, not evidence that the authorisation server granted the union.", "required_buyer_context": "client/resource and authorisation-server context; previous requested/granted scope sets and new challenge; reauthorisation request and resulting effective grant. Buyer deployment not inspected.", "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state." }, "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.", "decision_profile": { "schema": "varexis-vendor-evidence-review/1", "review_status": "documentation_review_only", "applicability_status": "MCP specification 2026-07-28 step-up flow; previously requested and actually granted scope sets are explicitly distinguished. Review capture 2026-10-31. Buyer deployment not inspected.", "checked_on": "2026-10-31", "claim_to_check": "Should an MCP client request only the newest challenged scope during reauthorisation?", "documented_statement": { "status": "documented", "statement": "MCP 2026-07-28 describes computing the union of the client's previously requested scope set and the current challenge before reauthorisation. It also recommends including challenged scopes alongside previously granted ones to avoid losing permissions for other operations. This is request-set continuity, not evidence that the authorisation server granted the union.", "source_ids": [ "mcp-auth" ] }, "review_inference": { "status": "review_inference", "statement": "Refuse to treat a scope request as effective authority. Preserve the relevant resource and authorisation context, reconcile requested versus granted scopes, and do not carry unrelated credentials or authority across issuers. The existing record compares a challenge with advertised scopes and initial selection. This review concerns accumulation across successive operation challenges and avoiding accidental loss of earlier requested permissions. Operational review inference; no deployment outcome was observed.", "source_ids": [ "mcp-auth" ] }, "buyer_evidence_required": [ "client/resource and authorisation-server context", "previous requested/granted scope sets and new challenge", "reauthorisation request and resulting effective grant" ], "review_condition": { "status": "varexis_review_policy", "statement": "Refuse to treat a scope request as effective authority. Preserve the relevant resource and authorisation context, reconcile requested versus granted scopes, and do not carry unrelated credentials or authority across issuers." }, "unknowns": "Buyer implementation, installed versions, effective authority, source completeness and actual business outcomes were not inspected.", "unknown_finding": { "status": "unknown", "statement": "No buyer deployment or transaction was observed." }, "evidence_sources": [ { "source_id": "mcp-auth", "url": "https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization.md", "final_url": "https://modelcontextprotocol.io/specification/2026-07-28/basic/authorization.md", "captured_at_utc": "2026-10-31T14:07:23.008429+00:00", "status": 200, "content_type": "text/markdown; charset=utf-8", "bytes": 25510, "sha256": "59bc8d07ef88538e4d4e539ca1c846c3ae3162e7911dc29453495cddeac18444", "title": "MCP HTTP authorization, specification 2026-07-28", "publisher": "Model Context Protocol", "checked_on": "2026-10-31", "capture_status": "captured_primary_documentation", "claim_review_completed": true, "hash_basis": "Raw HTTP response bytes retained privately; not deployment attestation.", "version_context": "MCP specification 2026-07-28", "rights_disposition": "Original bounded paraphrase with source attribution. Full source capture remains private; no source code, examples or vendor documentation is redistributed. Anthropic repository MIT licensing and IETF source notices remain with original sources.", "reviewed_sections": [ "Step-Up Authorization Flow", "previously requested scope set", "Retry the original request", "same resource and operation" ] } ], "observed_deployment": false, "commercial_reliance_boundary": "Documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations locally; they do not inspect provider accounts, verify live behaviour, enforce decisions or certify compliance.", "paid_value": { "decision_context": "Refuse to treat a scope request as effective authority. Preserve the relevant resource and authorisation context, reconcile requested versus granted scopes, and do not carry unrelated credentials or authority across issuers.", "free": "Complete source review, questions, provenance and limitations; free to read and save locally.", "single_request": "Unavailable for this publication-only record; historical saved retrieval is unchanged.", "evidence_receipt": "Unavailable for this publication-only record; no paid retrieval entitlement is added.", "excluded": [ "Fresh source research", "Native provider integration or schema support", "Live inspection or runtime enforcement", "Payment settlement or verified deletion", "Certification or expanded licences" ], "integrity": "Hashes identify content versions; they do not prove factual truth or provide a signature." }, "revalidation": { "trigger": "Recheck current primary documentation and applicable SDK, service and configuration before reliance. No ongoing monitoring is included.", "specific_watch": "Step-Up Authorization Flow; previously requested scope set" }, "buyer_relevance": "Refuse to treat a scope request as effective authority. Preserve the relevant resource and authorisation context, reconcile requested versus granted scopes, and do not carry unrelated credentials or authority across issuers.", "refusal_conditions": [ "Refuse to treat a scope request as effective authority. Preserve the relevant resource and authorisation context, reconcile requested versus granted scopes, and do not carry unrelated credentials or authority across issuers.", "Do not infer deployment conformance, authority or successful outcomes from source documentation." ], "decision_context": { "operator": "Developer or reviewer assessing agent execution and evidence", "scenario": "Should an MCP client request only the newest challenged scope during reauthorisation?", "consequence": "Refuse to treat a scope request as effective authority. Preserve the relevant resource and authorisation context, reconcile requested versus granted scopes, and do not carry unrelated credentials or authority across issuers.", "confidence": "Primary-documentation support only; buyer demand and deployment outcomes unestablished." }, "novelty_review": { "candidate_id": "ICE12-09", "disposition": "new_distinct", "nearest_record_id": "VXI-EXT-ICE09-MCP-SCOPE-CHALLENGE-VERSUS-ADVERTISED-SCOPES-01-v1", "nearest_record_url": "/varexis-index/records/mcp-scope-challenge-versus-advertised-scopes.json", "nearest_record_sha256": "209b8084db47e817ba82d6f9f85eed6dd0d0740300ec9fa8f2fa6333f109f6f9", "material_distinction": "The existing record compares a challenge with advertised scopes and initial selection. This review concerns accumulation across successive operation challenges and avoiding accidental loss of earlier requested permissions.", "review_status": "Primary-source review and full adjacent-record comparison; no independent challenge claimed." }, "optional_selection": { "guide_id": "delegated-agent-identity-continuity", "guide_url": "/index-guides/delegated-agent-identity-continuity", "guide_manifest": "/varexis-index/decision-guides.json", "checker": { "product_id": "agent-tool-admission", "price_gbp_excluding_vat": 49, "purchase_url": "/index-access?route=agentic_pack_tool_admission_v1", "licence_scope": "Existing separate internal-use licence; subscriptions do not include the executable.", "benefit": "Optional local analysis of supported supplied declarations only; no native Claude SDK or MCP integration is added." }, "boundary": "This free record supports an evidence-selection decision. The existing checker does not diagnose these platforms, extract their logs or prove the documented condition occurred." }, "exact_access": { "endpoint": "/mcp/catalogue", "tool": "get_publication_record", "arguments": { "record_id": "VXI-EXT-ICE12-MCP-STEPUP-SCOPE-UNION-CONTINUITY-01-v1" }, "record_url": "/varexis-index/records/mcp-stepup-scope-union-continuity.json", "original_mcp_search": false, "paid_saved_retrieval": false } }, "niche": { "niche_id": "ice12-identity", "label": "Agent Identity, Credentials & Delegation", "classification_id": "identity", "classification_label": "Agent Identity, Credentials & Delegation", "topic_id": "identity", "buyer_intent": "Refuse to treat a scope request as effective authority. Preserve the relevant resource and authorisation context, reconcile requested versus granted scopes, and do not carry unrelated credentials or authority across issuers.", "comparison_role": "supplementary_discovery" }, "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.", "service_route": { "request_guide": "/varexis-index/request.html", "request_workflow": "/varexis-index/request-workflow.json", "service_id": "single_request", "service_routes_url": "/varexis-index/service-routes.json", "payment_required": true, "availability_endpoint": "/api/index/capabilities", "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED", "checkout_url": "/index-access" }, "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.", "human_page": "/varexis-index/catalog.html#mcp-stepup-scope-union-continuity", "machine_readable_record": "/varexis-index/records/mcp-stepup-scope-union-continuity.json" } } ], "access": { "mode": "exact_http_only", "payment_required": false, "purchase_url": null, "mcp_preview_available": false, "paid_saved_retrieval_available": false, "natural_language_search_qualified": false }, "boundary": "Catalogue additions are available free through the exact HTTP JSON links below. Enhanced natural-language discovery is not yet qualified for these records. They are outside MCP search, MCP preview and paid saved retrieval. No search qualification, executable capability or entitlement is added.", "content_sha256": "0cc21966ec211927680f76adc1bb91ce6c27fa19075c710ecb5512a2e360846f" }