# LNX link in bio (remote · lnx.net)

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

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `lnx.net`: 81/100 (this document), [markdown](https://verifymcp.io/servers/net-lnx-lnx/lnx.md), [page](https://verifymcp.io/servers/net-lnx-lnx/lnx)

## Channel facts

- Endpoint: `https://lnx.net/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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-10-23.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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 (excellent).
  - Context-footprint check failed: tool/resource definitions use about 392 tokens (~196/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 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.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the LNX link in bio MCP server?

LNX link in bio is a hosted endpoint at https://lnx.net/mcp, 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 net-lnx-lnx 'https://lnx.net/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "net-lnx-lnx": {
      "url": "https://lnx.net/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "net-lnx-lnx": {
      "type": "http",
      "url": "https://lnx.net/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.net-lnx-lnx]
url = "https://lnx.net/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-lnx-lnx": {
      "type": "remote",
      "url": "https://lnx.net/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add net-lnx-lnx --url 'https://lnx.net/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  net-lnx-lnx:
    url: "https://lnx.net/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "net-lnx-lnx": {
      "Transport": "http",
      "Url": "https://lnx.net/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add net-lnx-lnx -t streamable-http -u 'https://lnx.net/mcp'
```

### Other

```json
{
  "mcpServers": {
    "net-lnx-lnx": {
      "type": "http",
      "url": "https://lnx.net/mcp"
    }
  }
}
```

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-10-22 (score 81, +1)

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

### 2026-10-20 (score 80, +1)

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

### 2026-10-18 (score 79, +1)

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

### 2026-10-16 (score 78, +1)

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

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

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

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

No change was recorded against any check on this day. Stability & Change Management went from 33 to 40. That category is still filling its 30-day observation window: 10 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-10-10 (score 75, +2)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 33. That category is still filling its 30-day observation window: 6 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-10-06 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 20. That category is still filling its 30-day observation window: 4 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.

## MCP tools (2)

### `create_page` (~264 tokens)

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.

Input parameters:

- `bio` (string): Short plain-text bio, max 1000 chars. Blank lines separate paragraphs.
- `links` (array): Link buttons, in display order (max 20). Websites, shops, booking pages, newsletters, latest release, etc.
- `name` (string, required): Display name of the person or brand, shown as the page title.
- `socials` (array): Social profiles shown as icons (max 10). Anything not in the platform list goes in links.
- `tagline` (string): One-line subtitle under the name, e.g. "Ceramic artist in Lisbon". Max 120 chars.
- `theme` (string): default = centered, round photo; boxy = full-width cover image; big-image = large photo beside the content.
- `username` (string): Desired address lnx.net/<username>: 3-30 lowercase letters, digits, _ or -. Omit to derive one from name.

### `check_username` (~34 tokens)

Check an lnx.net username

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

Input parameters:

- `username` (string, required): Desired username.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/net-lnx-lnx/lnx#diagnostics

## Score history

- 2026-10-23: 81
- 2026-10-22: 81
- 2026-10-21: 80
- 2026-10-20: 80
- 2026-10-19: 79
- 2026-10-18: 79
- 2026-10-17: 78
- 2026-10-16: 78
- 2026-10-15: 77
- 2026-10-14: 77
- 2026-10-13: 76
- 2026-10-12: 76
- 2026-10-10: 75
- 2026-10-06: 73
- 2026-10-04: 72
- 2026-10-03: 72
- 2026-10-02: 71
- 2026-10-01: 71
- 2026-09-30: 70

## Common questions

### What is the LNX link in bio MCP server?

LNX link in bio is an MCP server listed in the public MCP registry as net.lnx/lnx. Build a free link-in-bio page (lnx.net/name) for the user from their links, socials and bio. This page covers its hosted endpoint (https://lnx.net/mcp).

### Is the LNX link in bio MCP server safe to use?

LNX link in bio scores 81 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 LNX link in bio MCP server expose?

LNX link in bio exposes 2 tools: create_page, check_username. Their descriptions and schemas cost roughly 298 tokens of context every time the server is loaded.

### Does the LNX link in bio MCP server require authentication?

No. We connected to LNX link in bio without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the LNX link in bio MCP server still maintained?

LNX link in bio is still listed as active in the MCP registry. We last reached this channel on 23 October 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://lnx.net/mcp
- Website: https://lnx.net/
- Changelog RSS feed: https://verifymcp.io/servers/net-lnx-lnx/lnx.xml
- Changelog JSON feed: https://verifymcp.io/servers/net-lnx-lnx/lnx.json
- HTML version of this page: https://verifymcp.io/servers/net-lnx-lnx/lnx