{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-16T13:36:43.315Z",
  "record_id": "VXI-EXT-PROCUREMENT-TELEPORT-OAUTH-01-v1",
  "record_kind": "external_reference",
  "title": "Teleport MCP: Proxy identity and upstream OAuth",
  "system": "Teleport MCP access",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a Teleport login also authorize the upstream MCP service?",
  "near_questions": [
    "Is upstream OAuth separate from Teleport login?",
    "Which layer restricts MCP tools?",
    "Where are upstream tokens stored?",
    "Does the authorization request leave from the workstation?",
    "Which scopes did the upstream server request?",
    "What happens after the server URI changes?",
    "Does tsh refresh expired access tokens?",
    "Can a custom Authorization header replace stored credentials?",
    "Does the client support this login version?",
    "Which identity reaches the upstream service?",
    "What evidence is needed for both access layers?",
    "Can I preserve this proxy-and-service review?"
  ],
  "supported_claims": [
    {
      "claim": "Some upstream servers need a separate OAuth token. Teleport still applies its own roles and tool permissions, while the upstream token satisfies that service. The documented login stores credentials locally and contacts the authorization server from the workstation. Changing the upstream URI requires a new login.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration or effective access rights",
    "Independent execution, completeness or security testing",
    "Vendor certification, legal compliance or guaranteed suitability"
  ],
  "public_summary": "Some upstream servers need a separate OAuth token. Teleport still applies its own roles and tool permissions, while the upstream token satisfies that service. The documented login stores credentials locally and contacts the authorization server from the workstation. Changing the upstream URI requires a new login.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Teleport upstream MCP OAuth",
    "source_url": "https://goteleport.com/docs/connect-your-client/model-context-protocol/mcp-oauth-login/",
    "checked_on": "2026-10-16",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-TELEPORT-OAUTH-01-v1",
    "candidate_record_sha256": "a6dc7032a20613be6dea3187fa4f4e432b5bcd13b231cedd2bf72f713c3f08d9",
    "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": "Some upstream servers need a separate OAuth token. Teleport still applies its own roles and tool permissions, while the upstream token satisfies that service. The documented login stores credentials locally and contacts the authorization server from the workstation. Changing the upstream URI requires a new login.",
    "required_buyer_context": "Teleport version, roles, upstream URI, OAuth issuer, scopes and client credentials. Effective configuration and dated operational evidence have not been 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",
    "checked_on": "2026-10-16",
    "claim_to_check": "One proxy login establishes all upstream permissions and contains every authentication flow.",
    "documented_statement": {
      "status": "documented",
      "statement": "Some upstream servers need a separate OAuth token. Teleport still applies its own roles and tool permissions, while the upstream token satisfies that service. The documented login stores credentials locally and contacts the authorization server from the workstation. Changing the upstream URI requires a new login.",
      "source_ids": [
        "teleport"
      ]
    },
    "buyer_evidence_required": [
      "Teleport roles and allowed tools.",
      "Upstream OAuth issuer, scopes and server URI.",
      "Client version and local credential handling."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Confirm both authority layers and authorization-server access before connecting."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "teleport",
        "url": "https://goteleport.com/docs/connect-your-client/model-context-protocol/mcp-oauth-login/",
        "final_url": "https://goteleport.com/docs/connect-your-client/model-context-protocol/mcp-oauth-login/",
        "title": "Teleport upstream MCP OAuth",
        "checked_on": "2026-10-16",
        "sha256": "10bc518f77bad3b243762103cd3387eae6254461cd8f1a2d0c61946a7a32287e",
        "bytes": 176808
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "Retain the two-layer identity boundary for a managed connector review.",
      "free": "Complete review, practical questions, sources and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Teleport version, roles, upstream URI, OAuth issuer, scopes and client credentials."
    }
  },
  "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#teleport-mcp-upstream-oauth-separate-authority",
  "machine_readable_record": "/varexis-index/records/teleport-mcp-upstream-oauth-separate-authority.json"
}