lnx
Registry code: e9e6f67a8885aa7e
LNX (lnx.net) makes link-in-bio pages: one address such as lnx.net/yourname that collects someone's links, socials and a short bio. Use create_page when the user wants a link-in-bio page, a personal landing page, or one link for their Instagram/TikTok bio. Gather their name and links from the conversation first; ask only for what is missing. Then give the user the returned claim_url.
- endpoint
- https://lnx.net/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is lnx live?
- Yes — it answered the hub's last check (checked 4h ago). It answered 99% of checks over the last 30 days.
- Is lnx free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does lnx have?
- 2 tools: check_username, create_page.
- Is lnx safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.7%· all time 99.7%
last good check
of 2 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- unknown → live
- topic
- communication social media
- used for
- create a link-in-bio page
- check username availability
- takes → gives
- text → data
- tools
- 1 reads1 changes data
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
check_username reads unknown 22h ago
Checks whether lnx.net/<username> is available, and suggests alternatives if not.
{ "type": "object", "required": [ "username" ], "properties": { "username": { "type": "string", "description": "Desired username." } } }arguments 12 linescreate_page changes data unknown never probed
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.
{ "type": "object", "required": [ "name" ], "properties": { "bio": { "type": "string", "description": "Short plain-text bio, max 1000 chars. Blank lines separate paragraphs." }, "name": { "type": "string", "description": "Display name of the person or brand, shown as the page title." }, "links": { "type": "array", "items": { "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "https://, mailto: or tel: URL." }, "label": { "type": "string", "description": "Button text, e.g. \"Book a session\"." } } }, "description": "Link buttons, in display order (max 20). Websites, shops, booking pages, newsletters, latest release, etc." }, "theme": { "enum": [ "default", "boxy", "big-image" ], "type": "string", "description": "default = centered, round photo; boxy = full-width cover image; big-image = large photo beside the content." }, "socials": { "type": "array", "items": { "type": "object", "required": [ "platform", "url" ], "properties": { "url": { "type": "string", "description": "Profile URL; an email address for the email platform." }, "platform": { "enum": [ "instagram", "tiktok", "youtube", "twitter", "threads", "linkedin", "github", "facebook", "spotify", "twitch", "discord", "pinterest", "snapchat", "dribbble", "behance", "email", "website" ], "type": "string", "description": "twitter means X/Twitter; website is a personal site." } } }, "description": "Social profiles shown as icons (max 10). Anything not in the platform list goes in links." }, "tagline": { "type": "string", "description": "One-line subtitle under the name, e.g. \"Ceramic artist in Lisbon\". Max 120 chars." }, "username": { "type": "string", "description": "Desired address lnx.net/<username>: 3-30 lowercase letters, digits, _ or -. Omit to derive one from name." } } }arguments 93 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's ide9e6f67a8885aa7e.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/e9e6f67a8885aa7e/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/e9e6f67a8885aa7e?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.
Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.
- qr.lnx.net lnx-qr