generated: '2026-07-19'
method: searched
source: https://mcp.linktr.ee/docs
surface: mcp-only
versioning:
  scheme: mcp-protocol-date + server-semver
  mcp_protocol_version: '2025-03-26'
  server_version: '0.1.0'
  docs: https://mcp.linktr.ee/docs
  note: >-
    The server card advertises protocol version 2025-06-18 while the tool reference states
    2025-03-26; the discrepancy is recorded as observed, not reconciled.
  discrepancy_sources:
  - https://linktr.ee/.well-known/mcp/server-card.json
  - https://mcp.linktr.ee/docs
deprecation:
  policy_url: null
  sunset_header: false
  note: >-
    No deprecation or sunset policy is published for the MCP surface. The server is at 0.1.0 and
    Linktree describes the wider developer program as still expanding access.
sla:
  url: null
  uptime_target: null
status_page: https://status.linktr.ee/
changelog: https://app.getbeamer.com/linktree/en
deprecated_operations: []
arbor_registry:
  added: '2026-08-13'
  surface: https://arbor.linktr.ee/
  versioning:
    scheme: semver
    current: 26.0.1
    source: https://arbor.linktr.ee/manifest.json
    protocol_version: '1.0'
    service_version: '1.0.0'
    service_version_source: https://arbor.linktr.ee/health
  deprecation:
    policy_url: null
    machine_readable: true
    field: items[].meta.intention.status
    values: [shipped, deprecated]
    deprecated_count: 3
    items:
    - name: dialog
      removal_version: null
      migration: Route destructive confirmations to AlertDialog; maintain existing usage only.
    - name: radio-group
      removal_version: 16.0.0
      migration: Install `radio` instead; alias kept only during the rename window.
    - name: popover
      removal_version: null
      migration: Shipped without an approved design (DS-290); route to RichTooltip or Menu.
    note: >-
      Arbor marks deprecated components in the manifest with migration guidance, and in one case
      a named removal version — real deprecation signalling on a public surface. It is NOT a
      published deprecation policy, and it covers design-system components rather than API
      operations, so no Deprecation pointer is claimed from it.
  see: components/linktree-components.yml
first_party_package_decay:
  checked: '2026-08-13'
  source: https://registry.npmjs.org/
  note: >-
    Release currency of the first-party @linktr.ee npm scope, the only provider-published dated
    decay evidence available for this provider.
  active:
  - {name: "@linktr.ee/messaging-react", version: 4.0.4, published: '2026-08-11'}
  - {name: "@linktr.ee/arbor-mcp", version: 0.12.0, published: '2026-08-08'}
  - {name: "@linktr.ee/linkapp", version: 0.0.56, published: '2026-02-19'}
  - {name: "@linktr.ee/create-link-app", version: 2.2.5, published: '2026-02-19'}
  - {name: "@linktr.ee/create-linkapp", version: 0.0.14, published: '2025-11-20'}
  - {name: "@linktr.ee/registry", version: 0.0.9, published: '2025-11-20'}
  stale:
  - {name: "@linktr.ee/ui-link-kit", version: 0.0.59, published: '2023-06-26', note: superseded by Arbor}
  - {name: "@linktr.ee/knapsack-gherkin-testcafe", version: 1.0.8, published: '2020-10-08', note: internal CI tooling}
  see: packages/linktree-packages.yml
developer_program:
  stage: expression-of-interest
  url: https://linktr.ee/marketplace/developer
  statement: >-
    "We're expanding access to our APIs and SDKs. Register your interest to join our developer
    program and start building integrations for millions of creators."
  note: >-
    As of this pass Linktree publishes no general-purpose public REST API. The MCP server is the
    only live programmatic surface; broader API/SDK access is waitlisted.
documentation_gaps:
- >-
  The server card and llms.txt both point documentation at https://developers.linktr.ee, which
  does not resolve (DNS failure). The live tool reference is at https://mcp.linktr.ee/docs.