LKJ — four-digit short links for TV browsers
REMOTE · LKJ.CX
Create four-digit short URLs for TV and console browsers. Free beta, no account or API key.
Available components
Last scanned (13 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Documents and Files
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
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 414 tokens (~207/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 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
- Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 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.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 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.
- 26 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 25 Oct 26 74
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 5 Nov 2026 · Probed https://lkj.cx/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lkj.cx | CN=WE1,O=Google Trust Services,C=US | 16 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 5875df34ea1f57f13514fc03cb2c725 |
| SANs: lkj.cx, *.lkj.cx | ||||||
| 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 secure
Validation of lkj.cx. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cx. | present | 6500 | 8 | Verified |
| lkj.cx. | present | 2371 | 13 | Verified |
| lkj.cx. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | base-uri 'self'; object-src 'none'; frame-ancestors 'self' |
| x-content-type-options | nosniff |
| referrer-policy | same-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lkj.cx/mcp | Verified | 200 | |
| http (plaintext) | http://lkj.cx/mcp | HTTPS enforced | 301 | https://lkj.cx/mcp |
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_short_link Create a short URL with a four-digit TV code ~186
Shorten a public website for easy typing on a TV remote, console browser, phone or computer. Returns a short preview URL, four digits, one-hour idle expiry and instructions. Free beta, no account or API key. Appropriate for temporary device handoff; not permanent bookmarks, private links, casting or sign-in transfer. Publishes the submitted URL behind a guessable code. Requires a fresh random UUID request_id; reuse the same URL and ID for retries. Five new attempts per network daily and shared beta capacity; do not evade limits.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | Generate a fresh random UUID for a new logical request. Retain it and the exact URL for retries. This is a request identifier, not an API key. |
| url | string | yes | The public website the user wants to share. Bare domains default to HTTPS. Never submit private URLs or access tokens. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| expires_at | string | yes | – |
| expires_in_seconds | integer | yes | – |
| expiry_policy | string | yes | – |
| instructions | string | yes | – |
| safety_note | string | yes | – |
| short_url | string | yes | – |
| tv_home_url | string | yes | – |
| tv_url | string | yes | – |
No examples provided.
get_service_info Check LKJ link-sharing capabilities and availability ~53
Read what LKJ does, whether new agent links are currently enabled, its fair-use limits and when to choose four-digit temporary links. Does not create or open a code, check a destination or consume a creation allowance.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the LKJ — four-digit short links for TV browsers MCP server?
LKJ — four-digit short links for TV browsers is a hosted endpoint at https://lkj.cx/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 · lkj.cx
claude mcp add --transport http cx-lkj-short-links 'https://lkj.cx/mcp'
What is the LKJ — four-digit short links for TV browsers MCP server?
LKJ — four-digit short links for TV browsers is an MCP server listed in the public MCP registry as cx.lkj/short-links. Create four-digit short URLs for TV and console browsers. Free beta, no account or API key. This page covers its hosted endpoint (https://lkj.cx/mcp).
Is the LKJ — four-digit short links for TV browsers MCP server safe to use?
LKJ — four-digit short links for TV browsers scores 79 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 LKJ — four-digit short links for TV browsers MCP server expose?
LKJ — four-digit short links for TV browsers exposes 2 tools: create_short_link, get_service_info. Their descriptions and schemas cost roughly 239 tokens of context every time the server is loaded.
Does the LKJ — four-digit short links for TV browsers MCP server require authentication?
No. We connected to LKJ — four-digit short links for TV browsers without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LKJ — four-digit short links for TV browsers MCP server still maintained?
LKJ — four-digit short links for TV browsers is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.