L1NK

website.l1nkPublished by l1nk.websiteOfficial publisherv1.0.0Updated Oct 24, 2026

Short links with QR, custom domains and bot-free click analytics. Create, edit, delete, analyze.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowData & Analytics

Overview

AI-generated overview

Lets an assistant create, edit and delete short links with QR codes and custom domains, and read bot-free click analytics.

What you can do
L1NK is a remote MCP server for a short-link service. According to its description, it lets an assistant create, edit and delete short links, work with QR codes and custom domains, and analyze click statistics that exclude bot traffic. No individual tools are listed in the manifest.
When to use it
Worth adding when an assistant needs to shorten or manage links and report on their click performance, for example in marketing or content workflows where links are created and tracked programmatically.
Requirements
A remote streamable HTTP endpoint at the provider's site; nothing is installed locally. An Authorization header is required, carrying a bearer token created in the provider's account area; the manifest notes a free plan is included. Network access to the provider is needed.
Before you install
The Authorization header carries a secret bearer token; keep it out of logs and shared transcripts. The server can create, edit and delete links, so destructive changes are possible. Click analytics data is held by the third-party provider.

Installation

In SourceWeft

  1. Open L1NK in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/website.l1nk%2Flinks/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "l1nk": {
      "type": "http",
      "url": "https://l1nk.website/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

6

get_analytics

Get click analytics

Click analytics by people (bots reported apart): totals, daily series, countries, devices, browsers, referrers and top links. For the whole account, or for one link with code. The plan caps how far back you can look (Free 30 days, Pro 365).

Parameterscodedays

Version history

1
  1. v1.0.0LatestSep 17, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.