LNX link in bio

net.lnxPublished by lnx.netOfficial publisherv1.0.1Updated Oct 27, 2026

Build a free link-in-bio page (lnx.net/name) for the user from their links, socials and bio.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Builds a free link-in-bio page on lnx.net from a user's links, socials and bio, and checks whether a chosen username is available.

What you can do
  • Create a link-in-bio page from a name, links, socials and bio, returning a claim URL
  • Check whether a lnx.net username is free and get suggested alternatives
  • Hand the finished page to the user to review, edit and publish under their own LNX account
When to use it
Useful when someone wants a quick personal landing page collecting their links and social profiles, or wants to check whether a desired lnx.net username is still free before committing.
Requirements
A remote MCP endpoint at lnx.net; no package, environment variables or headers are declared. Publishing the generated page requires the user to open the claim URL and have an LNX account.
Before you install
The page is not public until the user opens the claim URL and publishes it with an LNX account, so the assistant only prepares a draft. The bio, links and socials are sent to lnx.net, a third party. No authentication is declared for the endpoint itself.

Installation

In SourceWeft

  1. Open LNX link in bio in the dashboard and add it to a workspace.
  2. 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/net.lnx%2Flnx/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": {
    "lnx-link-in-bio": {
      "type": "http",
      "url": "https://lnx.net/mcp"
    }
  }
}

Tools

2

create_page

Create a link-in-bio page

Builds a link-in-bio page on lnx.net from the user's name, links, socials and bio, and returns a claim_url. The user opens it, sees the finished page, can edit it, and publishes it to lnx.net/<username> with an LNX account. Nothing goes public until they do.

Parametersbionamerequiredlinksthemesocialstaglineusername

check_username

Check an lnx.net username

Checks whether lnx.net/<username> is available, and suggests alternatives if not.

Parametersusernamerequired

Version history

2
  1. v1.0.1LatestOct 1, 2026
  2. v1.0.0Sep 30, 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.