L1NK
REMOTE · L1NK.WEBSITE · SCANNED SEP 20
Short links with QR, custom domains and bot-free click analytics. Create, edit, delete, analyze.
Available components
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 517 tokens (~86/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the L1NK MCP server?
L1NK is a hosted endpoint at https://l1nk.website/api/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.
remote · l1nk.website
claude mcp add --transport http website-l1nk-links 'https://l1nk.website/api/mcp'
{
"mcpServers": {
"website-l1nk-links": {
"url": "https://l1nk.website/api/mcp"
}
}
} {
"servers": {
"website-l1nk-links": {
"type": "http",
"url": "https://l1nk.website/api/mcp"
}
}
} [mcp_servers.website-l1nk-links] url = "https://l1nk.website/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"website-l1nk-links": {
"type": "remote",
"url": "https://l1nk.website/api/mcp",
"enabled": true
}
}
} openclaw mcp add website-l1nk-links --url 'https://l1nk.website/api/mcp' --transport streamable-http
mcp_servers:
website-l1nk-links:
url: "https://l1nk.website/api/mcp" {
"McpServers": {
"website-l1nk-links": {
"Transport": "http",
"Url": "https://l1nk.website/api/mcp"
}
}
} assistant mcp add website-l1nk-links -t streamable-http -u 'https://l1nk.website/api/mcp'
{
"mcpServers": {
"website-l1nk-links": {
"type": "http",
"url": "https://l1nk.website/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Sept 26 76
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://l1nk.website/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=l1nk.website | CN=WE1,O=Google Trust Services,C=US | 23 Jul 2026 | 21 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | a81546ed265ff5da135b360e53da9359 |
| SANs: l1nk.website, *.l1nk.website | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of l1nk.website. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| website. | present | 26175 | 13 | Verified |
| l1nk.website. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://l1nk.website/.well-known/oauth-protected-resource/api/mcp", error_description="Sign in with OAuth or use Authorization: Bearer <L1NK API token>"
Bearer resource_metadata="https://l1nk.website/.well-known/oauth-protected-resource/api/mcp", error_description="Sign in with OAuth or use Authorization: Bearer <L1NK API token>"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'none'; frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Protected resource metadata
| Document | https://l1nk.website/.well-known/oauth-protected-resource/api/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://l1nk.website/api/mcp |
| Authorisation server | https://zlubrsnidqrbmobgsriw.supabase.co/auth/v1 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://l1nk.website/api/mcp | Verified | 200 | |
| http (plaintext) | http://l1nk.website/api/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_link Create short link ~115
Create a short link that redirects to a URL. Returns shortUrl, which is what you share.
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | – | Optional custom alias (letters, numbers, - and _; max 20). |
| domain_id | integer | – | Optional id of a verified custom domain of the account. |
| expires_in_days | integer | – | Optional expiry. Pro plan only. |
| name | string | – | Optional label to recognise the link in the dashboard. |
| url | string | yes | Destination URL. https:// is added if missing. |
No output schema declared.
No examples provided.
delete_link Delete link ~50
Delete a link permanently. Anyone opening it afterwards gets "not found". Confirm with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The short code or custom alias of the link (the part after the slash). |
No output schema declared.
No examples provided.
get_analytics Get click analytics ~60
Click analytics for the whole account: totals, bots, daily series and top links. The plan caps how far back you can look (Free 30 days, Pro 365).
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Days to look back. Default 30. |
No output schema declared.
No examples provided.
get_link Get link details ~51
Details of one link: destination, clicks, creation and expiry dates, last click and recent click history.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The short code or custom alias of the link (the part after the slash). |
No output schema declared.
No examples provided.
list_links List links ~24
List the active (not expired) links of the account with their click counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
update_link Update link ~102
Change where a link points, set a new expiry (Pro) or remove its expiry. The short code stays the same.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The short code or custom alias of the link (the part after the slash). |
| expires_in_days | integer | – | New expiry, counted from today. Not together with remove_expiration. |
| remove_expiration | boolean | – | true to make the link permanent. |
| url | string | – | New destination URL. |
No output schema declared.
No examples provided.
What is the L1NK MCP server?
L1NK is an MCP server listed in the public MCP registry as website.l1nk/links. Short links with QR, custom domains and bot-free click analytics. Create, edit, delete, analyze. This page covers its hosted endpoint (https://l1nk.website/api/mcp).
Is the L1NK MCP server safe to use?
L1NK scores 78 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 L1NK MCP server expose?
L1NK exposes 6 tools: create_link, list_links, get_link, update_link, delete_link, get_analytics. Their descriptions and schemas cost roughly 402 tokens of context every time the server is loaded.
Does the L1NK MCP server require authentication?
Yes. L1NK asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the L1NK MCP server still maintained?
L1NK is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.