# Appy smart links (remote · mcp.appy.to)

Create and edit Appy smart links for apps, and read their click and install stats.

- Trust score: 80/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.appy.to`: 80/100 (this document), [markdown](https://verifymcp.io/servers/to-appy-smart-links/mcp.md), [page](https://verifymcp.io/servers/to-appy-smart-links/mcp)

## Channel facts

- Endpoint: `https://mcp.appy.to`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1531 tokens (~139/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Appy smart links MCP server?

Appy smart links is a hosted endpoint at https://mcp.appy.to/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http to-appy-smart-links 'https://mcp.appy.to/'
```

### Cursor

```json
{
  "mcpServers": {
    "to-appy-smart-links": {
      "url": "https://mcp.appy.to/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "to-appy-smart-links": {
      "type": "http",
      "url": "https://mcp.appy.to/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.to-appy-smart-links]
url = "https://mcp.appy.to/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "to-appy-smart-links": {
      "type": "remote",
      "url": "https://mcp.appy.to/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add to-appy-smart-links --url 'https://mcp.appy.to/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  to-appy-smart-links:
    url: "https://mcp.appy.to/"
```

### Netclaw

```json
{
  "McpServers": {
    "to-appy-smart-links": {
      "Transport": "http",
      "Url": "https://mcp.appy.to/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add to-appy-smart-links -t streamable-http -u 'https://mcp.appy.to/'
```

### Other

```json
{
  "mcpServers": {
    "to-appy-smart-links": {
      "type": "http",
      "url": "https://mcp.appy.to/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 74, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-24 (score 74)

First indexed and scored.

## MCP tools (11)

### `create_link` (~337 tokens)

Create a smart link. Only fallbackUrl is required; add targets for app stores, countryRules for per-country Android stores, a deeplinkUrl to open the installed app, a socialPreview for how the link looks when shared, and a slug for a readable URL. Returns the new link with its public url.

Input parameters:

- `countryRules` (array): up to 50 rules, one per country, that send Android visitors from that country to their own URL; huawei, samsung and xiaomi targets still win, and a rule for RU wins over the rustore target
- `deeplinkUrl` (string): in-app URL that opens the installed app, for example acme://product/42
- `fallbackUrl` (string, required): http(s) page for desktop visitors and anyone without a matching target
- `parameterForwarding` (boolean): pass the query string of each click on to the destination (Business and Enterprise)
- `slug` (string): custom slug of 5 to 64 lowercase letters, digits or hyphens; omit for a random one
- `socialPreview` (object): title, description and image that WhatsApp, iMessage, Slack, X, LinkedIn and other apps show when the link is shared; leave it out to show the destination's own preview
- `targets` (object): store or app page URL per platform; allowed keys: iphone, ipad, android, huawei, samsung (Galaxy Store), xiaomi (GetApps), rustore (RuStore, used for Android visitors in Russia)
- `title` (string): name shown in the dashboard, up to 200 characters

### `delete_link` (~43 tokens)

Delete a link. It stops redirecting immediately, so confirm with the user first.

Input parameters:

- `slug` (string, required): the link slug, the last part of the link URL

### `get_account` (~44 tokens)

Plan of the account behind the API key, the features it includes (api, mcp, sdk), its link limit (null means unlimited) and how many links it has.

### `get_account_stats` (~76 tokens)

Clicks across all of the account's links over a date range, with the same daily series and breakdowns as get_link_stats.

Input parameters:

- `end` (string): last day, YYYY-MM-DD in UTC; default today
- `start` (string): first day, YYYY-MM-DD in UTC; default 29 days before end

### `get_link` (~52 tokens)

Read one link by slug: its public url, fallbackUrl, deeplinkUrl, per-platform targets, country rules and settings.

Input parameters:

- `slug` (string, required): the link slug, the last part of the link URL

### `get_link_stats` (~105 tokens)

Clicks for one link over a date range: total and unique clicks, clicks per day, and breakdowns by country, operating system, device, browser, referrer and outcome (app store, app opened, fallback page).

Input parameters:

- `end` (string): last day, YYYY-MM-DD in UTC; default today
- `slug` (string, required): the link slug
- `start` (string): first day, YYYY-MM-DD in UTC; default 29 days before end

### `get_link_timeseries` (~84 tokens)

Clicks per day for one link over a date range, without the breakdowns. Use it for trends and charts.

Input parameters:

- `end` (string): last day, YYYY-MM-DD in UTC; default today
- `slug` (string, required): the link slug
- `start` (string): first day, YYYY-MM-DD in UTC; default 29 days before end

### `get_top_links` (~97 tokens)

The account's links ranked by clicks over a date range, best first. Use it to answer which links or campaigns performed best.

Input parameters:

- `end` (string): last day, YYYY-MM-DD in UTC; default today
- `limit` (integer): how many links to return, 1 to 100, default 10
- `start` (string): first day, YYYY-MM-DD in UTC; default 29 days before end

### `list_domains` (~67 tokens)

The account's custom domains (for example go.acme.com) with their status (pending, verifying, active, error), the DNS record to add, which domain is the default for link URLs, and how many domains the plan allows (limits.used and limits.max). Business and Enterprise plans.

### `list_links` (~83 tokens)

List the account's links, newest first, with their destinations and targets. Use search to find a link by slug or title.

Input parameters:

- `limit` (integer): page size from 1 to 100, default 20
- `offset` (integer): number of links to skip when paging
- `search` (string): only links whose slug or title contains this text

### `update_link` (~236 tokens)

Change an existing link. Only the fields you send change; the slug itself cannot be changed. Returns the updated link.

Input parameters:

- `countryRules` (array): the complete new list of country rules; it replaces the current list, an empty list removes every rule, leave it out to keep the rules as they are
- `deeplinkUrl` (string): new in-app URL; an empty string removes it
- `fallbackUrl` (string): new fallback page
- `parameterForwarding` (boolean): turn parameter forwarding on or off
- `slug` (string, required): slug of the link to change
- `socialPreview` (object): the complete new social preview; it replaces the current one, an empty title removes the preview, leave it out to keep it; send the current imageUrl back to keep an image uploaded in the dashboard
- `targets` (object): targets to change per platform (iphone, ipad, android, huawei, samsung, xiaomi, rustore); an empty string removes that platform, platforms not listed stay as they are
- `title` (string): new title; an empty string removes it

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/to-appy-smart-links/mcp#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 77
- 2026-10-30: 77
- 2026-10-29: 76
- 2026-10-28: 76
- 2026-10-27: 75
- 2026-10-26: 75
- 2026-10-25: 74
- 2026-10-24: 74

## Common questions

### What is the Appy smart links MCP server?

Appy smart links is an MCP server listed in the public MCP registry as to.appy/smart-links. Create and edit Appy smart links for apps, and read their click and install stats. This page covers its hosted endpoint (https://mcp.appy.to).

### Is the Appy smart links MCP server safe to use?

Appy smart links scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Appy smart links MCP server expose?

Appy smart links exposes 11 tools: create_link, delete_link, get_account, get_account_stats, get_link, and 6 more. Their descriptions and schemas cost roughly 1,224 tokens of context every time the server is loaded.

### Does the Appy smart links MCP server require authentication?

Yes. Appy smart links asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Appy smart links MCP server still maintained?

Appy smart links is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.appy.to/
- Authorisation metadata: https://mcp.appy.to/.well-known/oauth-protected-resource
- Website: https://appy.to/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/to-appy-smart-links/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/to-appy-smart-links/mcp.json
- HTML version of this page: https://verifymcp.io/servers/to-appy-smart-links/mcp