Skip to content

LNX link in bio

by lnx.net · remote · no sign-in to list tools · v1.0.1 · published by net.lnx

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

Changes · 2
CompareRegistry entry

2 tools: 2 change things.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http lnx https://lnx.net/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

2 tools

Changes things 2Claude Code: ask
  • check_usernameChecks whether lnx.net/<username> is available, and suggests alternatives if not.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Checks whether lnx.net/<username> is available, and suggests alternatives if not.

    Annotations the server declares

    • title: Check an lnx.net username
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • create_pageBuilds a link-in-bio page on lnx.net from the user's name, links, socials and bio, and returns a claim_url.No findings

    Why it is in this group

    • The name "create_page" says "create": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create a link-in-bio page
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http lnx https://lnx.net/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__lnx__create_page",
      "mcp__lnx__check_username"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as lnx. Review it before you use it.